MCP Server Ecosystem: Data on 61,855 Servers

Zusammenfassung

Pixel shares an analysis of 61,855 MCP servers, revealing rapid registry growth and a shift toward remote hosting, with 60% of servers remote-only. The overview also compares package ecosystems, GitHub star distribution, and licensing—useful context for developers tracking MCP adoption and choosing tools.

DEV Community

The State of MCP Servers: I analyzed all 61,855 of them

I run Serverdex, a directory that indexes the official Model Context Protocol (MCP) registry. That means I have a row for every published MCP server sitting in a database — so I pulled the numbers on all 61,855 of them and wrote up the state of the ecosystem. Here's what stood out. 1. The registry 100x'd in about a year In September 2025 the registry held a few hundred servers. It has roughly doubled month over month through 2026: Feb 2026: 845 new servers Jul 2026: 3,465 Sep 2026: 9,427 Oct 2026: 16,876 October 2026 alone added more servers than existed in the entire first six months. If you've felt like MCP went from "interesting protocol" to "everyone is shipping one" overnight — the data agrees. 2. Remote won MCP started as local stdio servers: you install a package and run it yourself. That is no longer the norm. 60% of servers are remote-only — a hosted HTTP endpoint with nothing to install. Only ~32% ship as a local package alone. streamable-http is now the dominant transport, well ahead of local stdio. The ecosystem has quietly shifted from "download and run" to "point your client at a URL." The median server is now something you connect to, not something you install. 3. How they ship Of the ~24,000 servers with an installable package: npm: 16,717 PyPI: 5,367 MCPB: 2,295 Docker (OCI): 1,794 NuGet: 175, Cargo: 129 MCP tooling is a JavaScript-first world, with Python a clear second. 4. A few giants, a long tail There are 1.27 million combined GitHub stars across the index — but attention is brutally concentrated. 92 servers hold 1,000+ stars each, while the vast majority have none. The head is names you'd expect: Browser Use, Scrapling, Metabase, CCXT, the official GitHub MCP server. 5. Open by default MIT is the default license of the MCP ecosystem by a wide margin (6,571 servers), with Apache-2.0 a distant second (778). The space is overwhelmingly open source. Methodology Numbers are from the Serverdex index of the official MCP registry, as of 15 November 2026: 61,855 published servers. Growth is by first-publication date. Languages, stars and licenses cover the servers with a resolvable public GitHub repository. "Remote-only" means a server advertises an HTTP endpoint and no installable package. The full report — with charts and the most-starred servers — is here: The State of MCP Servers. If you maintain an MCP server, it's probably already indexed; you can claim its page for free. And if you want a specific cut of the data (by category, by month, remote vs local over time), ask in the comments — happy to pull it.
MCP Server Ecosystem: Data on 61,855 Servers
Powered by Readybot.io

Das Neueste von Pixel

Fix GitHub Pages: Missing Artifact Error

Pixel's announcement explains why the GitHub Pages deploy action reports that no github-pages artifact was found. It covers skipped or failed build jobs, missing uploads, …

Rotate DB and Redis Passwords Without Downtime

Pixel shares a practical guide to rotating exposed database and Redis passwords without interrupting application connections. The approach updates Secrets, changes service credentials, and gradually …

AI Agent Receipts Prove What Actually Executed

Pixel’s announcement examines how public Zambo receipts verify what an AI agent actually did. A BTC price fetch succeeded with a recomputable output hash, while …