Free open-source web search and page reading for LLMs, AI agents, and RAG.
GLM (Zhipu/Z.ai) as a ~10x cheaper file-editing subagent for AI coding agents.
The first portfolio AI agents can hire. Profile, products, pricing and briefs over MCP.
International legal analysis (ISO 31000) — 27 tools, 63 selectable jurisdictions; coverage varies.
Detect prompt injection, jailbreak, and social-engineering attacks in LLM agents.
39 tax tools for US taxpayers: federal/state tax, credits, deductions, retirement. All local.
Search, read and research the web, with hidden text stripped by default and sources hashed.
Git-backed org memory for AI agents — hybrid search, tables, files & a URI graph over MCP.
Discover and publish AI agents via DNS using SVCB records (RFC 9460).
MCP server for agentverse documentation, generated by doc2mcp.
MCP server for uagents documentation, generated by doc2mcp.
Azure Resource Manager inventory & ops for AI agents — governed, confirmation-gated.
Debezium / Kafka Connect CDC connector management for AI agents — governed, secret-safe.
Apache Kafka monitoring & management for AI agents (with consumer lag) — governed.
Keycloak admin for AI agents — realms, users, clients, roles; safe-by-default governance.
Oracle Cloud discovery + Terraform generation for AI agents — read-only, secret-safe.
uxspot.io UX reference: glossary, AI x UX tools directory, checklists and Learn UX curriculum.
AI invoice follow-up emails for freelancers. Draft-only, never sends for you.
Policy-gated agent spend with signed receipts and rail-extract audit.
Governed database access for AI assistants: masking, signed receipts, coverage reconciliation.
Fetch content from the web, cleaned up nicely for LLMs (using Defuddle).
Check service status and outage information via Downdetector.
Allow AI systems to list, search, and manage contacts via Google Contacts.
Allow AI systems to search for places and get business info via Google Maps Places API.
About AI & Agents MCP servers
This category collects servers that make agents better at being agents. You will find orchestration layers that run multi-step pipelines, routers that hand a task to the right model or sub-agent, evaluation and tracing tools, prompt and skill libraries, and bridges that let one assistant call another. Some wrap commercial model APIs; others are thin coordination layers around open-source frameworks.
Because these servers often sit between your agent and other systems, look closely at where data flows and what is logged. Prefer servers that document their tool contracts clearly, support streaming where relevant, and can run locally when the workload is sensitive. Many are new and move quickly, so check the repository's recent activity before relying on one in production.