x402 Merchant Check MCP server
online · 100% uptimecom.gradientdecisions/merchant-check·v1.0.0Pre-payment merchant trust checks for x402 agents on Base and Solana.
0 stars
Reviews
Write oneNobody has reviewed x402 Merchant Check yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
x402 Merchant Check tools (1)
write = sends, deletes, buys or postscheck_merchantFreeBefore 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.
Public scan report
scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1522ms20/20
- Tool poisoning1 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 42 days ago12/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How x402 Merchant Check compares
Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 87/100
- higher than 83% of 1,761 Finance servers
- Tools
- 1
- the typical Finance server has 8
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Finance server answers 100%
- Response time
- 235 ms
- faster than 60% of 1,133 Finance servers
What its tools let an agent do: 1 read
Install x402 Merchant Check in Claude Code, Cursor or VS Code
claude mcp add --transport http merchant-check https://mcp.gradientdecisions.com/mcp
What the publisher says
From the x402 Merchant Check repository's README, as published. We do not edit it. Read it on GitHub
merchant-check-mcp
Gradient Decisions provides merchant intelligence for autonomous commerce. x402 Merchant Check evaluates observable on-chain payment behavior so agents can make more informed decisions before paying unfamiliar x402 merchants. Agent-native, machine-readable, x402-native — $0.01 per check, paid via x402. It is a pre-payment decision primitive, not a certification, a guarantee of safety, or a replacement for an agent's own payment policy. See INTEGRATION.md for the full discover → check → decide → pay flow, the 402-response-to-input mapping, and the exact response shape. See the privacy policy for how data is handled. This file tracks what's actually built, what's stubbed, and what needs you before this goes further.
Privacy policy
Live at gradientdecisions.com/privacy (src/privacy.ts), linked from the homepage footer and here. Drafted 2026-08-13 by Claude at direct request, grounded in this system's actual data practices (what querylog and merchantsignals really store — see "Internal caller-tracking dashboard" above) rather than generic boilerplate. Not reviewed by a lawyer — the page itself says so, and that caveat should stay until it has been. Contact email is info@gradientdecisions.com (switched 2026-08-19 from the developer's personal address — see "Data access policy" below for why and how). src/privacy.ts's CONTACT_EMAIL constant is the source of truth if it ever needs to change again.
DISCOVER → IDENTIFY PAYMENT DESTINATION → GRADIENT MERCHANT CHECK → AGENT PAYMENT POLICY → X402 PAYMENTStatus: two live surfaces, one product
checkmerchant MCP tool. Live on Base mainnet with real USDC (switched from Base Sepolia testnet — see "Going to mainnet"; real settled payments confirmed in querylog, real tx hashes on Base). Merchant coverage spans both Base and Solana (PayAI/Helius) — see "Solana data source". Payment flow verified end-to-end: free tools/list discovery → tools/call correctly 402s → agent builds and signs an x402 payment, submits it → facilitator settles it → real tier comes back. See "Try it yourself" below.
- Agents: https://mcp.gradientdecisions.com/mcp — the paid
static placeholder (src/homePlaceholder.ts), not a live dashboard. It used to render every scored merchant's recommendation/signals/pricing directly, plus serve the same dataset as raw JSON at /api/wallets — see "Data access policy" below for why that was locked down. The real redesigned homepage/dashboard is a separate later task, built from Figma mockups, not this placeholder.
- Humans: https://gradientdecisions.com — as of 2026-08-19 a minimal
Note: the two-chain merchant-signal data above is separate from this endpoint's own payment rail — check_merchant itself is still only paid via Base x402 (see "Payment flow" line above); nothing about that has changed.
Data access policy (2026-08-19)
Structured merchant data — recommendation, signals, pricing, reasons, platforms, anything checkmerchant returns — is available only through the paid checkmerchant MCP tool, paid per-query via x402. This wasn't always true, and the change is worth recording plainly:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
x402 Merchant Check: common questions
- Is x402 Merchant Check MCP server safe?
- Yes, by our scan: it is graded A (87/100). Read the x402 Merchant Check safety report
- How do I install x402 Merchant Check?
- It runs remotely at mcp.gradientdecisions.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does x402 Merchant Check need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is x402 Merchant Check maintained?
- The last commit was 44 days ago (2026-09-21). The latest release is v1.0.0.
- Is x402 Merchant Check up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of x402 Merchant Check?
- Servers from other publishers that do the same job: Pulsefeed X402 MCP server, three.ws Agent Payments MCP server and Yolfi Payments MCP server.
- How does x402 Merchant Check compare with other Finance MCP servers?
- safety score 87/100 (higher than 83% of 1,761 Finance servers); tools 1 (the typical Finance server has 8); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to x402 Merchant Check
Same job from other publishers: the closest match first, then the best rated.
- Pulsefeed X402Verify x402 payment endpoints before an AI agent pays: scam scan, on-chain checks, trust scores.not reviewedGrowingA
three.ws Agent PaymentsGoverned x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.not reviewedEstablishedB- Yolfi Payments MCPLet AI agents add Yolfi crypto checkout, paylinks, webhooks, and status checks.not reviewedEstablishedA
X402 ListFind and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.not reviewedEstablishedA- Coinbase CommerceMCP server for Coinbase Commerce — crypto merchant payments (BTC/ETH/USDC); settle crypto or fiatnot reviewedGrowingB
