Neutral on-chain execution benchmarking: slippage, revert rates, MEV, and DEX frontend attribution.
| Endpoint | https://cleartracedata.com/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.0 |
| Now | 7 tools · grade B (86) · pin ts_084f5a1c4cdbe14ca202589be4b4074b · protocol 2025-06-18 |
| First / last listed | 2026-11-01 01:50 UTC / 2026-11-01 01:50 UTC |
| Grade over time | 2026-11-01: B (86), 7 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: execution_benchmarks revert_rates attribution contract_attribution explain_transaction gas_prices request_api_key
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 and MEV exposure are tracked as separate metrics and are deliberately not folded in, params: chain, limit |
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 'router' venue, where the user signs and submits the swap. On a batch-auction or intent venue a solver se params: chain, project, comparable_only, limit |
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 TOGETHER. `direct_volume_usd`, `aggregator_volume_usd`, `proxy_volume_usd` and `aggregator_partner_vo params: chain, project, limit |
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. Known, named protocol contracts are often keyed by name rather than address upstream and may return n params: address*, chain |
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 specific frontend tagged the swap, while a fee recipient is indirect evidence and is never rated high params: tx_hash*, chain, deep, price |
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 lower bound and should be labelled as one; comparing an L2 'cost' against Ethereum's on this basis o params: none |
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 unlocking content. Ask the user before submitting their email; do not invent an address to satisfy params: email*, use_case, name, company |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.