July 28, 20261 min read

Can Your Agent Search for MCPs?

The official registry holds 17,000+ servers - but your agent cannot query it. One thin MCP fixes that.

This piece was originally published on Medium - Can Your Agent Search for MCPs?. The directory behind it is catalog.agentage.io.

The official MCP registry holds more than 17,000 servers. It is a source-of-truth database built for other programs to crawl - not a tool your agent can call in the middle of a task. So the server your agent needs stays invisible until you stop, open a directory, and hand-edit a config file.

The fix is one discovery MCP. Point your agent at it and it reads the directory's tool descriptions and picks the right server itself - no browsing, no config editing. You used to browse. Now you ask.

#The four things that made it work

The agent searches, not you. One MCP exposes three tools - mcp_search, mcp_get, mcp_categories. The tool descriptions are the router; all the intelligence is server-side.
Two ways in. A remote endpoint at catalog.agentage.io/mcp with no auth and no install, or npx -y @agentage/find-mcp for Claude Desktop, Cursor, and VS Code. Same three tools either way.
Curation is the product. The directory crawls the official registry and drops the dead servers - more than half of them - that your agent should never see.
Thin client on purpose. About 290 lines. The client stays portable and boring so the directory can carry the weight.

A directory earns its keep by what it removes - the dead servers your agent should never see.

Read the full write-up on Medium →