_ registry / mcp streamable-http · checked 1h ago

wallet-doctor-mcp

https://wallet-doctor-x402.m-zikriz.workers.dev

Registry code: d1b7d626c39630b8

api record

Multi-chain wallet MCP. 18 tools: balance, swap, bridge, stake, claim. Pay-per-call USDC (x402 v2).

from a public catalogue that lists it, not from the operator

endpoint
https://wallet-doctor-x402.m-zikriz.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 it live, free and safe measured by this hub
Is wallet-doctor-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-doctor-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does wallet-doctor-mcp have?
16 tools: captcha/types, captcha/health, drainForensics, captcha/solve, priceChart, nftAudit, tokenSafety, tokenHolders, ….
Is wallet-doctor-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.
reachable
live
uptime, 30 days
98.9%

90 days 99%· all time 99%

latency
93ms

last good check

priced tools
5

of 16 tools

_ answered our checks, 90 days 420 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
crypto & onchain onchain analytics
used for
  • get solana wallet balance and portfolio
  • audit a token launch
  • check token mint safety
  • trace a transaction
  • reconstruct a wallet drain
takes → gives
data → data
tools
16 reads
_ usage and payments 30 days

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 14 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
0

distinct

settlements
0

none in the window

received on chain
0 USDC

thin

_ what it can do 16 tools
5 paid1 open 10 never probed 6 of 16 classified

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.

  • balance reads 0.0001 USDC paid never probed

    Get Solana wallet SOL/USDC balance — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": "string"
  }
}
    arguments 9 lines
  • price reads 0.0001 USDC paid never probed

    Token price quote (mint or symbol) — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": "string"
  }
}
    arguments 9 lines
  • portfolio reads 0.001 USDC paid never probed

    Wallet portfolio breakdown in USD — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": "string"
  }
}
    arguments 9 lines
  • txtrace reads 0.0005 USDC paid never probed

    Trace tx with side-effect decoding (Solana RPC public) — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "signature"
  ],
  "properties": {
    "signature": "string"
  }
}
    arguments 9 lines
  • approvals reads 0.0005 USDC paid never probed

    Scan SPL token approvals (Solana RPC) — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": "string"
  }
}
    arguments 9 lines
  • liquidityCheck reads open 9h ago

    Liquidity pool depth + LP lock status — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": "string"
  }
}
    arguments 9 lines
  • captcha/types reads unknown never probed

    List supported captcha types and prices — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • captcha/health reads unknown 9h ago

    Free captcha backend health check — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • drainForensics reads unknown never probed

    Wallet drain forensics — full reconstruction — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": "string"
  }
}
    arguments 9 lines
  • captcha/solve reads unknown never probed

    Image captcha OCR solver ($0.005 USDC per call). Returns recognized text. — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "image_b64"
  ],
  "properties": {
    "image_b64": "string"
  }
}
    arguments 9 lines
  • priceChart reads unknown never probed

    24h OHLC token chart — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": "string"
  }
}
    arguments 9 lines
  • nftAudit reads unknown never probed

    Audit NFT collection for honeypots — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": "string"
  }
}
    arguments 9 lines
  • tokenSafety reads unknown never probed

    Token mint safety: authorities, freeze, top holders — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": "string"
  }
}
    arguments 9 lines
  • tokenHolders reads unknown never probed

    Top 50 token holders — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": "string"
  }
}
    arguments 9 lines
  • launchAudit reads unknown never probed

    Token launch audit: bundle, snipers, first 100 holders — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "mint"
  ],
  "properties": {
    "mint": "string"
  }
}
    arguments 9 lines
  • topTraders reads unknown never probed

    Top 25 traders ranking by PnL (last 30 days) — pay per call in USDC (x402 v2).

    mcp-tool

    {
  "type": "object",
  "required": [
    "wallet"
  ],
  "properties": {
    "wallet": "string"
  }
}
    arguments 9 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d1b7d626c39630b8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d1b7d626c39630b8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d1b7d626c39630b8/badge.svg)](https://brick.blue/agent/d1b7d626c39630b8?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.