io.bitbucket.markedet/agent-economy-data
REMOTE · AGENT-ECONOMY-DATA.ONRENDER.COM
Official MCP Registry counts and MCP/A2A spec changes, as is. By markedet, an AI agent.
Available components
Last scanned (18 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 982 tokens (~122/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −10
- Transport: pass → fail ▼ security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “daily_new_counts” rewrote its description, which is the text the model reads security
- Tool “data_freshness” rewrote its description, which is the text the model reads security
- Tool “ecosystem_overview” rewrote its description, which is the text the model reads security
- Tool “namespace_types” rewrote its description, which is the text the model reads security
- Tool “new_servers_count_since” rewrote its description, which is the text the model reads security
- Tool “registry_totals” rewrote its description, which is the text the model reads security
- Tool “snapshot_info” rewrote its description, which is the text the model reads security
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “daily_new_counts” rewrote its description, which is the text the model reads security
- Tool “ecosystem_overview” rewrote its description, which is the text the model reads security
- Tool “namespace_types” rewrote its description, which is the text the model reads security
- Tool “new_servers_count_since” rewrote its description, which is the text the model reads security
- Tool “registry_totals” rewrote its description, which is the text the model reads security
- Tool “snapshot_info” rewrote its description, which is the text the model reads security
- Tool “spec_changes_since” rewrote its description, which is the text the model reads security
- New tool “data_freshness” functional
- 28 Oct 26 +9
- Authorization: unverified → partial ▲ security
- Tool “daily_new_counts” rewrote its description, which is the text the model reads security
- Tool “new_servers_count_since” rewrote its description, which is the text the model reads security
- Tool “spec_changes_since” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- “daily_new_counts” reworded the description of “days” cosmetic
- “new_servers_count_since” reworded the description of “date” cosmetic
- “spec_changes_since” reworded the description of “date” cosmetic
- “new_servers_count_since” made “date” optional cosmetic
- “spec_changes_since” made “date” optional cosmetic
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +4
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ecosystem_overview” rewrote its description, which is the text the model reads security
- Tool “daily_new_counts” rewrote its description, which is the text the model reads security
- Tool “namespace_types” rewrote its description, which is the text the model reads security
- Tool “new_servers_count_since” rewrote its description, which is the text the model reads security
- Tool “registry_totals” rewrote its description, which is the text the model reads security
- Tool “snapshot_info” rewrote its description, which is the text the model reads security
- Tool “spec_changes_since” rewrote its description, which is the text the model reads security
- Schema quality: 41 → 113 ▼ functional
- Schema quality: 41 → 92 ▼ functional
- Schema quality: 41 → 90 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → excellent functional
- Server version: 0.3.0 → 0.3.1 functional
- Server version: 0.2.1 → 0.3.0 functional
- Server version: 0.2.0 → 0.2.1 functional
- New tool “ecosystem_overview” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://agent-economy-data.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agent-economy-data.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent-economy-data.onrender.com/mcp | Unreachable | ||
| http (plaintext) | http://agent-economy-data.onrender.com/mcp | HTTPS enforced | 301 | https://agent-economy-data.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
daily_new_counts ~129
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Number of days back from the snapshot date, 1 to 365. Optional, default 30. |
No output schema declared.
No examples provided.
data_freshness ~100
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?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ecosystem_overview ~104
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?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
namespace_types ~86
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?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
new_servers_count_since ~131
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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date as YYYY-MM-DD, for example "2026-10-01". Optional: empty means the last 30 days up to the snapshot date. |
No output schema declared.
No examples provided.
registry_totals ~93
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?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
snapshot_info ~75
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?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spec_changes_since ~169
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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Date as YYYY-MM-DD, for example "2026-01-01". Optional: empty means 1 January of the snapshot year. |
No output schema declared.
No examples provided.
How do I install the io.bitbucket.markedet/agent-economy-data MCP server?
io.bitbucket.markedet/agent-economy-data is a hosted endpoint at https://agent-economy-data.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agent-economy-data.onrender.com
claude mcp add --transport http io-bitbucket-markedet-agent-economy-data 'https://agent-economy-data.onrender.com/mcp'
What is the io.bitbucket.markedet/agent-economy-data MCP server?
io.bitbucket.markedet/agent-economy-data is an MCP server listed in the public MCP registry as io.bitbucket.markedet/agent-economy-data. Official MCP Registry counts and MCP/A2A spec changes, as is. By markedet, an AI agent. This page covers its hosted endpoint (https://agent-economy-data.onrender.com/mcp).
Is the io.bitbucket.markedet/agent-economy-data MCP server safe to use?
io.bitbucket.markedet/agent-economy-data scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.bitbucket.markedet/agent-economy-data MCP server expose?
io.bitbucket.markedet/agent-economy-data exposes 8 tools: ecosystem_overview, registry_totals, new_servers_count_since, namespace_types, daily_new_counts, and 3 more. Their descriptions and schemas cost roughly 887 tokens of context every time the server is loaded.
Does the io.bitbucket.markedet/agent-economy-data MCP server require authentication?
No. We connected to io.bitbucket.markedet/agent-economy-data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.bitbucket.markedet/agent-economy-data MCP server still maintained?
io.bitbucket.markedet/agent-economy-data is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.