MCP Server Ecosystem Tracker: 56 Servers Cataloged

The Model Context Protocol ecosystem now spans at least 15,930 indexed servers across four major registries — but most published lists mix categories, omit auth models, or never tell you who actually maintains the server. This Issue #1 of our monthly MCP tracker catalogs 56 production-ready or vendor-backed servers across 10 categories with all 7 columns: name, category, registry source, auth model, transport, maintainer, and status.

The ecosystem shifted structurally in May 2026. MCP tunnels — a research preview that opens an outbound-only encrypted connection so agents can reach customer data without inbound firewall rules — were announced at Code with Claude London on May 19, 2026. Self-hosted sandboxes entered public beta the same day, with Cloudflare, Daytona, Modal, and Vercel as sandbox providers. Together these announcements reshape what "production" means for MCP servers: hosted endpoints, OAuth 2.1, and outbound-only gateways are now the default deployment shape, not the advanced configuration.

This guide covers the what-changed context for Issue #1, a registry count comparison across all eight major sources, the full 56-server catalog by category, an auth-model and transport breakdown, and a preview of what we will track in Issue #2 (June 2026). For the deployment playbook, see our MCP server org deployment 30-60-90 day plan. For auth-model best practices, see the MCP server security engineering guide.

Three events in May 2026 make this the right moment to launch a recurring MCP tracker. First, the MCP tunnels research preview and self-hosted sandboxes public beta were announced at Code with Claude London on May 19, 2026 — the first structural change to the production deployment model since the 2025-11-25 spec formalized OAuth 2.1. Second, AWS's Agent Toolkit MCP Server reached general availability with 60+ official servers spanning documentation, infrastructure, Lambda, containers, AI/ML, and analytics — the largest first-party server catalog from any cloud provider. Third, the observability category expanded from 6 to 9 vendor-maintained servers between March and May 2026, with IBM Instana, Honeycomb, and New Relic all shipping GA endpoints.

For context on the code-with-claude event specifically, see our companion post: Code with Claude: sandboxes and MCP tunnels launch. The MCP tunnels announcement quoted a developer from The New Stack coverage directly: "The compliance team is the real bottleneck for production agents, not the model. Self-hosted sandboxes and MCP tunnels are the layer that lets agents actually run inside the customer's perimeter instead of behind a sandbox the security team takes six weeks to clear."

The spec version to track is 2025-11-25 — published November 25, 2025 on the protocol's first anniversary. It introduces async Tasks, improved OAuth 2.1 enforcement, structured tool outputs, and elicitation primitives. The previous spec version (2025-06-18) focused on the original OAuth-based authorization and elicitation groundwork. Do not cite 2024-11-05 as the current spec — that was the launch-era version. For a full engineering walkthrough of what the spec update means for server authors, see the MCP inspector deep-dive.

The MCP registry landscape has no single source of truth. Each aggregator uses different inclusion criteria, quality filters, and update cadences. PulseMCP deliberately omits low-quality entries and updates daily. Smithery includes any installable server. The official MCP Registry (~2,000) applies a curation layer. First-party catalogs (AWS, Azure, Google Cloud) list only their own servers. The table below is a May 2026 snapshot — treat counts as point-in-time and verify against the source before using in a procurement decision.

The order-of-magnitude gap between curated first-party catalogs and aggregator registries is the key insight for buyers: AWS's 60+ servers are all GA and AWS-maintained; PulseMCP's 15,930+ include community experiments, archived projects, and alpha tooling. The useful signal is the overlap between the official MCP Registry (~2,000) and PulseMCP — a server appearing in both has cleared two curation filters. For marketing-specific server selections, see our companion catalog: 25 MCP servers for marketing reviewed.

The database category is the most mature in the MCP ecosystem and the most important to audit carefully — several Anthropic reference servers in this category have been archived, and community successors with different maintainers, different auth models, and different stability guarantees have filled the gap.

* Supabase MCP is hosted at mcp.supabase.com/mcp (HTTP transport, OAuth 2.1 + dynamic client registration + PAT, 2.6k GitHub stars). Google Cloud MCP Toolbox covers PostgreSQL, MySQL, SQL Server, Oracle, MongoDB, Redis, Elasticsearch, ClickHouse, Couchbase, Neo4j, Snowflake, and Trino through a single server binary. SQLite MCP: the original Anthropic reference server is archived; community successors exist with varying quality. Verify maintainer status before deploying.

The CRM category is where the OAuth 2.1 transition is most visible. HubSpot, Salesforce, Notion, and Linear all use OAuth 2.1 as their primary auth model — only Pipedrive (community-only, no official server) uses an API key. If your CRM stack is in this category, you should expect OAuth 2.1 as the standard integration pattern in 2026. For teams building agentic CRM workflows, our CRM automation services cover the full integration architecture.

HubSpot MCP exposes 100+ tools across contacts, companies, and deals. Salesforce MCP (salesforcecli/mcp) ships 60+ tools and is the most comprehensive CRM MCP in any ecosystem as of May 2026. Pipedrive has no official MCP server as of April 2026 — the community server (iamsamuelfraga/pipedrive-mcp) exposes 100+ tools but carries no Pipedrive maintenance guarantee.

Dev tools is the most active category in the MCP ecosystem by server count, by maintainer quality, and by the speed of the archived-to-GA transition. Several servers in this category started as Anthropic reference implementations in November 2024 and have since been taken over by the original vendors — GitHub, Sentry, and GitLab all made this transition. The Atlassian Remote MCP entered beta in May 2025 and reached GA in February 2026, covering Jira, Confluence, and Compass with 72+ tools.

GitHub MCP: Anthropic's reference is archived; GitHub now maintains github/github-mcp-server officially. Sentry MCP: reference archived; Sentry maintains getsentry/sentry-mcp. GitLab MCP: reference archived; community successors only as of May 2026. Atlassian Remote MCP covers Jira, Confluence, and Compass with 72+ tools (OAuth 2.1, GA since February 2026). PagerDuty MCP exposes 60+ tools including full incident write APIs.

Every server in the productivity category uses a hosted transport — no stdio-only options remain for the major productivity platforms. The Anthropic reference servers for Google Drive and Slack have both been archived; Google and Slack each ship official hosted replacements. ClickUp made the most dramatic capability expansion in this category, growing from 6 to approximately 49 tools in 2026.

Microsoft 365 MCP is exposed via Azure MCP tools. Slack MCP and Google Drive MCP: the original Anthropic reference servers are archived; both vendors now ship official replacements. ClickUp expanded from 6 to ~49 tools in 2026. Asana's official server launched February–April 2026.

The data and analytics category shows the clearest split between cloud-hosted OAuth 2.1 servers (BigQuery, Looker — both Google Managed MCP) and community-first stdio servers (dbt, DuckDB). The dbt server is partly dbt Labs-supported, making it a rare hybrid between community and vendor in this category.

BigQuery and Looker are exposed through the Google Managed MCP catalog announced at Google Cloud Next '26. For analytics and data pipeline integrations, our analytics services team works with dbt and BigQuery MCP server patterns.

The AI/ML category is the most architecturally interesting: these servers allow one AI model or agent to call another model's capabilities via MCP. The Anthropic Claude API MCP Connector and the OpenAI MCP Connector are both in beta — the protocol for AI-to-AI tool use via MCP is maturing but not yet GA on either platform. Pinecone and Qdrant are the two production-grade vector search MCPs in this catalog; Weaviate and LanceDB were omitted as their MCPs are not ready for production use as of March 2026.

Anthropic Claude API MCP Connector entered public beta February 2026 (mcp-client-2025-11-20). OpenAI MCP Connector: via ChatGPT MCP connectors on the Developer Platform. Weaviate and LanceDB MCPs are not cataloged here — per March 2026 vector DB review, neither is ready for production use.

The observability category grew from 6 to 9 vendor-maintained servers between March and May 2026, according to ChatForest's observability MCP tracker. The five cataloged here are the highest-maturity entries by stars, downloads, or explicit GA/production status. Honeycomb is worth a separate callout: it deprecated its self-hosted MCP server in 2026 in favor of a fully managed hosted endpoint — the first observability vendor to treat MCP as a managed service rather than a self-hosted tool. For reliability patterns across server categories, see our 100-server MCP reliability stress test.

Grafana MCP: 2,600+ GitHub stars, 252,000+ Docker Hub pulls — the most-used observability MCP by community signals. New Relic MCP reached GA February 23, 2026, powering the New Relic Agentic Platform launched the following day. Honeycomb deprecated its self-hosted server in 2026; the hosted endpoint is now the only supported option.

The security category has the weakest maturity profile in this catalog. No server here has reached full GA except 1Password (Beta) — and HashiCorp Vault remains community-only. This is partly structural: security vendors are cautious about exposing credential and secret management APIs through a protocol still maturing its OAuth 2.1 enforcement. For a detailed threat model of MCP server auth patterns, see the MCP server security best practices engineering guide.

1Password MCP (1Password/op-mcp) is CLI-backed. HashiCorp has not shipped an official Vault MCP; the community server at hashicorp-community/vault-mcp carries no HashiCorp maintenance guarantee. Snyk MCP supports CLI scans and issue listing. Auth0 MCP covers tenant management and app configuration.

The web and search category is the most homogeneous in the catalog: all five servers are GA, all use API key auth, and all support HTTP transport alongside stdio. This category is also where the Anthropic-reference-to-vendor-successor transition is most complete — Brave Search moved from the archived reference repo to a community/Brave-maintained option, and the void has largely been filled by Tavily and Exa. For web scraping pipelines, Apify stands apart: a single server exposing 19,000+ pre-built Actors.

Brave Search MCP: Anthropic's reference is archived; Brave and community maintainers have filled the gap. Tavily MCP (tavily-ai/tavily-mcp) covers real-time web search, extraction, and site crawl. Apify MCP exposes 19,000+ pre-built Actors through a single server endpoint. For content pipeline integrations using web search MCP servers, see our content engine services.

This category contains the two most architecturally distinct entries in the catalog. The Local Filesystem MCP is one of seven active Anthropic reference servers — it is explicitly educational, not production-ready, and ships with no security guarantees beyond what you configure in your own environment. The AWS MCP Server (Agent Toolkit) is the opposite: 60+ GA servers hosted by AWS across two regions, covering the broadest scope of any single first-party MCP catalog. They represent the two poles of the ecosystem: educational reference and hyperscaler-managed production.

Local Filesystem MCP is one of the 7 maintained reference servers at github.com/modelcontextprotocol/servers (86.2k stars, 10.8k forks). It is explicitly an educational example; Anthropic does not guarantee production stability for reference servers. AWS MCP Server reached GA May 2026 with 60+ servers hosted in us-east-1 and eu-central-1 covering docs, infrastructure, Lambda, containers, AI/ML, and analytics.

Every other published MCP list shows transport (hosted vs. stdio) or auth model in isolation. This section cross-references both columns against the 56-server catalog to surface the structural trend that matters for enterprise buyers: the 2026 ecosystem is mid-transition from stdio + API key to hosted + OAuth 2.1, and the split tells you which category of server you are looking at before you read another word of documentation.

The transport split is equally informative. Of the 56 servers, roughly 28 support stdio-only or stdio-primary transport, while approximately 22 are hosted-endpoint (vendor-operated remote MCP over streamable HTTP), and 6 support both. The hosted count will accelerate: every new first-party server from AWS, Google Cloud, Azure, HubSpot, Salesforce, Notion, Linear, Asana, Slack, and Vercel launched in 2026 uses a hosted endpoint. The community/research servers from 2024-2025 default to stdio. The clearest heuristic: if a server was launched by a vendor after January 2026, assume hosted + OAuth 2.1 unless the docs say otherwise.

For teams evaluating which auth model to implement in a custom MCP server, the MCP server patterns for enterprise AI agents covers the full decision framework including token scope design and service-account patterns.

Issue #2 (June 2026) will track changes against this May baseline. The 56-server catalog is the reference point — every entry will be re-verified, new servers will be added, and any status changes (beta to GA, community to archived, preview to deprecation) will be called out explicitly with a change log column.

Three categories to watch most closely for Issue #2:

MCP tunnels graduation. Tunnels launched as a research preview on May 19, 2026. If Anthropic follows its typical cadence (research preview to public beta in 4-6 weeks), a beta announcement could land before or during June. A beta status would materially change the hosted-vs-self-hosted calculation for any server in this catalog that currently requires inbound network access.

Security category maturation. The security category is the weakest in this issue — no GA servers, three beta entries, one community server. HashiCorp Vault is the most likely to announce an official MCP server in the June timeframe, given HashiCorp's participation in the Linux Foundation's AAIF. Auth0's management API MCP is also a candidate to exit beta.

Registry count trajectory. PulseMCP has been growing at roughly 1,000+ new indexed servers per month in Q1-Q2 2026. If that pace holds, we may see 16,500+ entries on PulseMCP by the June snapshot. Smithery's growth from ~6,000 (March) to ~7,300 (May) is a 1,300-server addition in two months — a pace that suggests the ecosystem is still in its fastest growth window.

For the full H1 2026 adoption data context that informs our tracking methodology, see the MCP ecosystem H1 2026 retrospective. For enterprise teams deciding whether to build or buy MCP server infrastructure, the MCP server build vs. buy TCO calculator covers the full cost and capability tradeoff. Our AI transformation services team advises on MCP server selection and deployment architecture for enterprise clients.