web3ctx MCP server

web3ctx

The last mile before your agent signs.

Human-validated, chain-run web3 integration recipes, served version-true over MCP.

Five tools

A real answer

“how do I bridge USDC with CCTP” — one call to the authless endpoint, 2026-08-28:

{
  "intent": "lookup",
  "recipe": {
    "project_id": "cctp",
    "version": "2",
    "recipe_type": "usdc-bridge-send",
    "last_validated": "2026-08-07",
    "validated_by": "farseen (github: FarseenSh)",
    "receipts": {
      "validated_on": "2026-08-07",
      "validated_by": "farseen (github: FarseenSh)",
      "checks": [
        "attest",
        "test"
      ],
      "chains_exercised": [
        "base-sepolia",
        "arbitrum-sepolia"
      ],
      "on_chain": [
        {
          "kind": "txHash",
          "hash": "0xd4b4e6395f52ad726dd6062e7a7ec47a2d3a7875d36f20fbb154cde756a3d0f5",
          "role": "approve",
  // … 207 more lines — the receipts, the
  // validated recipe body, and ten citations each pinned to a commit or an exact package version.

The whole response is 26,191 bytes (sha256 bc58a9feba1f6309…) and it publishes byte-for-byte: evidence/showcase/cctp-search.json. Diff it against your own call.

Why this exists

It does not get fooled by a wrong premise. Ten questions built on premises verified false before the run — an archived repo, a renamed package, a version that does not exist. web3ctx was deceived 0 of 10; every other arm was deceived at least once (1–3 of 10). 🔴 Our own intent=integrate row was deceived once, and it publishes here beside the other: a stray line in one recipe cited an archived repository. The ten traps and every arm’s answer →

Citations you can re-fetch. Every unit carries project@version and a URL pinned to a 40-character commit: 142 of 144 across the audited payloads, against ~0 for every tool compared. The audit protocol →

When it does not know, it says so. Asked about eight projects it does not index, it declines all eight and names what would resolve each one. Competitors answer most of them. ⚠ Zero confabulated rows anywhere, including ours — that column separates nobody, and it is reported rather than claimed as an advantage. Abstention honesty →

The recipes are the moat. Each one was run by a human against live chains and ships with the transaction receipts, so anyone can check the claim by RPC rather than trusting the stamp.

Freshness, stated honestly

Shortened. The full README is on GitHub.