# Cleartracedata Cleartrace MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.cleartracedata%2Fcleartrace
Registry id: `mcp-registry/com.cleartracedata/cleartrace`
Status: live (checked 2026-10-27T17:06:07.872Z)

## Measurements (30 days)

- Uptime: 99.9%
- Checks: 5054
- Outages (90 days): 7

## Install

```json
{
  "mcpServers": {
    "cleartracedata-cleartrace-mcp-server": {
      "type": "http",
      "url": "https://cleartracedata.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http cleartracedata-cleartrace-mcp-server https://cleartracedata.com/mcp
```

## Tools (7)

- `attribution`: Which frontend, router or interface originated on-chain DEX volume, aggregated per contract per chain. This is the dataset ClearTrace exists for: it names the v
- `contract_attribution`: What ClearTrace knows about a single contract or wallet address: its per-chain volume split across the four attribution vectors, plus any label resolved for it.
- `execution_benchmarks`: Rank DEXs and aggregators by realized execution quality: median slippage against a minute-level off-chain reference price (Dune prices.usd, an interpolated 5-mi
- `explain_transaction`: Classify a single transaction against the attribution engine: which frontend or router originated the trade and by which evidence, the pools it touched, any fee
- `gas_prices`: Current gas price on each supported chain, from RPC. On the L2s (Base, Arbitrum, Optimism) this is the EXECUTION gas price only and excludes the L1 data availab
- `request_api_key`: Mint a free API key that multiplies this server's rate limits by 10x. Requires an email address. The key changes LIMITS ONLY. Every figure served here is public
- `revert_rates`: The share of a venue's routing transactions that fail on-chain, per chain. Reported separately from slippage because reliability and price are different questio

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.