# `io.bitbucket.markedet/agent-economy-data` on Anlyon Radar

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by Anlyon Radar. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://radar.anlyon.com/servers/io.bitbucket.markedet/agent-economy-data
- JSON: https://radar.anlyon.com/api/v1/servers/io.bitbucket.markedet/agent-economy-data
- Version: 0.5.2 (active)
- Publisher: io.bitbucket.markedet (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Metadata from the official MCP Registry, synced 2026-11-11T08:17:43.965Z

Title and description, as the publisher wrote them:

```untrusted-server-text
MCP server counts from the official registry, new servers per day, and MCP/A2A spec changes. As is.
```

Scanned 2026-11-11T08:18:12.403Z over streamable-http.

**8 tools: 1 change things and 7 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 1 | ask |
| Only reads | read | 7 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | `mcp__agent-economy-data__spec_changes_since` |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | `mcp__agent-economy-data__registry_totals` |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

- **warn** Annotations that disagree with the tool in `namespace_types` ([annotation-conflict](https://radar.anlyon.com/methodology#annotation-conflict))

```untrusted-server-text
The server marks "namespace_types" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "namespace_types" says "type": a word for a change.
```


## Changes things (1)

Creates or changes something that can be changed back. Claude Code: ask.

### `namespace_types`

- The name "namespace_types" says "type": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
- Findings: warn annotation-conflict

Description, as the server wrote it:

```untrusted-server-text
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?'.
```

## Only reads (7)

Looks things up and changes nothing. Claude Code: allow.

### `daily_new_counts`

- The name "daily_new_counts" says "count": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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`

- The description's first verb is "return": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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`

- The description's first verb is "return": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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?'.
```

### `new_servers_count_since`

- The name "new_servers_count_since" says "count": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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`

- The description's first verb is "return": a word for reading.
- Tag untrusted-input: The description's first sentence says "return" and "http": it reads web pages, which anyone can write.

Description, as the server wrote it:

```untrusted-server-text
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`

- The name "snapshot_info" says "snapshot": a word for reading.

Description, as the server wrote it:

```untrusted-server-text
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`

- The description's first verb is "return": a word for reading.
- Tag private-data: The description's first sentence says "return" and "note": it reads notes.

Description, as the server wrote it:

```untrusted-server-text
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?'.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `agent-economy-data`:

```json
{
  "permissions": {
    "allow": [
      "mcp__agent-economy-data__ecosystem_overview",
      "mcp__agent-economy-data__registry_totals",
      "mcp__agent-economy-data__new_servers_count_since",
      "mcp__agent-economy-data__daily_new_counts",
      "mcp__agent-economy-data__snapshot_info",
      "mcp__agent-economy-data__spec_changes_since",
      "mcp__agent-economy-data__data_freshness"
    ],
    "ask": [
      "mcp__agent-economy-data__namespace_types"
    ],
    "deny": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `mcp__agent-economy-data__registry_totals`: untrusted-input
- `mcp__agent-economy-data__spec_changes_since`: private-data

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-16T14:23:02.280Z, unchanged since 2026-11-16T14:23:02.280Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://radar.anlyon.com/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| Reachable | `yes` |
| HTTP status of an anonymous initialize | `200` |
| tools/list served without credentials | `yes` |
| Tools that change things, listed without credentials | `1` |
| Protocol version | `2025-06-18` |
| WWW-Authenticate on 401 | `not observed` |
| resource_metadata in WWW-Authenticate | `none` |
| RFC 9728 protected resource metadata | `none` |
| Authorization servers | `none` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `not observed` |
| Client ID metadata documents | `not observed` |

- **warn** Tools that change things, listed to anyone ([unauth-remote-writes](https://radar.anlyon.com/methodology#unauth-remote-writes))

```untrusted-server-text
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

https://unstuckagents.com/mcp: tools/list returned 8 tools to an anonymous client, including namespace_types (write)
```

Posture changes:

- 2026-11-02T00:20:46.687Z: Tools that change things, listed without credentials `3` -> `1`
