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

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `agent-economy-data.onrender.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-bitbucket-markedet-agent-economy-data/agent-economy-data.md), [page](https://verifymcp.io/servers/io-bitbucket-markedet-agent-economy-data/agent-economy-data)

## Channel facts

- Endpoint: `https://agent-economy-data.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http io-bitbucket-markedet-agent-economy-data 'https://agent-economy-data.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-bitbucket-markedet-agent-economy-data": {
      "url": "https://agent-economy-data.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-bitbucket-markedet-agent-economy-data": {
      "type": "http",
      "url": "https://agent-economy-data.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-bitbucket-markedet-agent-economy-data]
url = "https://agent-economy-data.onrender.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-bitbucket-markedet-agent-economy-data --url 'https://agent-economy-data.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-bitbucket-markedet-agent-economy-data:
    url: "https://agent-economy-data.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-bitbucket-markedet-agent-economy-data": {
      "Transport": "http",
      "Url": "https://agent-economy-data.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-bitbucket-markedet-agent-economy-data -t streamable-http -u 'https://agent-economy-data.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-bitbucket-markedet-agent-economy-data": {
      "type": "http",
      "url": "https://agent-economy-data.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 77, +11)

- [security improvement] Transport: fail → pass

### 2026-11-04 (score 66, −10)

- [security regression] Transport: pass → fail

### 2026-11-03 (score 76, +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.

### 2026-11-01 (score 75, +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.

### 2026-10-31 (score 74, 0)

- [security] 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

### 2026-10-30 (score 74, +1)

- [security] 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
- [functional] New tool “data_freshness”

### 2026-10-28 (score 73, +9)

- [security improvement] 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
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [cosmetic] “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

### 2026-10-27 (score 64, +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.

## MCP tools (8)

### `ecosystem_overview` (~104 tokens)

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

### `registry_totals` (~93 tokens)

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

### `new_servers_count_since` (~131 tokens)

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

Input parameters:

- `date` (string): Date as YYYY-MM-DD, for example "2026-10-01". Optional: empty means the last 30 days up to the snapshot date.

### `namespace_types` (~86 tokens)

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

### `daily_new_counts` (~129 tokens)

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

Input parameters:

- `days` (integer): Number of days back from the snapshot date, 1 to 365. Optional, default 30.

### `snapshot_info` (~75 tokens)

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` (~169 tokens)

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

Input parameters:

- `date` (string): Date as YYYY-MM-DD, for example "2026-01-01". Optional: empty means 1 January of the snapshot year.

### `data_freshness` (~100 tokens)

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-bitbucket-markedet-agent-economy-data/agent-economy-data#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 66
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 64
- 2026-10-26: 63
- 2026-10-25: 59

## Common questions

### 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 77 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://agent-economy-data.onrender.com/mcp
- Website: https://markedet.bitbucket.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-bitbucket-markedet-agent-economy-data/agent-economy-data.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-bitbucket-markedet-agent-economy-data/agent-economy-data.json
- HTML version of this page: https://verifymcp.io/servers/io-bitbucket-markedet-agent-economy-data/agent-economy-data