Base Transaction Decoder MCP server
{
"mcpServers": {
"base-transaction-decoder": {
"type": "http",
"url": "https://api.0200project.com/mcp"
}
}
}{
"mcpServers": {
"base-transaction-decoder": {
"type": "http",
"url": "https://api.0200project.com/mcp"
}
}
}{
"mcpServers": {
"base-transaction-decoder": {
"type": "http",
"url": "https://api.0200project.com/mcp"
}
}
}{
"servers": {
"base-transaction-decoder": {
"type": "http",
"url": "https://api.0200project.com/mcp"
}
}
}{
"mcpServers": {
"base-transaction-decoder": {
"type": "http",
"url": "https://api.0200project.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 0.1.4
What it does
Decodes Base mainnet transactions into plain English and strict JSON, showing what moved, who was involved, risk flags, and gas cost. Returns deterministic onchain data with no LLM in the response path, ensuring stable output for parsing. Serves developers building agents or interfaces that need to explain transactions to users.
- Explain a swap or transfer to a user in a wallet or trading interface by passing a transaction hash.
- Extract structured facts from a transaction (assets moved, counterparties, gas paid) for further processing or logging.
- Flag risky transactions before user interaction by checking for unverified contracts, drainer blacklists, or unusual approvals.
Tools this server exposes
| Tool | Does |
|---|---|
| explain_transaction | Accepts a Base mainnet transaction hash and returns a JSON object with action type, assets moved, counterparties, risk flags, gas cost, and verification checks. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.