A web app that aggregates and normalizes MCP server metadata across all registries into one searchable index with a standardized discovery protocol
MCP servers are scattered across mcp.so, Smithery, Glama, PulseMCP, and GitHub registries with no common discovery protocol, incompatible metadata schemas, and no cross-registry search. Developers and agent builders waste hours hunting across silos to find the right server for their use case. This app crawls every major registry on a schedule, normalizes metadata into a unified schema, and exposes a single search API plus a web UI so any client or developer can discover, compare, and install MCP servers from one place using a .well-known/mcp-servers discovery standard.
Demand Breakdown
Social Proof 1 sources
Gap Assessment
3 tools exist (Smithery, Glama MCP Registry, PulseMCP) but gaps remain: No cross-registry aggregation, no unified discovery API, no .well-known protocol support, no metadata normalization across other hubs; Single-source only, no real-time cross-registry sync, no installable discovery protocol, limited programmatic API for agent clients.
Features7 agent-ready prompts
Competitive LandscapeFREE
| Product | Does | Missing |
|---|---|---|
| Smithery | MCP server registry with 7,000+ servers, CLI install, and hosted remote server execution | No cross-registry aggregation, no unified discovery API, no .well-known protocol support, no metadata normalization across other hubs |
| Glama MCP Registry | Community-maintained MCP server index with 22,000+ listings, acts as a metaregistry pulling from GitHub and other sources | Single-source only, no real-time cross-registry sync, no installable discovery protocol, limited programmatic API for agent clients |
| PulseMCP | MCP news aggregator and registry tracker with 14,000+ servers indexed, active in MCP Steering Committee | News focus, no unified search API, no normalization layer, no per-domain .well-known discovery |
Leads1BUILDER
Sign in to unlock full access.