Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Nothing to run from here
agenteconomy.cloud 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.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
x402 seller trust for AI agents: verify on-chain revenue, check delivery, diagnose listings.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agenteconomy-cloud-mcp https://mcp.agenteconomy.cloud/mcp
# 2 — ask your agent for something these tools do
# discover, verify, check and 2 more
agenteconomy.cloud costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AGAll 1 server
agenteconomy1 server
1 category
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 agenteconomy-cloud-mcp https://mcp.agenteconomy.cloud/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
5 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.
FREE (rate-limited: 10/min burst, 120/hour per IP). Text of what you need in → sellers out with chain evidence (tier, verified revenue windows, real-buyer counts, on-chain-observed median price), the seller’s endpoint and payment details, their description and capability category (seller-asserted/auto-assigned claims, source-labeled), and their registered spec where one exists. Referral-only: you
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | yes | what the buying agent needs |
| network | string | no | CAIP-2 filter, e.g. eip155:8453; default all |
| limit | integer | no | — |
| cursor | string | no | — |
PAID $0.10/call (x402, mcp-pricing-v1.1). Seller address or slug in → one signed seller_trust verdict out: the frozen score-v1.0.0 predicate re-evaluated at issuance, the chain evidence it rests on, exclusions applied, and full provenance — recomputable by anyone. Ed25519-signed over RFC 8785 canonical JSON.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| seller | string | yes | 0x… payTo address or 12-hex slug — exactly one seller per call |
PAID $0.25/call (x402, mcp-pricing-v1.1). Level-1 payment-flow conformance against a live x402 endpoint: quote (402 + parseable v2 PAYMENT-REQUIRED), requirements (accepts[] validity; payTo vs catalog/registration/expected_payto is a named finding), then a REAL probe purchase from our own wallet when an 'exact' entry on our rail advertises ≤ $0.05, and delivery-of-something. Above the cap or upto-
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | string | yes | https:// resource URL whose x402 payment machinery to test |
| listing_id | string | no | optional catalog listing id — compares the advertised payTo against the cataloged seller |
| expected_payto | string | no | optional 0x… address you expect the endpoint to charge to; mismatch is a named finding |
PAID $1.00/call (x402, mcp-pricing-v1.1). Seller-side funnel diagnosis for one x402 endpoint, as data: findability (catalog presence, listing age, description quality, capability-v1 category), conformance (check's real flow — quote, requirements, a REAL probe purchase when an 'exact' entry on our rail advertises ≤ $0.05, settle, deliver), category demand (verified earners, seller-deduped 30d reven
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | string | yes | https:// resource URL of the x402 endpoint to diagnose (pre-catalog endpoints welcome — findability reports honestly) |
| asserted_price_micro | integer | no | your advertised price in micro-USDC — becomes the price basis vs the category median; defaults to the live quote's cheapest recognized entry |
| expected_payto | string | no | optional 0x… address you expect the endpoint to charge to; mismatch is a named finding |
Supply-side registration: $5 / 30 days (x402, mcp-pricing-v1.1) for actions start and renew; actions challenge_response, status and update_spec are free. You pay to be EXAMINED (EIP-191 ownership challenge + endpoint 402-conformance + registration-v1.0.0 schema validation) and can pay and fail — the fee buys the examination, never the outcome. Presence in discover is never gated by registration, a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | yes | start and renew are paid ($5/30 days); challenge_response, status and update_spec are free | |
| spec | object | no | registration-v1.0.0 Q1/Q2 document (start, update_spec) — schema: https://agenteconomy.cloud/schemas/registration-v1.0.0.json |
| registration_id | string | no | from start (all actions after start) |
| seller | string | no | 0x… payTo address — alternative lookup where registration_id is not at hand |
| signature | string | no | challenge_response: EIP-191 personal_sign of the exact challenge_text by the payTo key — 0x + 130 hex (r||s||v). update_spec: same signer over the spec-update text (see signed_at) |
| challenge_id | string | no | challenge_response: optional; defaults to the latest issued challenge |
| signed_at | string | no | update_spec: ISO 8601 timestamp inside the signed text, within 15 minutes of server time — text: "agenteconomy.cloud spec update v1 registration_id: <id> spec_hash: <sha256 hex of the JCS-canonical |
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 agenteconomy.cloud 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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 1.1.0.
1.1.0
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 agenteconomy.cloud 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.