agenteconomy.cloud
REMOTE · MCP.AGENTECONOMY.CLOUD · SCANNED SEP 20
x402 seller trust for AI agents: verify on-chain revenue, check delivery, diagnose listings.
Available components
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · mcp.agenteconomy.cloud
claude mcp add --transport http cloud-agenteconomy-mcp 'https://mcp.agenteconomy.cloud/mcp'
{
"mcpServers": {
"cloud-agenteconomy-mcp": {
"url": "https://mcp.agenteconomy.cloud/mcp"
}
}
} {
"servers": {
"cloud-agenteconomy-mcp": {
"type": "http",
"url": "https://mcp.agenteconomy.cloud/mcp"
}
}
} [mcp_servers.cloud-agenteconomy-mcp] url = "https://mcp.agenteconomy.cloud/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cloud-agenteconomy-mcp": {
"type": "remote",
"url": "https://mcp.agenteconomy.cloud/mcp",
"enabled": true
}
}
} openclaw mcp add cloud-agenteconomy-mcp --url 'https://mcp.agenteconomy.cloud/mcp' --transport streamable-http
mcp_servers:
cloud-agenteconomy-mcp:
url: "https://mcp.agenteconomy.cloud/mcp" {
"McpServers": {
"cloud-agenteconomy-mcp": {
"Transport": "http",
"Url": "https://mcp.agenteconomy.cloud/mcp"
}
}
} assistant mcp add cloud-agenteconomy-mcp -t streamable-http -u 'https://mcp.agenteconomy.cloud/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 8 Sept 26 +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.
- 7 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 6 Sept 26 56
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.agenteconomy.cloud/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenteconomy.cloud | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 116ad94b1923ea0137da24b7140ba62 |
| SANs: agenteconomy.cloud, mcp.agenteconomy.cloud, *.mcp.agenteconomy.cloud | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.agenteconomy.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| agenteconomy.cloud. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agenteconomy.cloud/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.agenteconomy.cloud/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check ~215
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).
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | 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 |
No output schema declared.
No examples provided.
diagnose ~243
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 |
No output schema declared.
No examples provided.
discover ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| need | string | yes | what the buying agent needs |
| network | string | – | CAIP-2 filter, e.g. eip155:8453; default all |
No output schema declared.
No examples provided.
register ~500
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | yes | 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: <id>\nspec_hash: <sha256 hex of the JCS-canonical… |
| spec | object | – | registration-v1.0.0 Q1/Q2 document (start, update_spec) — schema: https://agenteconomy.cloud/schemas/registration-v1.0.0.json |
No output schema declared.
No examples provided.
verify ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| seller | string | yes | 0x… payTo address or 12-hex slug — exactly one seller per call |
No output schema declared.
No examples provided.
What is the agenteconomy.cloud MCP server?
agenteconomy.cloud is an MCP server listed in the public MCP registry as cloud.agenteconomy/mcp. x402 seller trust for AI agents: verify on-chain revenue, check delivery, diagnose listings. This page covers its hosted endpoint (https://mcp.agenteconomy.cloud/mcp).
Is the agenteconomy.cloud MCP server safe to use?
agenteconomy.cloud scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the agenteconomy.cloud MCP server expose?
agenteconomy.cloud exposes 5 tools: discover, verify, check, diagnose, register. Their descriptions and schemas cost roughly 1,228 tokens of context every time the server is loaded.
Does the agenteconomy.cloud MCP server require authentication?
No. We connected to agenteconomy.cloud without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the agenteconomy.cloud MCP server still maintained?
agenteconomy.cloud is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.