Names added
Present now, absent from the previous observation.
API TRACKER RESEARCH · BY APIDECK
Watch the MCP ecosystem grow.
A dated view of registry listing growth. See what changed, where additions came from, and what the numbers actually measure.
Latest observation: · Official MCP Registry
48,439Registry listings observed
+3,634Net change since 2026-10-17
+8.1%Change over the observed interval
OBSERVED HISTORY
Registry size over time
Each bar is a completed observation. Gaps are not interpolated; no daily growth is assumed. Bars start at zero.
What changed?
2026-10-17 → 2026-10-23 UTC
No longer present
Absent now. This does not prove a project shut down.
Largest sources of new listing names
Namespaces identify registry publishers, not verified companies. These are addition counts, not quality or popularity rankings.
| Registry namespace | Added listings |
|---|---|
| com.textforagents | 115 |
| io.github.theluckystrike | 77 |
| io.github.pipeworx-io | 53 |
| io.github.alphaparkinc | 48 |
| com.insightfulpipe | 47 |
| com.modevc | 46 |
| dev.agentdiet | 31 |
| co.youraitools | 19 |
| com.mambabuilt | 18 |
| io.github.sepehr071 | 18 |
Sources & methodology
Source: Official MCP Registry, normalized with MCP Connect. Glama and Smithery are not added as separate sources to this series. A registry record may itself describe an aggregator-hosted service.
- Fetch every available page with the latest-version filter. Reject incomplete refreshes. Exclude records marked deleted or deprecated, then count each exact registry name once.
- Compare name sets across consecutive observations. Version changes under the same name do not count as additions. Renames can appear as an addition and a removal; different names may refer to the same implementation.
- Record UTC timestamps and SHA-256 hashes of sorted name arrays. Keep the source and counting method fixed. A source or identity-method change requires a separate series.
- Refreshes are scheduled daily, subject to the catalog workflow being enabled and completing successfully. Updates are reviewed before publication; this page is not a live feed. Missing dates mean no published observation.
Only two observations were available when this series started. We do not infer a daily trajectory or annualize this interval. Publisher verification and deduplicated implementation growth need separate evidence and are not measured here.
Cite this tracker
API Tracker by Apideck. “MCP registry growth tracker.” Include the observation dates and describe the unit as registry listings, not unique MCP products.
https://apitracker.io/mcp-growth