# agenteconomy.cloud (remote · mcp.agenteconomy.cloud) x402 seller trust for AI agents: verify on-chain revenue, check delivery, diagnose listings. - Trust score: 62/100 (medium) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - remote · `mcp.agenteconomy.cloud`: 62/100 (this document), [markdown](https://verifymcp.io/servers/cloud-agenteconomy-mcp/mcp.md), [page](https://verifymcp.io/servers/cloud-agenteconomy-mcp/mcp) ## Channel facts - Endpoint: `https://mcp.agenteconomy.cloud/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.1.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-20. - **Endpoint Security**: 46/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 62/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 1566 tokens (~313/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 47/100 - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 96/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 89% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 60/100 - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. ## Install ### How do I install the agenteconomy.cloud MCP server? agenteconomy.cloud is a hosted endpoint at https://mcp.agenteconomy.cloud/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http cloud-agenteconomy-mcp 'https://mcp.agenteconomy.cloud/mcp' ``` ### Cursor ```json { "mcpServers": { "cloud-agenteconomy-mcp": { "url": "https://mcp.agenteconomy.cloud/mcp" } } } ``` ### VS Code ```json { "servers": { "cloud-agenteconomy-mcp": { "type": "http", "url": "https://mcp.agenteconomy.cloud/mcp" } } } ``` ### Codex ```toml [mcp_servers.cloud-agenteconomy-mcp] url = "https://mcp.agenteconomy.cloud/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "cloud-agenteconomy-mcp": { "type": "remote", "url": "https://mcp.agenteconomy.cloud/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add cloud-agenteconomy-mcp --url 'https://mcp.agenteconomy.cloud/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: cloud-agenteconomy-mcp: url: "https://mcp.agenteconomy.cloud/mcp" ``` ### Netclaw ```json { "McpServers": { "cloud-agenteconomy-mcp": { "Transport": "http", "Url": "https://mcp.agenteconomy.cloud/mcp" } } } ``` ### Vellum ```bash assistant mcp add cloud-agenteconomy-mcp -t streamable-http -u 'https://mcp.agenteconomy.cloud/mcp' ``` ### Other ```json { "mcpServers": { "cloud-agenteconomy-mcp": { "type": "http", "url": "https://mcp.agenteconomy.cloud/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-19 (score 62, +1) No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-17 (score 61, +1) No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-15 (score 60, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-13 (score 59, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-11 (score 58, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-08 (score 57, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-07 (score 56, 0) - [functional improvement] Stability: unverified → 0.03 ### 2026-09-06 (score 56) First indexed and scored. ## MCP tools (5) ### `discover` (~153 tokens) 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. Input parameters: - `cursor` (string) - `limit` (integer) - `need` (string, required): what the buying agent needs - `network` (string): CAIP-2 filter, e.g. eip155:8453; default all ### `verify` (~117 tokens) 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. Input parameters: - `seller` (string, required): 0x… payTo address or 12-hex slug — exactly one seller per call ### `check` (~215 tokens) 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). Input parameters: - `endpoint` (string, required): https:// resource URL whose x402 payment machinery to test - `expected_payto` (string): optional 0x… address you expect the endpoint to charge to; mismatch is a named finding - `listing_id` (string): optional catalog listing id — compares the advertised payTo against the cataloged seller ### `diagnose` (~243 tokens) 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). Input parameters: - `asserted_price_micro` (integer): your advertised price in micro-USDC — becomes the price basis vs the category median; defaults to the live quote's cheapest recognized entry - `endpoint` (string, required): https:// resource URL of the x402 endpoint to diagnose (pre-catalog endpoints welcome — findability reports honestly) - `expected_payto` (string): optional 0x… address you expect the endpoint to charge to; mismatch is a named finding ### `register` (~500 tokens) 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. Input parameters: - `action` (required): start and renew are paid ($5/30 days); challenge_response, status and update_spec are free - `challenge_id` (string): challenge_response: optional; defaults to the latest issued challenge - `registration_id` (string): from start (all actions after start) - `seller` (string): 0x… payTo address — alternative lookup where registration_id is not at hand - `signature` (string): 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) - `signed_at` (string): update_spec: ISO 8601 timestamp inside the signed text, within 15 minutes of server time — text: "agenteconomy.cloud spec update v1\nregistration_id: \nspec_hash: