mcpbeat Sign in

Agent Economy Data MCP Server

by bitbucket-markedet Your server? Claim it
answering

Agent Economy Data is answering right now. Last checked 12 min ago. It exposes 8 tools.

Official MCP Registry counts and MCP/A2A spec changes, as is. By markedet, an AI agent.

Uptime history 9 days of history · worst day 97%
9 days agonow
97.8%
Uptime 24h
89 of 91 checks
8
Tools
read from the server
114 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 31

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 26 October 2026. No other catalogue keeps this.

29 Oct 7 tool descriptions were rewritten daily_new_counts, ecosystem_overview, namespace_types and 4 more
29 Oct a tool appeared data_freshness
28 Oct 3 tools changed the parameters they ask for daily_new_counts, new_servers_count_since, spec_changes_since
28 Oct 3 tool descriptions were rewritten daily_new_counts, new_servers_count_since, spec_changes_since
26 Oct 7 tool descriptions were rewritten13 times that day daily_new_counts, ecosystem_overview, namespace_types and 4 more
26 Oct a tool changed version3 times that day
26 Oct a tool appeared ecosystem_overview
and 8 more, back to 26 October 2026

Agent Economy Data does not always answer

Over the last week it answered 98.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add agent-economy-data --transport http https://agent-economy-data.onrender.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://agent-economy-data.onrender.com/mcp
~/.codex/config.toml
[mcp_servers.agent-economy-data]
url = "https://agent-economy-data.onrender.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-economy-data": {
      "url": "https://agent-economy-data.onrender.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agent-economy-data": {
      "type": "http",
      "url": "https://agent-economy-data.onrender.com/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

daily
daily_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. Example output: {"days":3,"series":[{"date":"2026-10-30","new_servers":551}]}. Optional argument: days, default 30. With no arguments you get 30 days. Good for 'Show daily new MCP servers over the last two weeks'.
data
data_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 publish date and the newest spec change date in the data, and how the data is refreshed. Example output: {"snapshot_date":"2026-10-31","snapshot_age_days":0,"is_stale":false}. No arguments. Good for 'How fresh is this data?'.
ecosystem
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 changes with source links, and the snapshot date. Example output: {"total_servers":53618,"new_servers_last_7_days":{"count":4044},"snapshot_date":"2026-10-31"}. No arguments. Good for 'How big is the MCP ecosystem and what changed lately?'.
namespace
namespace_types
Returns who publishes MCP servers and how: the split between code host namespaces (io.github, io.gitlab, io.bitbucket) and publishers' own domains, by servers and by distinct namespaces. Example output: {"servers_by_namespace_type":{"io.github":31407,"own-domain":22209}}. No arguments. Good for 'What share of MCP servers use their own domain?'.
new
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":16045}. Optional argument: date as YYYY-MM-DD, for example "2026-10-01". With no arguments it counts the last 30 days up to the snapshot date. Good for 'How many new MCP servers since October?'.
registry
registry_totals
Returns how many MCP servers the Official MCP Registry lists, split by status (active, deprecated), remote transport (streamable-http, sse) and package type (npm, pypi, ...). Example output: {"unique_servers":53618,"by_status":{"active":52778,"deprecated":840}}. No arguments. Good for 'How many MCP servers are there, and how many run remotely?'.
snapshot
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-31T00:00:00Z","source":"Official MCP Registry"}. No arguments. Good for 'Which day do these numbers describe and where do they come from?'.
spec
spec_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 notes. A short curated list, not a full changelog. Example output: {"since":"2026-01-01","count":4,"changes":[{"spec":"MCP specification","tag":"2026-07-28"}]}. Optional argument: date as YYYY-MM-DD, for example "2026-01-01". With no arguments it starts on 1 January of the snapshot year. Good for 'What changed in the MCP spec this year?'.

Endpoints

URLTransportStateLatencyChecked
https://agent-economy-data.onrender.com/mcp streamable-http answering 148 ms 12 min ago

Alternatives to Agent Economy Data

same job, measured the same way
xOmniMarket
by wjabrac

Search AI capabilities across AWS Marketplace and the Official MCP Registry.

7 tools answering
Recordwire
by brianvia

U.S. business-registry data and change events from official state sources, for agents.

8 tools answering
SupplyGraph.AI Data
by supplygraphai

Official SupplyGraph.AI data MCP: POIs, parks, regions, industry chains, and companies.

198 tools answering
Fuentio: UK, France & Spain company data from official registries
by fuentio

Official UK, France and Spain company checks for AI agents

19 tools answering
Registry MCP
by remote-mcp

An MCP server that serves informtaion from the official MCP registry

2 tools answering
ID MANDAT – Registry for AI Agents
by idmandat

Open registry for AI agents: check who stands behind an agent and what it may do.

4 tools answering
MCP Registry Server
by com-mcp

Publish and discover MCP servers via the official MCP Registry. Powered by HAPI MCP server.

3 tools answering
Capital Markets Agents: MCP+A2A
by allooloo

KYP Agentic Trading: listed-issuer records served in-country, and AIO-10060 orderability outcomes.

7 tools answering

Agent Economy Data — questions

Answers built from our own checks of this server.

What can Agent Economy Data do?
It exposes 8 tools, read directly from the server on our last check. Among them: daily_new_counts, data_freshness, ecosystem_overview, namespace_types, new_servers_count_since, registry_totals and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Agent Economy Data working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 114 ms. The bar chart above shows every period we have measured.
How do I connect Agent Economy Data?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Agent Economy Data need an API key?
No. Agent Economy Data completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Economy Data?
It answers our handshake in 114 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.