mcpbeat Sign in

agenteconomy.cloud MCP Server

by agenteconomy Your server? Claim it
answering

agenteconomy.cloud is answering right now. Last checked 11 min ago. It exposes 5 tools. Last commit 6 Sep 2026.

x402 seller trust for AI agents: verify on-chain revenue, check delivery, diagnose listings.

Uptime history 57 days of history · worst day 92%
57 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
142 ms
Response time
average over 24h
0
Stars
last commit 6 Sep 2026

agenteconomy.cloud missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.agenteconomy.cloud/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.agenteconomy.cloud/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.agenteconomy.cloud/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.agenteconomy.cloud/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.agenteconomy.cloud/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

check
check
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-only: depth 'quote_only' with the cap disclosed in gates. One signed payment_flow_conformance verdict out (verdict-v1.1.0).
diagnose
diagnose
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 revenue, median on-chain payment vs your price basis) and competition — then ONE primary blocker under a frozen disclosed precedence. One signed seller_diagnostic verdict out (verdict-v1.1.0).
discover
discover
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 contract and pay the seller directly.
register
register
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, and tier/rank/verdicts never move with it: registration adds claims-labeled data. SPEND-CAP WARNING: $5 = 5000000 micro-USDC is above the $1 default per-call cap many x402 clients ship — raise your client cap for start/renew or it will refuse to sign. Flow: start (submit spec, pay, receive a 72h challenge) → challenge_response (submit the payTo key’s EIP-191 signature; the audit runs) → registered while paid_through holds. renew re-audits and extends 30 days; renewal grace 7 days after paid_through — the mark itself drops at paid_through exactly.
verify
verify
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.agenteconomy.cloud/mcp streamable-http answering 100 ms 11 min ago

Alternatives to agenteconomy.cloud

same job, measured the same way
Pulsefeed X402
by nikolife2016

Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.

103 installs/wk 11 tools answering
Agent Notary
by jdhart81

Verifiable delivery for the agent economy: commit-reveal content notarization. Sellers commit to a d

8 tools answering
verify402
by a32116150-ctrl

Free x402 preflight gate plus paid on-chain truth checks for AI agents.

1 027 installs/wk local only
Djd Agent Score
by jacobsd32-cpu

Reputation scoring for AI agent wallets on Base. Trust scores, fraud checks, x402.

39 installs/wk local only
Dokimo MCP
by ypratap11

Verify AI-agent revenue: recompute a Merkle proof and check it against an on-chain anchor.

3 tools answering
AI Agent Analytics
by davisvillelabs

Seller-side analytics for AI-agent discovery, settled revenue, delivery, and repeat use.

3 tools answering
Aegis
by borisinc

Trust layer for the x402 economy - check any service before you pay. Scores, discovery, routing.

8 tools answering
TWZRD Agent Intelligence
by twzrd-intel

Pre-spend trust for AI agents that buy: check x402 services and product listings before paying.

193 installs/wk 28 tools answering

agenteconomy.cloud — questions

Answers built from our own checks of this server.

What can agenteconomy.cloud do?
It exposes 5 tools, read directly from the server on our last check. Among them: check, diagnose, discover, register, verify. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is agenteconomy.cloud working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 142 ms. The bar chart above shows every period we have measured.
How do I connect agenteconomy.cloud?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does agenteconomy.cloud need an API key?
No. agenteconomy.cloud completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is agenteconomy.cloud?
It answers our handshake in 142 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is agenteconomy.cloud open source?
We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.