Categories › AI & Agents › Multi-agent, orchestration & workflows
MCP server counts from the official registry, new servers per day, and MCP/A2A spec changes. As is.
Remote server: your requests and data go to unstuckagents.com. Claude Code: claude mcp add --transport http agent-economy-data https://unstuckagents.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
ecosystem_overview — Returns the total number of servers in the Official MCP Registry, new servers in the last 7 and 30 days, the 3 latest MCP and A2A spec changregistry_totals — Returns how many MCP servers the Official MCP Registry lists, split by status (active, deprecated), remote transport (streamable-http, sse) new_servers_count_since — Returns how many MCP servers were first published on or after a date, split by namespace type. Example output: {"since":"2026-10-01","count"namespace_types — Returns who publishes MCP servers and how: the split between code host namespaces (io.github, io.gitlab, io.bitbucket) and publishers' own ddaily_new_counts — Returns a ready-to-chart series of new MCP servers per UTC day for the last N days (1 to 365). The last day can be partial, see snapshot_at.snapshot_info — Returns the snapshot date and source behind the other tools, and which fields are kept or dropped. Example output: {"snapshot_at":"2026-10-3spec_changes_since — Returns what changed in the MCP and A2A specifications since a date, each as a short summary in our own words with a link to the release notdata_freshness — Returns how old these numbers are: the snapshot date, its age in days today (UTC), whether it is older than 7 days, the newest server first Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.