x402-trust-board
https://x402-trust-check.ben-mcalilly.workers.dev
Registry code: 26018e38d4d4cf7d
Call check_payment before paying any x402 or MPP endpoint. Don't pay when the verdict is avoid. Sellers: call check_listing to find out why an endpoint isn't in Coinbase's Bazaar.
- endpoint
- https://x402-trust-check.ben-mcalilly.workers.dev/mcp
- protocol
- streamable-http ·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 x402-trust-board live?
- Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.
- Is x402-trust-board free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does x402-trust-board have?
- 2 tools: check_payment, check_listing.
- Is x402-trust-board 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 100%· all time 100%
last good check
of 2 tools
- unknown → live
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 2 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-19
concentrated, shared-payto
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_payment unknown never probed
Before paying an agent-payable API (x402 or MPP), check whether it is safe: does it answer reliably, do its payment terms match its listing (no switched or burn wallets, no overcharges), and is the address it asks you to pay one the seller has proven is theirs. Returns verdict ok | caution | avoid | unknown with reasons. Pass the payTo address from the 402 response when you have it.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The full https:// URL you are about to pay" }, "payTo": { "type": "string", "description": "Optional: the address its 402 response asks you to pay" } } }arguments 16 linescheck_listing unknown 16h ago
For sellers: check whether an x402 endpoint is listed in Coinbase's Bazaar and, if not, why. Runs Coinbase's public validator (the indexer's own checks), looks the payout address up in Coinbase's merchant list, and adds the Settle Watch's 30-day availability against Coinbase's 99% bar for featured listings. Returns findings with a fix for each.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The full https:// URL of your paid endpoint" }, "method": { "enum": [ "GET", "POST" ], "type": "string", "description": "HTTP method of the route (default GET)" } } }arguments 20 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 id26018e38d4d4cf7d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/26018e38d4d4cf7d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/26018e38d4d4cf7d?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.