com.cleartracedata/cleartrace

com.cleartracedata/cleartrace · v1.0.0 · crypto-web3

com.cleartracedata/cleartrace is healthy: it completed an MCP handshake in 1309 ms and exposes 7 tools.

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

Endpoint: https://cleartracedata.com/mcp (streamable-http)

No repository listed · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count7
Latency1309 ms
Last checked (UTC)2026-10-17T02:45:35.131Z

Health history

Checked (UTC)StatusLatencyError
2026-10-17T02:45:35.131ZHealthy1309
2026-10-15T19:55:09.825ZHealthy1528
2026-10-14T18:40:36.601ZHealthy3018

Tools (7)

execution_benchmarksRank 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_ratesThe 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
attributionWhich 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_attributionWhat 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_transactionClassify 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_pricesCurrent 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_keyMint 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