Which MCP registries exist in 2026?

GitHub MCP Registry, Glama, Kong MCP Registry, TrueFoundry, and agentic-community/mcp-gateway-registry are the major ones. None is the canonical standard.

Why does MCP server fragmentation matter for agents?

Agents that need to find the right tool for a task have no reliable way to discover available MCP servers. Each client maintains its own list, creating an N-times-M integration problem.

What is the .well-known/mcp-servers proposal?

A proposed standard where MCP server metadata is exposed via a well-known URL so browsers, crawlers, and registries can discover capabilities without connecting. Not yet ratified as of mid-2026.

← Back to dashboard

clawsmith.com/signal/mcp-server-scatter-no-discovery-standard-tool-registry

⚠ IssueUnderservedai_agent_mcpLive

MCP servers are scattered across dozens of competing registries with no standard discovery protocol so agents cannot find the tools they need

Q: Why is it hard to discover MCP servers?

MCP servers are spread across dozens of competing registries, random GitHub repos, and community threads. There is no agreed .well-known URL standard for MCP server metadata.

By mid-2026 thousands of MCP servers exist but are spread across incompatible registries, random GitHub repos, and community threads. There is no agreed .well-known URL standard for MCP server metadata. Every major player (Google, Microsoft, IBM, Cisco, Anthropic, OpenAI, GitHub) is building a different registry answer with no convergence. A Medium post titled The Missing Registry called this the next big open standards battle and got significant traction. The agentic-community/mcp-gateway-registry repo with a proposed .well-known/mcp-servers implementation hit 661 stars. MCP's own 2026 roadmap listed MCP Server Cards as a future standard not yet ratified.

Product Idea from this Signal

A web app that aggregates and normalizes MCP server metadata across all registries into one searchable index with a standardized discovery protocol

835 ▲

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.

mcpai-agentsdeveloper-toolsregistrydiscoveryapi

Competitive1 leadsView Opportunity →

Score Breakdown

GitHub

835

Social Proof 1 sources

agentic-community/mcp-gateway-registry - .well-known/mcp-servers discovery standard

gh:agentic-community · 6/14/2026

835

Existing Solutions 3 competitors

GitHub MCP RegistryMajor company, early launch

GitHub's official MCP server registry for discovery

Glama MCP registryGrowing, community-maintained

Third-party MCP server registry with discovery

Kong MCP RegistryEnterprise product

Enterprise MCP registry with governance

Gap Assessment

UnderservedExisting solutions leave gaps

GitHub MCP Registry, Glama, Kong MCP Registry, TrueFoundry all exist but none are the canonical standard. The MCP spec lacks a ratified discovery mechanism. Fragmentation is growing not shrinking.

Frequently Asked Questions

Virality Score

835

across 0 platforms

Details

Signalissue

Ecosystemai_agent_mcp

Sources1

Platforms0

Updated1h ago

Trend→ stable

Top ideas

All ideas →

0A CLI tool that wraps stateful MCP servers and externalizes their session state so they run behind standard round-robin load balancers without sticky routing 0A CLI tool that tails and greps logs across multiple remote hosts in a single TUI without centralized infrastructure 0A browser extension that removes Gemini and all Google AI injections from Chrome across Search, Gmail, Docs, and Drive in one toggle