Data
What we measured about every server in the official MCP registry, in one file. Free to use with attribution (CC BY 4.0).
Archived snapshot of 2026-10-04, citable: doi:10.5281/zenodo.23137127 (Zenodo).
The registry today
| Servers in the registry | 66,705 | read 2026-11-18 |
|---|---|---|
| Remote endpoints checked | 43,212 | checked 2026-11-18 |
| Completed the MCP handshake | 23,464 (54%) | our check |
| Asked for sign-in first | 12,735 (29%) | our check |
| Asked for payment first | 172 | our check |
| Did not complete the handshake | 6,841 (16%) | failures re-checked |
| Unknown, left out of the counts above | 814 | rate-limited us or templated URL |
| Linked repositories that no longer resolve | 4,239 of 33,118 | GitHub API, 2026-11-18 |
| Entries that read like tests | 789 | name pattern |
Columns
name, endpoint, check_result, check_class, checked_at, protocol, tool_count, github_repo, github_stars, github_last_push, github_archived, registry_status, flags, indexed, npm_package, npm_exists, npm_weekly_downloads, npm_latest_publish, pypi_package, pypi_exists, pypi_last_week_downloads, pypi_latest_upload, package_deprecated
Multiple packages in one registry use aligned JSON arrays in the package columns; blank values or null array entries mean unknown. Zero downloads and false existence are preserved. package_deprecated is true when any listed npm package is deprecated or any listed PyPI release is yanked; false means all listed packages have known false flags, otherwise it is blank. Downloads include bots and CI.
Descriptions are not in the file: they belong to their publishers and appear with attribution on each server's page. How each column is measured.