Agent Economy Data

io.bitbucket.markedetPublished by markedet.bitbucket.iov0.3.2Updated Oct 31, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Read-only remote MCP server that returns snapshot counts of MCP servers in the Official MCP Registry plus recent MCP and A2A spec changes.

What you can do
  • Get registry totals split by status, remote transport and package type
  • Count servers first published since a given date, or over the last 7 and 30 days
  • See the split between code-host namespaces and publishers' own domains
  • Pull a ready-to-chart series of new servers per UTC day for 1 to 365 days
  • Check the snapshot date, its age and freshness, and which fields are kept or dropped
  • List curated MCP and A2A specification changes since a date, with release-note links
When to use it
Useful when you want quick, sourced figures on how fast the MCP ecosystem is growing, who publishes servers, or what changed in the MCP and A2A specs, without querying the registry yourself. It is a statistics and changelog view, not a server directory.
Requirements
Remote streamable HTTP endpoint; no authentication, environment variables or headers declared. Network access to the hosted endpoint is required.
Before you install
Numbers are a fixed snapshot, so check data_freshness before relying on them. Counts only, with no server names, and spec changes are a short curated list rather than a full changelog. The data is provided as is, with no affiliation to or endorsement by the Official MCP Registry.

Installation

In SourceWeft

  1. Open Agent Economy Data in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.bitbucket.markedet%2Fagent-economy-data/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-economy-data": {
      "type": "http",
      "url": "https://agent-economy-data.onrender.com/mcp"
    }
  }
}

Tools

8

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?'.

Takes no parameters.

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?'.

Takes no parameters.

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?'.

Parametersdate

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?'.

Takes no parameters.

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'.

Parametersdays

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?'.

Takes no parameters.

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?'.

Parametersdate

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?'.

Takes no parameters.

Version history

5
  1. v0.3.2LatestOct 31, 2026
  2. v0.3.1Oct 29, 2026
  3. v0.3.0Oct 26, 2026
  4. v0.2.1Oct 26, 2026
  5. v0.2.0Oct 25, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.