Skip to content

agent-economy-data MCP server

io.bitbucket.markedet/agent-economy-datamarkedet.bitbucket.iostreamable-httpv0.5.2Scanned

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

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the agent-economy-data MCP server can do

The agent-economy-data MCP server is published by markedet.bitbucket.io, a domain the MCP Registry verified. It has 8 tools. It can create or change data (1 tool: namespace_types), but cannot delete data. 7 tools only read.

1 tool reads private data (spec_changes_since); 1 tool brings in text other people can write (registry_totals).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 0.5.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 1Claude Code: ask
  • namespace_typesReturns 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 names…1 finding

    Why it is in this group

    • 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

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 7Show 7 read-only tools
  • daily_new_countsReturns a ready-to-chart series of new MCP servers per UTC day for the last N days (1 to 365).No findings

    Why it is in this group

    • The name "daily_new_counts" says "count": a word for reading.
    Description, as the server wrote it
    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'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • data_freshnessReturns 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 …No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • ecosystem_overviewReturns 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 d…No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • new_servers_count_sinceReturns how many MCP servers were first published on or after a date, split by namespace type.No findings

    Why it is in this group

    • The name "new_servers_count_since" says "count": a word for reading.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • registry_totalsReturns how many MCP servers the Official MCP Registry lists, split by status (active, deprecated), remote transport (streamable-http, sse) and package type (npm, pypi, ...).Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • snapshot_infoReturns the snapshot date and source behind the other tools, and which fields are kept or dropped.No findings

    Why it is in this group

    • The name "snapshot_info" says "snapshot": a word for reading.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • spec_changes_sinceReturns 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.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    Description, as the server wrote it
    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?'.

    Annotations the server declares

    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

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

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:23 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

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
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    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.

    Matched text

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

    What this check looks for

Posture changes

  1. Nov 2, 2026
    • Tools that change things, listed without credentials: 3 to 1

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

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

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools7 changed.~7 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 1.View diff
    • Tools that change things, listed without credentials: 3 to 1
  3. Tools1 added, 7 changed.+1 added~7 changedView diff
  4. Tools7 changed.~7 changedView diff
  5. Tools1 added.+1 addedView diff
  6. Tools6 changed.~6 changedView diff

Install

Pinned to version 0.5.2. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.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": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-economy-data. Review it before you use it.

Capability tags behind 2 rules
  • mcp__agent-economy-data__registry_totals untrusted-input
  • mcp__agent-economy-data__spec_changes_since private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.bitbucket.markedet/agent-economy-data/verify?hash=35ddea715d76bd7b4f83050b26f13ab1a2c18f6901b0dcf3d29b96b3381a4c8d" | jq -e '.changed == false'

Pinned hash 35ddea715d76, from Nov 11, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.bitbucket.markedet/agent-economy-data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.bitbucket.markedet/agent-economy-data
[![Anlyon Radar](https://radar.anlyon.com/badge/io.bitbucket.markedet/agent-economy-data.svg)](https://radar.anlyon.com/servers/io.bitbucket.markedet/agent-economy-data)

Source: MCP Registry. Synced Nov 11, 2026, 08:17 UTC.

agent-economy-data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the agent-economy-data MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the agent-economy-data MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the agent-economy-data MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the agent-economy-data MCP server have?

8 tools: 1 write, 7 read. namespace_types, ecosystem_overview, registry_totals, new_servers_count_since, daily_new_counts, snapshot_info, spec_changes_since and data_freshness.

Does the agent-economy-data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the agent-economy-data MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the agent-economy-data MCP server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.