[theevoq]

mcpbeat monitors the MCP ecosystem rather than listing it: every remote address in the registry receives a real JSON-RPC initialize handshake every 15 minutes, and the tool list of each responding server is recorded together with the date it was read.

Current numbers, measured today:

• 20 107 servers tracked, 10 570 of them reachable over the network
• 7 900 answering right now; 2 279 are listed as active in the registry but never respond
• 1.4M checks performed so far

Adoption comes from actual npm and PyPI download counts rather than GitHub stars, and Agent Skills are deduplicated by SHA-256 of their content, so a skill repackaged into forty repositories counts once.

Everything is published as CSV under CC BY 4.0 at https://mcpbeat.com/data/ — no key, no signup, so any number on the site can be verified against the raw rows.

[cliffhall]

Thank you for this pull request, and apologies for the long wait for a response. This repository does not accept new server implementations or server listings, and it now accepts issues, not pull requests, from anyone but its maintainers (CONTRIBUTING.md). To make your server discoverable, publish it to the MCP Server Registry by following its quickstart guide.

This is part of the backlog triage in #4875.