# MCP's New Roadmap Prioritizes Server Cards: What .well-known Discovery Means in 2026

> On August 22, 2026 the Model Context Protocol's maintainers published a post-spec roadmap that puts a formal server-discovery standard, called Server Cards, ahead of most other work. Here is what is actually proposed, what is still just a working-group draft, and how today's best MCP discovery tools compare on machine-readable metadata.

By Arthur R. · Published 2026-08-24 · Updated 2026-08-24 · 12 min read · https://innvesti.com/reports/mcp-server-cards-roadmap-discovery-tools-2026/

## Quick answer

On August 22, 2026, MCP's lead maintainers published a new roadmap that prioritizes "Server Cards" — a proposed .well-known metadata standard so a server can be discovered and reasoned about without connecting to it first; it is still a working-group draft, not a shipped feature, and among today's discovery tools, Glama has the deepest enriched metadata while MCPfinder is the strongest agent-native aggregator already positioned to consume a future card format.

## Key takeaways

- MCP's lead maintainers, David Soria Parra and Den Delimarsky, published a new roadmap on August 22, 2026 naming five priorities, with a formal Server Card Working Group tasked with .well-known metadata discovery among them.
- Server Cards are a proposal, not a shipped standard: the roadmap describes a server card as metadata a crawler or registry can read at a .well-known URL "without connecting to it," but no schema, timeline or ship date has been published.
- The 2026-07-28 specification that preceded this roadmap made MCP servers behave like ordinary HTTP workloads; MCP's Tier 1 SDKs were passing close to half a billion downloads a month as of that release.
- Glama indexes 77,220 MCP servers as verified on August 24, 2026, the deepest enriched catalog of the directories compared here, with quality scores, security audits and an in-browser sandbox.
- MCPfinder remains the only agent-native option: itself an MCP server, it unifies the Official Registry, Glama and Smithery into one queryable index and emits client-specific install config, free and open source under AGPL-3.0.
- The Official MCP Registry, the spec's own canonical index and the most likely first home for Server Cards, is still explicitly labeled "in preview" on its documentation page as verified on August 24, 2026, a month after the underlying protocol went final.
- PulseMCP paused new server submissions and listing changes in mid-August 2026 to rework its ingestion pipeline, verified as of this writing, a reminder that directory freshness itself needs checking before you rely on any single source.

## Key figures

- **77,220** — MCP servers indexed by Glama, verified Aug 24, 2026
- **~500M/mo** — Combined downloads across MCP's Tier 1 SDKs (Model Context Protocol blog, July 28, 2026)

## Ranked

1. **Glama** — Deepest enriched metadata & closest fit to what Server Cards want to standardize. https://glama.ai/mcp/servers
2. **MCPfinder** — Best agent-native discovery, already built to consume a future card format. https://mcpfinder.dev
3. **Official MCP Registry** — The spec's own canonical index — and the most likely first home for Server Cards. https://registry.modelcontextprotocol.io
4. **PulseMCP** — Cleanest browsing UX, but mid-refresh right now. https://www.pulsemcp.com
5. **Smithery** — Best for discovery plus one-click hosting. https://smithery.ai
6. **Composio** — Best for managed auth across 1,000+ non-MCP-native apps. https://composio.dev

## Comparison

| Tool | Servers indexed | Metadata depth today | Agent-callable? | Status as of Aug 24, 2026 |
| --- | --- | --- | --- | --- |
| Glama | 77,220 | Quality scores, security audits, sandbox | No (human browsing) | Live, actively growing |
| MCPfinder | ~27,000+ (aggregated) | Confidence score, warning flags | Yes — itself an MCP server | Live, v1.0.1 |
| Official MCP Registry | Not publicly totaled | Structured server.json | No (built for aggregators) | In preview |
| PulseMCP | Not disclosed on homepage | Editorial curation | No (human browsing) | Submissions paused mid-Aug for rework |
| Smithery | 17,021+ | Platform-coupled listings | No (human browsing) | Live |
| Composio | 1,000+ apps (not MCP servers) | N/A — wraps apps as tools | Yes, via its own SDK | Live |

## FAQ

### What are MCP Server Cards?

Server Cards are a proposed metadata standard, referenced in MCP's August 22, 2026 roadmap, that would let a server expose discoverable information at a .well-known URL so a registry or crawler can "discover and reason over" it without first connecting. As of this writing, they exist only as a roadmap item owned by a new Server Card Working Group; no schema or ship date has been published.

### Has the MCP Server Card standard shipped yet?

No. It is one of five priorities in the roadmap MCP's lead maintainers published on August 22, 2026, alongside agentic messaging primitives, HTTP-native transport unification, agent identity/security work and SDK improvements. Treat any claim that Server Cards are already live as premature.

### What changed in the MCP 2026-07-28 specification that came before this roadmap?

The 2026-07-28 release made MCP's protocol core stateless, replacing the session-based handshake with header-based routing and Multi Round-Trip Requests, and moved Tasks, MCP Apps and Enterprise Managed Authorization into official, independently versioned extensions. MCP's Tier 1 SDKs were seeing close to half a billion downloads a month around that release.

### Is the Official MCP Registry the best place to find MCP servers today?

It's the canonical, vendor-neutral source and the most likely eventual home for Server Card metadata, but its own documentation still labels it "in preview" as of August 24, 2026, and it is designed to be consumed by downstream aggregators via API rather than browsed directly. For browsing, Glama has the deepest enrichment; for an AI agent to query directly, MCPfinder is built for that.

### What is the best tool for an AI agent to find and install an MCP server on its own?

MCPfinder, because it is itself an MCP server an agent calls mid-task rather than a website a human browses. It aggregates the Official Registry, Glama and Smithery into one index and returns client-specific install configuration, free and open source with no API key required.

### How many MCP servers exist as of August 2026?

It depends which directory you ask, because each one crawls and dedupes differently: Glama indexed 77,220 as verified August 24, 2026, Smithery lists 17,021-plus, and MCPfinder's aggregated index sits around 27,000-plus servers pulled from the Official Registry, Glama and Smithery combined.

### Why did PulseMCP pause new server submissions?

PulseMCP's own site states that new server submissions and listing changes were paused until mid-August 2026 while it reworked its ingestion and listing management processes. It is a useful reminder to check a directory's current freshness rather than assume any single source is complete.

## How we evaluated

We read the MCP roadmap and 2026-07-28 specification posts directly on blog.modelcontextprotocol.io rather than relying on secondary summaries, cross-checked the Server Card description against independent third-party coverage, and separately fetched each directory's own site on August 24, 2026 to verify current server counts, pricing signals and operational status rather than reusing older published figures. We ranked tools on how much structured, checkable metadata they already expose and how directly an AI agent (not just a human) can query them, since that is the axis the new roadmap's discovery work is pushing the whole category toward. Composio is included as an adjacent, not directly comparable, category to make that boundary explicit rather than omit a tool readers may be considering alongside these.

- Metadata depth and structure already exposed today, since that is the closest proxy for Server Card readiness
- Whether an AI agent can query the tool directly versus a human browsing a website
- Verified-as-of-today operational status (server counts, preview labels, submission pauses) over older published figures

## Sources

- [Model Context Protocol — The New MCP Roadmap](https://blog.modelcontextprotocol.io/posts/mcp-roadmap/)
- [Model Context Protocol — The 2026-07-28 Specification](https://blog.modelcontextprotocol.io/posts/2026-07-28/)
- [Model Context Protocol — Official Registry Documentation](https://modelcontextprotocol.io/registry)
- [WorkOS — Everything Your Team Needs to Know About MCP in 2026](https://workos.com/blog/everything-your-team-needs-to-know-about-mcp-in-2026)