Everything we measure, as plain CSV. Rebuilt every night, last on 4 August 2026. Take it, chart it, publish it — the only thing we ask is a link back.
Every remote endpoint gets a real MCP handshake every 15 minutes. The file records what it answered and when we asked — not what its README claims.
Weekly downloads from npm and PyPI. Everyone else publishes GitHub stars, which say how many people liked a link, not how many run the thing.
Agent Skills are matched by content hash, so one skill repackaged into forty repositories counts once — with the number of copies in its own column.
Read this before you build on the numbers.
Local servers have no uptime. Roughly half the registry ships as an npm or PyPI package that the client starts on your machine. There is no address to ping, so those rows carry installs but empty uptime columns — that is missing data, not zero availability.
“Not responding” is not always broken. A server behind a corporate network or one that requires an API key answers our anonymous handshake with a refusal. We record the refusal honestly; it usually means the server is running and simply will not talk to strangers.
Uptime history starts when we did. The daily file begins on the day we ran the first check, not on the day the ecosystem appeared. It grows by one row a day and cannot be backfilled — by us or by anyone else.
curl -O https://mcpbeat.com/static/data/servers.csv