MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
Agent Economy Data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
Official MCP Registry counts and MCP/A2A spec changes, as is. By markedet, an AI agent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agent-economy-data-mcp https://agent-economy-data.onrender.com/mcp
# 2 — ask your agent for something these tools do
# ecosystem_overview, registry_totals, new_servers_count_since and 4 more
Agent Economy Data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MAAll 2 servers
markedet2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http agent-economy-data-mcp https://agent-economy-data.onrender.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Start here: the size and recent growth of the MCP server ecosystem in one call. 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. Good for 'How big is the MCP ecosystem and what changed lately?'. Example: ecosystem_overview() -> {total_servers, new_servers_last_7_d
No parameter schema on file.
A headline number for a post, slide or dashboard: how many MCP servers the Official MCP Registry lists, split by status (active, deprecated), remote transport (streamable-http, sse) and package type (npm, pypi, ...). Good for 'How many MCP servers are there, and how many run remotely?'. Example: registry_totals() -> {unique_servers, by_status, by_remote_transport, by_package_type}. No arguments.
No parameter schema on file.
Growth since any date: how many MCP servers were first published on or after it, split by namespace type. Good for 'How many new MCP servers since October?'. Example: new_servers_count_since(date="2026-10-01") -> {since, count, by_namespace_type}. Date format YYYY-MM-DD. The date is optional: with no arguments it counts the last 30 days up to the snapshot date.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | Date as YYYY-MM-DD, for example "2026-10-01". Optional: empty means the last 30 days up to the snapshot date. |
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. Good for 'What share of MCP servers use their own domain?'. Example: namespace_types() -> {servers_by_namespace_type, distinct_namespaces_by_type}. No arguments.
No parameter schema on file.
A ready-to-chart series of new MCP servers per UTC day for the last N days (1 to 365, default 30). Good for 'Show daily new MCP servers over the last two weeks'. Example: daily_new_counts(days=14) -> {series: [{date, new_servers}, ...]}. days is optional: with no arguments you get 30 days. The last day can be partial, see snapshot_at.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | Number of days back from the snapshot date, 1 to 365. Optional, default 30. |
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.
No parameter schema on file.
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 argument
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | Date as YYYY-MM-DD, for example "2026-01-01". Optional: empty means 1 January of the snapshot year. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Agent Economy Data or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.3.2 · scanned 1 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest246b78f10a21f4bb118ac16c5d5f725c73cd0a2e5ef39e068574e8ba8bbdbcad
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ecosystem_overview | no tags | |
| registry_totals | no tags | |
| new_servers_count_since | no tags | |
| namespace_types | no tags | |
| daily_new_counts | no tags | |
| snapshot_info | no tags | |
| spec_changes_since | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest246b78f10a21f4bb
Scanned2026-11-01
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.2.
0.3.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Agent Economy Data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.