Data

What we measured about every server in the official MCP registry, in one file. Free to use with attribution (CC BY 4.0).

Download CSV

Archived snapshot of 2026-10-04, citable: doi:10.5281/zenodo.23137127 (Zenodo).

The registry today

Servers in the registry61,158read 2026-11-10
Remote endpoints checked39,109checked 2026-11-10
Completed the MCP handshake23,547 (60%)our check
Asked for sign-in first11,263 (29%)our check
Asked for payment first128our check
Did not complete the handshake4,171 (11%)failures re-checked
Unknown, left out of the counts above687rate-limited us or templated URL
Linked repositories that no longer resolve4,135 of 31,098GitHub API, 2026-11-10
Entries that read like tests774name 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.