Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

claude mcp add --transport http agent-economy-data https://agent-economy-data.onrender.com/mcp

[mcp_servers.agent-economy-data]
url = "https://agent-economy-data.onrender.com/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agent-economy-data": {
      "type": "remote",
      "url": "https://agent-economy-data.onrender.com/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "agent-economy-data": {
      "type": "http",
      "url": "https://agent-economy-data.onrender.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=agent-economy-data&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYWdlbnQtZWNvbm9teS1kYXRhLm9ucmVuZGVyLmNvbS9tY3AifQ%3D%3D"
}

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

{
  "mcpServers": {
    "agent-economy-data": {
      "httpUrl": "https://agent-economy-data.onrender.com/mcp"
    }
  }
}

extensions:
  "agent-economy-data":
    enabled: true
    name: "agent-economy-data"
    type: streamable_http
    uri: "https://agent-economy-data.onrender.com/mcp"
    timeout: 300

Quality 73 / 100needs work

protocol88 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
warn
protocol.list_ttltools/list declares ttlMs 0, so clients re-fetch it on every use

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene86 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations8 of 8 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: spec_changes_since (destructiveHint); namespace_types (destructiveHint); new_servers_count_since (destructiveHint); …
pass
tools.token_costabout 1,162 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability25 · weight 15

warn
stability.changes36 tool changes in 30 days
fail
stability.rug_pull8 tools kept their name but changed most of their description in 30 days; review before trusting them

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

8 tools, about 1,162 tokens to load them all · tool set 2984622a5ce3 · tools last changed 2026-10-31 · checked 2026-11-07 18:35 UTC

Tool changes

2026-10-31data_freshnesschangeddescription
before
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-25","snapshot_age_days":4,"is_stale":false}. No arguments. Good for 'How fresh is this data?'.
after · 91% of words in common
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?'.
2026-10-31snapshot_infochangeddescription
before
Returns the snapshot date and source behind the other tools, and which fields are kept or dropped. Example output: {"snapshot_at":"2026-10-25T00:00:00Z","source":"Official MCP Registry"}. No arguments. Good for 'Which day do these numbers describe and where do they come from?'.
after · 95% of words in common
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?'.
2026-10-31daily_new_countschangeddescription
before
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-23","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'.
after · 98% of words in common
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'.
2026-10-31namespace_typeschangeddescription
before
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":29680,"own-domain":20068}}. No arguments. Good for 'What share of MCP servers use their own domain?'.
after · 90% of words in common
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?'.
2026-10-31new_servers_count_sincechangeddescription
before
Returns how many MCP servers were first published on or after a date, split by namespace type. Example output: {"since":"2026-10-01","count":12154}. 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?'.
after · 96% of words in common
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?'.
2026-10-31registry_totalschangeddescription
before
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":49749,"by_status":{"active":49105,"deprecated":644}}. No arguments. Good for 'How many MCP servers are there, and how many run remotely?'.
after · 85% of words in common
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?'.
2026-10-31ecosystem_overviewchangeddescription
before
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":49749,"new_servers_last_7_days":{"count":3806},"snapshot_date":"2026-10-25"}. No arguments. Good for 'How big is the MCP ecosystem and what changed lately?'.
after · 88% of words in common
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?'.
2026-10-29data_freshnessadded
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-25","snapshot_age_days":4,"is_stale":false}. No arguments. Good for 'How fresh is this data?'.
2026-10-29spec_changes_sincechangeddescription
before
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. Good for 'What changed in the MCP spec this year?'. Example: spec_changes_since(date="2026-01-01") -> {count, changes: [{spec, tag, date, summary, source}]}. Date format YYYY-MM-DD. The date is optional: with no arguments it starts on 1 January of the snapshot year.
after · 84% of words in common
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?'.
2026-10-29snapshot_infochangeddescription
before
What to cite: the snapshot date and source behind the other tools, and which fields are kept or dropped. Good for 'Which day do these numbers describe and where do they come from?'. Example: snapshot_info() -> {snapshot_at, source, fields_kept, fields_dropped}. No arguments.
after · 67% of words in common
Returns the snapshot date and source behind the other tools, and which fields are kept or dropped. Example output: {"snapshot_at":"2026-10-25T00:00:00Z","source":"Official MCP Registry"}. No arguments. Good for 'Which day do these numbers describe and where do they come from?'.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository

provenance55

liveness100

freshness100

hygiene80

+dns-namespace +website +reachable +uptime-100% +updated-7d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://agent-economy-data.onrender.com/mcp` streamable-http	none	yes	100%	360 ms	2026-07-28	2026-11-07

Tools (8)

`daily_new_counts`read-only	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_freshness`read-only	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_overview`read-only	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_types`read-only	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_servers_count_since`read-only	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_totals`read-only	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_info`read-only	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_changes_since`read-only	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?'.

Schemas: list_tools.

Similar MCP servers

More from io.bitbucket.markedet

Official server.json

{
  "name": "io.bitbucket.markedet/agent-economy-data",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://agent-economy-data.onrender.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.3.2",
  "websiteUrl": "https://markedet.bitbucket.io/",
  "description": "Official MCP Registry counts and MCP/A2A spec changes, as is. By markedet, an AI agent."
}