WALLET DOCTOR

Pay-per-call Solana wallet & token analysis for AI agents

5 HTTP endpoints for wallet balances, transaction traces, token approvals, token-safety checks and drain triage. Each call is paid on the spot in USDC with the x402 protocol, on Solana or Base. There is no signup, no API key and no subscription.

x402 catalog (JSON)How an agent pays

Endpoints & prices

Prices come from the live x402 catalog (USDC, 6 decimals) and are charged only when the call succeeds. If a call fails (for example when the public Solana RPC is rate-limited) you get an error and the payment is not settled. Base URL: https://wallet-doctor-x402.m-zikriz.workers.dev

RequestWhat it returnsPrice (USDC)
GET /v1/balance?wallet=…Solana wallet balance: SOL and USDC$0.0001
GET /v1/txtrace?signature=…Transaction trace: status, slot, fee, SOL balance changes, first 20 log lines$0.0005
GET /v1/approvals?wallet=…SPL token approvals: token accounts with an active delegate (SPL Token + Token-2022)$0.0005
GET /v1/token_safety?mint=…Token mint safety: mint/freeze authority, supply, decimals; top-10 holder concentration when the public RPC allows it$0.0010
GET /v1/drain_forensics?wallet=…Wallet activity review: last 25 transactions with status, failed ones flagged, plus active token delegates$0.0025

How an agent pays (x402)

  1. Call an endpoint, e.g. GET https://wallet-doctor-x402.m-zikriz.workers.dev/v1/balance?wallet=<address>.
  2. The server answers HTTP 402 Payment Required. The body (and the PAYMENT-REQUIRED header) list the accepted options: scheme exact, USDC on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp or eip155:8453 (Base), the amount and the payee.
  3. Your x402 client signs a payment for that amount and repeats the request with the X-PAYMENT header.
  4. The payment is verified with the facilitator (PayAI), the endpoint runs, and the payment is settled only if the call succeeds; then you get the JSON result. A failed call is not charged.
curl -i "https://wallet-doctor-x402.m-zikriz.workers.dev/v1/balance?wallet=<address>"
# → HTTP/2 402  {"x402Version":2,"accepts":[{"scheme":"exact","network":"solana:…","amount":"100",…}]}
# Pay with any x402 v2 client (e.g. the x402 SDKs), then retry with the X-PAYMENT header.

MCP endpoint

Remote MCP server (streamable HTTP): https://manhourplan.com/wallet-doctor/mcp — listed in the official MCP Registry as com.manhourplan/wallet-doctor. tools/list is free and shows each tool's x402 price.

Paid tools use x402 over MCP: a call without payment returns a tool result with isError: true and the payment requirements in structuredContent (x402 v2 accepts). An x402-capable MCP client signs the payment and retries the call with params._meta["x402/payment"]; the result carries the settlement in _meta["x402/payment-response"]. Plain MCP clients without an x402 wallet will see the payment requirements but cannot pay.

claude mcp add --transport http wallet-doctor https://manhourplan.com/wallet-doctor/mcp

Important

Wallet Doctor returns data read from public blockchain sources and third-party APIs. The data may be incomplete, delayed or wrong. Results, including token-safety checks, are for information only. They are not financial, investment or security advice and are no guarantee that a token, wallet or transaction is safe. Do your own research. Payments are made in cryptocurrency and settle on-chain.