x402 seller trust for AI agents: verify on-chain revenue, check delivery, diagnose listings.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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).
https:// resource URL whose x402 payment machinery to test
optional catalog listing id — compares the advertised payTo against the cataloged seller
optional 0x… address you expect the endpoint to charge to; mismatch is a named finding
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
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).
| Argument | Type | Description |
|---|---|---|
| endpoint* | string | https:// resource URL whose x402 payment machinery to test |
| listing_id | string | optional catalog listing id — compares the advertised payTo against the cataloged seller |
| expected_payto | string | optional 0x… address you expect the endpoint to charge to; mismatch is a named finding |
{
"type": "object",
"required": [
"endpoint"
],
"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"
}
},
"additionalProperties": false
}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).
| Argument | Type | Description |
|---|---|---|
| endpoint* | string | 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 |
| 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 |
{
"type": "object",
"required": [
"endpoint"
],
"properties": {
"endpoint": {
"type": "string",
"maxLength": 500,
"description": "https:// resource URL of the x402 endpoint to diagnose (pre-catalog endpoints welcome — findability reports honestly)"
},
"expected_payto": {
"type": "string",
"description": "optional 0x… address you expect the endpoint to charge to; mismatch is a named finding"
},
"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"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| need* | string | what the buying agent needs |
| limit | integer | |
| cursor | string | |
| network | string | CAIP-2 filter, e.g. eip155:8453; default all |
{
"type": "object",
"required": [
"need"
],
"properties": {
"need": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "what the buying agent needs"
},
"limit": {
"type": "integer",
"default": 10,
"maximum": 20,
"minimum": 1
},
"cursor": {
"type": "string"
},
"network": {
"type": "string",
"description": "CAIP-2 filter, e.g. eip155:8453; default all"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| spec | object | registration-v1.0.0 Q1/Q2 document (start, update_spec) — schema: https://agenteconomy.cloud/schemas/registration-v1.0.0.json |
| action* | any | start and renew are paid ($5/30 days); challenge_response, status and update_spec are free |
| 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 new spec>\nsigned_at: <this value>" |
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.
| Argument | Type | Description |
|---|---|---|
| seller* | string | 0x… payTo address or 12-hex slug — exactly one seller per call |
{
"type": "object",
"required": [
"seller"
],
"properties": {
"seller": {
"type": "string",
"description": "0x… payTo address or 12-hex slug — exactly one seller per call"
}
},
"additionalProperties": false
}| challenge_id | string | challenge_response: optional; defaults to the latest issued challenge |
| registration_id | string | from start (all actions after start) |
{
"type": "object",
"required": [
"action"
],
"properties": {
"spec": {
"type": "object",
"description": "registration-v1.0.0 Q1/Q2 document (start, update_spec) — schema: https://agenteconomy.cloud/schemas/registration-v1.0.0.json"
},
"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"
},
"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)"
},
"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>\""
},
"challenge_id": {
"type": "string",
"description": "challenge_response: optional; defaults to the latest issued challenge"
},
"registration_id": {
"type": "string",
"description": "from start (all actions after start)"
}
},
"additionalProperties": false
}