MCP has a discovery problem. I built a meta-server that searches all 75,000 servers.
There are now tens of thousands of MCP servers. Glama indexes ~75,000. PulseMCP lists ~22,000. npm has thousands of packages tagged mcp-server. And yet the way we all use MCP is: find a server somewhere, paste it into a config file, restart the client, repeat. Two things are broken about this. Discovery is manual Your agent can't answer "is there a tool that queries Postgres?" — you have to know…
MCP has a discovery problem. The author built a meta-server called mcp-anything that can search all 75,000 MCP servers. Currently, finding a server and configuring it is a manual process where you have to know the answer to "is there a tool that queries Postgres?" before you can start using it. Adding more servers results in more context being burned, making it difficult to add more capabilities.
The author's solution is a single MCP server that inverts this process. Instead of configuring N servers, the model gets five meta-tools: search_mcp_servers, describe_mcp_server, list_mcp_tools, call_mcp_tool, and sync_registry. The index is built by syncing four catalogs - the official MCP registry, PulseMCP, npm search, and Glama - deduplicating across them by normalized repository URL and package identity, and merging popularity signals.
The ranking problem is solved by using stars and download counts instead of cosine similarity. Sessions are pooled with LRU eviction to reuse connections. Security is prioritized with safeguards against SSRF, arbitrary code execution, and secret leakage. A public hosted instance is available for trying out discovery, but it runs in discovery-only mode.
The author has learned that the unglamorous parts of shipping this product were the real work, including handling npm rate limits, dealing with case-sensitive namespace ownership, and deduplicating servers with different metadata shapes. They are working on per-tool indexing, live health signals, and container sandboxing for stdio. The repo is available for anyone interested in contributing.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
