Analytics

cleartracedata.com

Provides analytics and attribution for DEX trading, including execution quality scores, revert rates, volume attribution by frontend/router, and transaction classification.

1 endpoint7 known toolsFirst detected August 29, 2026Last detected August 29, 2026

ENDPOINT 1

https://cleartracedata.com/mcp

No auth detected

MCP server metadata

Name: cleartrace

Capabilities

experimentalpromptsresourcestools

Server instructions

ClearTrace measures how DEX trades actually executed on-chain, across Ethereum, Base, Arbitrum and Optimism. What it is good for: comparing execution quality between venues, attributing trade volume to the frontend or router that originated it (including unnamed ones), and explaining what a specific transaction did and who routed it. Three things to carry into any answer built on these tools: 1. This is a batch pipeline, not a live feed. Attribution volumes refresh weekly and are dated to the Monday of their window; quoting one as "today's" volume is wrong. 2. The metrics are deliberately separate. Slippage, revert rate and MEV exposure are three different measurements and are never combined into one "best execution" score, because the combination would hide which one moved. 3. Coverage is partial and says so. A contract with no label is reported as unlabeled rather than guessed at, and that is a real answer about a real anonymous router, not a gap to paper over. Every figure is public and free. An API key changes rate limits only.

Known tools 7

execution_benchmarks

Rank DEXs and aggregators by realized execution quality: median slippage against a 1-minute VWAP baseline, expressed as a score of 0-100 (higher means less slippage).

Inferred read-only

revert_rates

The share of a venue's routing transactions that fail on-chain, per chain.

Inferred read-only

attribution

Which frontend, router or interface originated on-chain DEX volume, aggregated per contract per chain.

Inferred read-only

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.

Inferred read-only

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 recipients, and whether it was sandwiched.

Potential side effects

gas_prices

Current gas price on each supported chain, from RPC.

Inferred read-only

request_api_key

Mint a free API key that multiplies this server's rate limits by 10x.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.cleartrace]
url = "https://cleartracedata.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: cleartrace
Remote MCP URL: https://cleartracedata.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "cleartrace": {
      "url": "https://cleartracedata.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "cleartrace": {
      "type": "http",
      "url": "https://cleartracedata.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "cleartrace",
  "transport": "streamable-http",
  "url": "https://cleartracedata.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.