wallet-labels-mcp
https://wallet-labels-mcp.mtree.workers.dev
Registry code: 052c33dd2819e985
Pay-per-call MCP for EVM wallet labels — ENS, OFAC SDN, Tornado mixer registry, ERC-20 metadata, and a public-label registry composed into one view per address. Tools require x402 USDC payment on Base. tools/call returns a 402 envelope; settle X-PAYMENT and retry against the REST endpoint.
- endpoint
- https://wallet-labels-mcp.mtree.workers.dev/mcp
- door code
- d42f4a8ea0237c0a
- 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 wallet-labels-mcp live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is wallet-labels-mcp free to use?
- Not measured yet.
- What tools does wallet-labels-mcp have?
- 3 tools: wallet_risk_score, labels_by_category, wallet_labels.
- Is wallet-labels-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.4%· all time 99.2%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get labels for an evm wallet address
- score an evm wallet for risk
- list addresses by category
- 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 also stands behind 17 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
none in the window
thin, shared-payto
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.
wallet_risk_score reads unknown never probed
Returns a 0–100 composite risk score for an EVM address (clean / low / medium / high / blocked) with itemized reasons per rule fired (OFAC SDN match, known-mixer match, contract anomaly). Costs $0.10 USDC on Base via x402.
{ "type": "object", "required": [ "address" ], "properties": { "chain": { "type": "string" }, "address": { "type": "string" } }, "additionalProperties": false }arguments 15 lineslabels_by_category reads unknown never probed
Returns all addresses in the bundled registries that match a category (sanctioned, mixer, exchange, dex, lending, stablecoin, wrapped-asset, founder, foundation, bridge, infrastructure). Costs $0.07 USDC on Base via x402.
{ "type": "object", "required": [ "category" ], "properties": { "limit": { "type": "number" }, "category": { "type": "string" } }, "additionalProperties": false }arguments 15 lineswallet_labels reads unknown never probed
Composes ENS, OFAC SDN list, Tornado Cash mixer registry, on-chain ERC-20 metadata, and a public-label registry into one labeled view of an EVM address. Returns sanctioned/mixer flags, ENS name, contract-vs-EOA distinction, and ERC-20 metadata for token contracts. Costs $0.05 USDC on Base via x402.
{ "type": "object", "required": [ "address" ], "properties": { "chain": { "type": "string" }, "address": { "type": "string" } }, "additionalProperties": false }arguments 15 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 id052c33dd2819e985.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/052c33dd2819e985/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/052c33dd2819e985?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.