agenteconomy.cloud
cloud.agenteconomy/mcpVersion 1.1.0x402 seller trust for AI agents: verify on-chain revenue, check delivery, diagnose listings.
Status
Responds128 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:42 UTC
- Latency
- 128 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.agenteconomy.cloud/mcpResponds128 msNo sign-in
Claude Code
claude mcp add --transport http agenteconomy https://mcp.agenteconomy.cloud/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: agenteconomy
Remote MCP server URL: https://mcp.agenteconomy.cloud/mcpCursor
{
"mcpServers": {
"agenteconomy": {
"url": "https://mcp.agenteconomy.cloud/mcp"
}
}
}VS Code
code --add-mcp '{"name":"agenteconomy","type":"http","url":"https://mcp.agenteconomy.cloud/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
5 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
checkPAID $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). | Not declared | Not declared | Not declared | Not declared |
diagnosePAID $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). | Not declared | Not declared | Not declared | Not declared |
discoverFREE (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. | Not declared | Not declared | Not declared | Not declared |
registerSupply-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. | Not declared | Not declared | Not declared | Not declared |
verifyPAID $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. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Sep 6, 2026
- Updated
- Sep 6, 2026
- Categories (suggested)
- Cloud and infrastructureE-commerceSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared