About forensics-mcp
forensics-mcp provides on-chain due-diligence tools for AI agents and other MCP clients. It covers token activity, wallet trust and settlement risks, with paid calls authorized through x402.
Key features
- 01Token activity verdicts
- 02RWA settlement safety checks
- 03Wallet trust screening
- 04ERC-20 supply and transfer analysis
- 05Combined due-diligence memos
Use cases
- 01Assessing a token before investment
- 02Checking an RWA before a trade
- 03Reviewing wallet flows and counterparties
MCP support
Exposes forensic analysis tools to MCP clients over streamable HTTP. Paid tools use x402 payments in USDC on Base.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://solene-fa2010da.base44.app/functions/forensicsMcpclaude mcp add --transport http leohoudinisanders-byte-forensics https://solene-fa2010da.base44.app/functions/forensicsMcp{"mcpServers":{"leohoudinisanders-byte-forensics":{"type":"http","url":"https://solene-fa2010da.base44.app/functions/forensicsMcp"}}}Open in Cursor{"servers":{"leohoudinisanders-byte-forensics":{"type":"http","url":"https://solene-fa2010da.base44.app/functions/forensicsMcp"}}}Open in VS Code{"mcpServers":{"leohoudinisanders-byte-forensics":{"type":"http","url":"https://solene-fa2010da.base44.app/functions/forensicsMcp"}}}{"mcpServers":{"leohoudinisanders-byte-forensics":{"serverUrl":"https://solene-fa2010da.base44.app/functions/forensicsMcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEOn-chain Forensics — MCP Server (x402-payable tools)
Due-diligence forensics for AI agents, exposed as MCP tools over streamable HTTP.
Endpoint: https://solene-fa2010da.base44.app/functions/forensicsMcp
Operator: Leo Sanders ([email protected]). Deep research with receipts: the agent that ships working proof, not promises.
Tools
| Tool | Price | What it does |
|---|---|---|
forensics_info | free | Service directory, chains, aliases, usage |
token_verdict | $0.02 | Token verdict card: activity score 0-100, verdict tier, transfers, whale/concentration flags, plain-English take. EVM (address+chain) or XRPL (issuer+currency) |
settle_safe | $0.02 | Pre-trade settle-safe screen for tokenized equities/RWAs: canonical-registry check, freeze/clawback flags, optional counterparty trust tier |
wallet_screen | $0.05 | Wallet trust screen: flows, counterparties, contract-interaction risk, trust tier (Base/Ethereum/XRPL) |
token_profile | $0.05 | Full ERC-20 forensics: 24h net supply change, mint/burn events, concentration, top transfers |
diligence_memo | $0.25 ($0.35 with counterparty) | Composed Token Due-Diligence Memo: verdict + forensics + settle-safe screen, decision-grade |
Payment (x402 v2)
No API keys, no signup — the payment IS the auth.
- Call a paid tool:
tools/callreturns HTTP 402 with aPAYMENT-REQUIREDheader (x402 v2 challenge, USDC on Base, eip155:8453). - Sign the EIP-3009 authorization with your wallet.
- Retry with the
X-PAYMENTheader. Settlement on Base mainnet; the tool result is served.
Any x402-capable client (e.g. x402 fetch) handles this automatically. The tools are also indexed in the Coinbase x402 Bazaar as MCP resources (type mcp, transport streamable-http).
Listed in the official MCP Registry
Published at registry.modelcontextprotocol.io as
io.github.leohoudinisanders-byte/forensics-mcp v1.0.0 (remote, streamable-http).
Related
- Landing: https://leohoudinisanders-byte.github.io/onchain-forensics/
- OpenAPI 3.1: https://leohoudinisanders-byte.github.io/onchain-forensics/openapi.json
- REST API: https://solene-fa2010da.base44.app/functions/forensicsApi
- Canton Swap Broker (OneSwap x402 wrapper): https://leohoudinisanders-byte.github.io/canton-swap-broker/
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.