accueil / serveurs / Finance & Paiement / cloud.agenteconomy/mcp
cloud.agenteconomy/mcp
serveur MCP (Model Context Protocol) · agenteconomy-mcp 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que cloud.agenteconomy/mcp est sûr ?
Au dernier audit MCP Hub, le serveur MCP « cloud.agenteconomy/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 5 outils
- check≈ 270 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).
Paramètres, retour & exemple (3)
Paramètresendpoint· string · requis
https:// resource URL whose x402 payment machinery to testlisting_id· string · optionnel
optional catalog listing id — compares the advertised payTo against the cataloged sellerexpected_payto· string · optionnel
optional 0x… address you expect the endpoint to charge to; mismatch is a named finding
Exemple d'appel{"name": "check", "arguments": {"endpoint": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - diagnose≈ 320 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).
Paramètres, retour & exemple (3)
Paramètresendpoint· string · requis
https:// resource URL of the x402 endpoint to diagnose (pre-catalog endpoints welcome — findability reports honestly)expected_payto· string · optionnel
optional 0x… address you expect the endpoint to charge to; mismatch is a named findingasserted_price_micro· integer · optionnel
your advertised price in micro-USDC — becomes the price basis vs the category median; defaults to the live quote's cheapest recognized entry
Exemple d'appel{"name": "diagnose", "arguments": {"endpoint": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - discover≈ 222 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.
Paramètres, retour & exemple (4)
Paramètresneed· string · requis
what the buying agent needslimit· integer · optionnelcursor· string · optionnelnetwork· string · optionnel
CAIP-2 filter, e.g. eip155:8453; default all
Exemple d'appel{"name": "discover", "arguments": {"need": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - register≈ 582 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.
Paramètres, retour & exemple (7)
Paramètresspec· object · optionnel
registration-v1.0.0 Q1/Q2 document (start, update_spec) — schema: https://agenteconomy.cloud/schemas/registration-v1.0.0.jsonaction· enum · requis · start | challenge_response | status | update_spec | renew
start and renew are paid ($5/30 days); challenge_response, status and update_spec are freeseller· string · optionnel
0x… payTo address — alternative lookup where registration_id is not at handsignature· string · optionnel
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 · optionnel
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 new spec>\nsigned_at: <this value>"challenge_id· string · optionnel
challenge_response: optional; defaults to the latest issued challengeregistration_id· string · optionnel
from start (all actions after start)
Exemple d'appel{"name": "register", "arguments": {"action": "start"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - verify≈ 141 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.
Paramètres, retour & exemple (1)
Paramètresseller· string · requis
0x… payTo address or 12-hex slug — exactly one seller per call
Exemple d'appel{"name": "verify", "arguments": {"seller": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».