agenteconomy.cloud

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
97%
Naming quality
88%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,432Tokens (tool definitions)
~1.7 KBTypical response size
Moderate attention impact (1.12% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.agenteconomy.cloud/mcp"
    }
  }
}

Remote endpoints

https://mcp.agenteconomy.cloud/mcpstreamable-http

What it can do

Tool inventory

Tools (5)

🟒 Read-only🟑 WriteπŸ”΄ Deleteβšͺ Unknown
βšͺdiscover(need, network, limit, cursor)

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 Schema

{
  "type": "object",
  "properties": {
    "need": {
      "type": "string",
      "minLength": 1,
      "maxLength": 500,
      "description": "what the buying agent needs"
    },
    "network": {
      "type": "string",
      "description": "CAIP-2 filter, e.g. eip155:8453; default all"
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20,
      "default": 10
    },
    "cursor": {
      "type": "string"
    }
  },
  "required": [
    "need"
  ],
  "additionalProperties": false
}
βšͺverify(seller)

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 Schema

{
  "type": "object",
  "properties": {
    "seller": {
      "type": "string",
      "description": "0x… payTo address or 12-hex slug β€” exactly one seller per call"
    }
  },
  "required": [
    "seller"
  ],
  "additionalProperties": false
}
🟒check(endpoint, listing_id, expected_payto)

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 Schema

{
  "type": "object",
  "properties": {
    "endpoint": {
      "type": "string",
      "maxLength": 500,
      "description": "https:// resource URL whose x402 payment machinery to test"
    },
    "listing_id": {
      "type": "string",
      "description": "optional catalog listing id β€” compares the advertised payTo against the cataloged seller"
    },
    "expected_payto": {
      "type": "string",
      "description": "optional 0x… address you expect the endpoint to charge to; mismatch is a named finding"
    }
  },
  "required": [
    "endpoint"
  ],
  "additionalProperties": false
}
βšͺdiagnose(endpoint, asserted_price_micro, expected_payto)

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 Schema

{
  "type": "object",
  "properties": {
    "endpoint": {
      "type": "string",
      "maxLength": 500,
      "description": "https:// resource URL of the x402 endpoint to diagnose (pre-catalog endpoints welcome β€” findability reports honestly)"
    },
    "asserted_price_micro": {
      "type": "integer",
      "minimum": 1,
      "description": "your advertised price in micro-USDC β€” becomes the price basis vs the category median; defaults to the live quote's cheapest recognized entry"
    },
    "expected_payto": {
      "type": "string",
      "description": "optional 0x… address you expect the endpoint to charge to; mismatch is a named finding"
    }
  },
  "required": [
    "endpoint"
  ],
  "additionalProperties": false
}
🟑register(action, spec, registration_id, seller, signature, ...)

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 Schema

{
  "type": "object",
  "properties": {
    "action": {
      "enum": [
        "start",
        "challenge_response",
        "status",
        "update_spec",
        "renew"
      ],
      "description": "start and renew are paid ($5/30 days); challenge_response, status and update_spec are free"
    },
    "spec": {
      "type": "object",
      "description": "registration-v1.0.0 Q1/Q2 document (start, update_spec) β€” schema: https://agenteconomy.cloud/schemas/registration-v1.0.0.json"
    },
    "registration_id": {
      "type": "string",
      "description": "from start (all actions after start)"
    },
    "seller": {
      "type": "string",
      "description": "0x… payTo address β€” alternative lookup where registration_id is not at hand"
    },
    "signature": {
      "type": "string",
      "description": "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)"
    },
    "challenge_id": {
      "type": "string",
      "description": "challenge_response: optional; defaults to the latest issued challenge"
    },
    "signed_at": {
      "type": "string",
      "description": "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>\""
    }
  },
  "required": [
    "action"
  ],
  "additionalProperties": false
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded5 tools
verifiedversion not recorded5 tools
verifiedversion not recorded5 tools
verifiedversion not recorded5 tools
verifiedversion not recorded5 tools
verifiedversion not recorded5 tools