agentcheck
https://agentcheck-kohl.vercel.app
Registry code: d635319c56317350
Call find_seller before paying any x402 seller. Results carry a verdict on whether the seller's buyers are real.
- endpoint
- https://agentcheck-kohl.vercel.app/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
- 10 · newcomer
- Is agentcheck live?
- Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.
- Is agentcheck free to use?
- Not measured yet.
- What tools does agentcheck have?
- 3 tools: find_seller, seller_report, audit_summary.
- Is agentcheck 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.3%· all time 99.3%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- topic
- security & compliance
- used for
- find x402 sellers with real buyers
- get audit verdict for an x402 seller
- get weekly seller audit totals
- takes → gives
- text → data
- tools
- 3 reads
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 stands behind 3 doors on this origin, so the chain figures are the operator's. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-19
no flags
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.
find_seller reads unknown never probed
Find pay-per-call (x402) API sellers for a job, ranked by whether their buyers are real, live status, recent paid use and price. Use before buying anything with an agent wallet. Returns the exact URL, price, call example and the seller's audit verdict.
{ "type": "object", "required": [ "query" ], "properties": { "n": { "type": "integer", "description": "Results, 1-20 (default 5)" }, "query": { "type": "string", "description": "What you need, e.g. 'web search', 'is this Base token a honeypot', 'send an SMS'" }, "network": { "type": "string", "description": "e.g. eip155:8453 (Base) or solana" }, "max_price_usd": { "type": "number" } } }arguments 23 linesseller_report reads unknown never probed
Audit verdict for one x402 seller domain: are its buyers real or seller-funded, 30-day dollars, repeat buyers, plus AgentCheck's own test-purchase findings where available.
{ "type": "object", "required": [ "domain" ], "properties": { "domain": { "type": "string" } } }arguments 11 linesaudit_summary reads unknown never probed
Totals from the latest weekly audit of every Bazaar seller with 50+ paid calls: how many have real buyers, how many fund their own buyers, dollars by verdict.
{ "type": "object", "properties": {} }arguments 4 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 idd635319c56317350.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d635319c56317350/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d635319c56317350?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.