wallet-cex-flows-mcp
https://wallet-cex-flows-mcp.mtree.workers.dev
Registry code: 6ca271daccd92ef9
Pay-per-call MCP for EVM wallet ↔ CEX flow analysis. Composite multichain flow scan + per-address CEX attribution + per-CEX recent inflows. 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-cex-flows-mcp.mtree.workers.dev/mcp
- door code
- 5a414bcc1eeaa0a9
- 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-cex-flows-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-cex-flows-mcp free to use?
- Not measured yet.
- What tools does wallet-cex-flows-mcp have?
- 3 tools: wallet_cex_attribution, wallet_cex_flows, cex_recent_inflows.
- Is wallet-cex-flows-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.2%· all time 99.4%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- analyse wallet flows to exchanges
- check if an address belongs to an exchange
- list top recent depositors to an exchange
- 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_cex_attribution reads unknown never probed
Single-address CEX attribution. Look up an EVM address in the curated CEX address registry. Returns is_cex + (if matched) cex_label, exchange_family (Binance / Coinbase / Kraken / OKX / Crypto.com / Bitfinex / Bittrex / Gate.io), cex_role (hot_wallet / deposit_aggregator / cold_storage). Costs $0.05 USDC on Base via x402.
{ "type": "object", "required": [ "address" ], "properties": { "chain": { "type": "string" }, "address": { "type": "string" } }, "additionalProperties": false }arguments 15 lineswallet_cex_flows reads unknown never probed
Composite wallet ↔ CEX flow analysis. Scans ERC-20 Transfer events involving the address (both directions) across up to 5 chains and matches counterparties against a curated CEX address registry. Returns per-chain per-CEX deposit/withdrawal counts, USDC/USDT/ETH atomic totals each direction, and net flow direction (depositor / withdrawer / balanced). Costs $0.30 USDC on Base via x402.
{ "type": "object", "required": [ "address" ], "properties": { "chains": { "type": "array", "items": { "type": "string" } }, "address": { "type": "string" }, "lookback_blocks": { "type": "number" } }, "additionalProperties": false }arguments 21 linescex_recent_inflows reads unknown never probed
Recent top depositors to a CEX. Aggregates inbound ERC-20 Transfer events targeting registry addresses for the requested exchange + chain, optionally filtered to a single token. Returns top 10 distinct sender addresses by total atomic volume (CEX↔CEX rebalancing excluded). Costs $0.10 USDC on Base via x402.
{ "type": "object", "required": [ "exchange" ], "properties": { "chain": { "type": "string" }, "token": { "type": "string" }, "exchange": { "type": "string" }, "lookback_blocks": { "type": "number" } }, "additionalProperties": false }arguments 21 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 id6ca271daccd92ef9.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/6ca271daccd92ef9/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/6ca271daccd92ef9?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.