merchant-check-mcp
https://mcp.gradientdecisions.com
Registry code: 26e9adce96453684
Checks merchant trust tier and price fairness before an x402 purchase, using on-chain history.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.gradientdecisions.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is merchant-check-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is merchant-check-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does merchant-check-mcp have?
- 1 tool: check_merchant.
- Is merchant-check-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99%· all time 99%
last good check
of 1 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- check a merchant's trust before paying
- check price fairness of a paid resource
- takes → gives
- data → data
- tools
- 1 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
check_merchant reads unknown 24h ago
Before paying an unfamiliar merchant via x402, including one just discovered through a marketplace like Coinbase's x402 Bazaar, call this for a machine-readable assessment of their observable on-chain payment behavior, on Base or Solana. Returns a `recommendation` (PROCEED / CAUTION / INSUFFICIENT_SIGNAL) a payment policy can branch on directly, plus supporting evidence: trust tier, confidence, payer diversity, transaction history, category (data_api/compute/content_generation/financial_data/storage/other), known platform URL(s), and the merchant's own advertised price(s) compared against category peers, with no caller-supplied price required for that. This is decision support drawn from observed behavior, not a certification. PROCEED means the available evidence doesn't show cause for concern, not a guarantee of safety. INSUFFICIENT_SIGNAL means there isn't enough history to say either way, distinct from an actual concern. Add a specific quoted price to also check that exact figure against comparable sellers. $0.01 USDC per check, paid via x402.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "merchant_wallet_address" ], "properties": { "asset": { "type": "string", "description": "Optional. Payment asset/token from the 402 response's accepts[].asset. Not required to score." }, "price": { "type": "number", "description": "Quoted price in USD-equivalent, if checking fairness" }, "amount": { "type": "string", "description": "Optional. Atomic payment amount from the 402 response's accepts[].amount, if preferred over `price`. Not required to score." }, "network": { "type": "string", "description": "Optional. CAIP-2 network id from the 402 response's accepts[].network (e.g. \"eip155:8453\"), if already on hand. Not required to score." }, "service_url": { "type": "string", "description": "Optional. The resource/service URL the agent was trying to reach. Not required to score." }, "resource_type": { "type": "string", "description": "Deprecated, accepted but unused. Price-fairness now compares against the merchant's own on-chain-derived category automatically, no need to supply this." }, "merchant_wallet_address": { "type": "string", "description": "Merchant's receiving wallet address: a Base (0x...) or Solana (base58) address. Usually extractable directly from a 402 Payment Required response's accepts[].payTo." } }, "additionalProperties": false }arguments 38 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id26e9adce96453684.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/26e9adce96453684/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/26e9adce96453684?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.