Ecosystem radar

How fast is the agent tool layer growing? Each week we count the servers published or updated in the official MCP registry, straight from its API. No ranking, no summaries, no opinion — a count, a trend, and a recent sample you can reproduce with one curl.

Machine-generated · rebuilt weekly from the official MCP registry, no editorial judgment. How it works.

Servers per week

Distinct server names whose registry record changed during each ISO week (Mon–Sun, UTC). Bar length is relative to the busiest week shown.

2026-W29 · 2,377 servers

2026-07-13 → 2026-07-20 · 2,354 new, 23 updated. Showing the 60 most recently updated — the full set is one query: registry.modelcontextprotocol.io/v0/servers?updated_since=2026-07-13T00%3A00%3A00.000Z

How it works

A weekly cron queries the official MCP registry’s public API (GET /v0/servers?updated_since=<week start>), pages through the results, collapses multiple versions of the same server to one entry, and writes a JSON snapshot per ISO week.

No LLM, no scoring, no editorial pick. Names, descriptions, versions and dates are passed through verbatim — the only text change is repairing double-encoded UTF-8 (mojibake) some publishers submit, which is a bug fix, not an edit.

The registry moves more than a thousand servers a week, so the page shows a recent sample; the count and the reproducing query are the point, not an enumeration. Each week’s raw JSON is served as-is under /radar/<week>.json.

Source code: the wellknownmcp org. This is a small demonstration of honest agentic publishing — data with its provenance attached, not content dressed as data.

Last rebuilt 2026-07-20 · everything here is verifiable — probe before you trust.