Is the Cleartracedata Cleartrace MCP server down?

• Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "contract_attribution",
  "description": "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.\n\nMost 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 nothing here, so an empty result for a famous router is not evidence the address is obscure.\n\nAn addr",
  "inputSchema": {
    "type": "object",
    "title": "contract_attributionArguments",
    "required": [
      "address"
    ],
    "properties": {
      "chain": {
        "type": "string",
        "title": "Chain",
        "default": null,
        "description": "One of: ethereum, base, arbitrum, optimism. Omit to return the address's split across all four, which is usually what you want, since the same deployment often appears on several."
      },
      "address": {
        "type": "string",
        "title": "Address",
        "description": "A single contract or wallet address, 0x-prefixed hex. Case-insensitive; checksummed or lowercase both work. One address per call."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Attribution and label for one address"
}

• Added readOnlyHint: false, destructiveHint: false, idempotentHint: false (inferred from the name). (verify)

{
  "name": "execution_benchmarks",
  "description": "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).\n\nThis score measures SLIPPAGE ONLY. Revert rates and MEV exposure are tracked as separate metrics and are deliberately not folded in, so do not present this as an overall 'best execution' ranking -- a venue can score well here and fai",
  "inputSchema": {
    "type": "object",
    "title": "execution_benchmarksArguments",
    "properties": {
      "chain": {
        "type": "string",
        "title": "Chain",
        "default": "all",
        "description": "One of: ethereum, base, arbitrum, optimism, or 'all' (the default) for the blended cross-chain rollup. Do not describe the blend as one chain's result."
      },
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 20,
        "description": "Rows to return, 1-100, default 20. Values outside that range are clamped, not rejected. The ceiling is deliberately low because results land in a context window, where a large page evicts the conversation."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "DEX and aggregator execution benchmark"
}

• Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "explain_transaction",
  "description": "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.\n\nConfidence 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. Pass that qualification through instead of stating the frontend flatly.\n\n`estimated_volume_usd` (o",
  "inputSchema": {
    "type": "object",
    "title": "explain_transactionArguments",
    "required": [
      "tx_hash"
    ],
    "properties": {
      "deep": {
        "type": "boolean",
        "title": "Deep",
        "default": false,
        "description": "Run the deeper classification pass. Slower. Worth setting only when the default pass came back unattributed."
      },
      "chain": {
        "type": "string",
        "title": "Chain",
        "default": "ethereum",
        "description": "One of: ethereum, base, arbitrum, optimism. Defaults to ethereum, and an unrecognised value falls back to ethereum rather than failing, so pass the transaction's actual chain explicitly."
      },
      "price": {
        "type": "boolean",
        "title": "Price",
        "default": false,
        "description": "Include price and value context alongside the routing classification."
      },
      "tx_hash": {
        "type": "string",
        "title": "Tx Hash",
        "description": "The transaction hash, 0x-prefixed hex. Must exist on `chain`: this does not search the other chains, so a hash from the wrong chain returns nothing rather than an error."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Explain one transaction's routing and origin"
}