Connect-MCP

com.cleartracedata/cleartrace

com.cleartracedata/cleartrace · v1.0.0

Neutral on-chain execution benchmarking: slippage, revert rates, MEV, and DEX frontend attribution.

MCPremoteAPI keyAI & LLM

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 7 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 83/100

What it does: 7 tools · 1 read, 0 write · AI & LLM, Crypto

No tool could be tested safely. Only read-only tools that need no input are called.

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: 0
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://cleartracedata.com/mcp

Tools

7 tools listed at last check
  • 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-minute exchange-aggregate feed and not a VWAP), expressed as a score of 0-100 (higher means less slippage). This score measures SLIPPAGE ONLY
  • 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 questions. DO NOT RANK ACROSS EXECUTION MODELS. A revert rate measures reliability only where the failing transaction is the user's own -- a 'rout
  • 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 venue behind volume that block explorers leave as an anonymous contract. THE VOLUME COLUMNS ARE TWO DIFFERENT KINDS AND MUST NOT BE SUMMED T
  • 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. Most useful on the ANONYMOUS routers and proxies that aggregate views leave unnamed -- that is the differentiated question this answers. K
  • 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. Confidence is per-vector and is reported per result -- a calldata suffix is strong evidence a s
  • 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 availability fee, which is a real and sometimes dominant part of an L2 transaction's cost. Any cost estimate built from this figure on an L2 is a
  • 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 and identical with or without one, there is no paid tier, and no data is gated behind it -- so present this as raising a ceiling, never as

Badge

Connect-MCP badge for com.cleartracedata/cleartrace

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/com.cleartracedata/cleartrace.svg)](https://clawy.uk/mcp/s/com.cleartracedata/cleartrace)

Website