English Français العربية

bridge-watch on-chain intelligence

Registre officiel Autres

Base on-chain address labels (eth-labels 104k category tags), tx explainer, clusters, CCTP USDC.

Code source Site web Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http bridge-watch-on-chain-intelligence 'https://agentsapi.top/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "bridge-watch-on-chain-intelligence": {
            "type": "http",
            "url": "https://agentsapi.top/mcp"
        }
    }
}
NPM package bridge-watch-mcp
Claude Code 
claude mcp add bridge-watch-on-chain-intelligence -e 'BRIDGE_WATCH_URL=<BRIDGE_WATCH_URL>' -e 'BRIDGE_WATCH_BEARER=<BRIDGE_WATCH_BEARER>' -- npx -y bridge-watch-mcp@0.1.1
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "bridge-watch-on-chain-intelligence": {
            "command": "npx",
            "args": [
                "-y",
                "bridge-watch-mcp@0.1.1"
            ],
            "env": {
                "BRIDGE_WATCH_URL": "<BRIDGE_WATCH_URL>",
                "BRIDGE_WATCH_BEARER": "<BRIDGE_WATCH_BEARER>"
            }
        }
    }
}

Variables d'environnement

  • BRIDGE_WATCH_URL Remote Streamable HTTP endpoint (default https://agentsapi.top/mcp).
  • BRIDGE_WATCH_BEARER Payer wallet address that already sent USDC on Base; sent as Bearer credential (100 credits per 1 USDC).

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. bridge-watch-mcp
  2. Install / run
  3. Free tier
  4. Paying
  5. Environment
  6. How it works
  7. Remote-first alternative
  8. License
  9. 0.1.2 (R218, 2026-10-13)

bridge-watch-mcp

Zero-dependency MCP stdio bridge for the Bridge Watch server: 104,209 on-chain address labels (Base / Ethereum), funding-cluster and CCTP tracing, transaction explanation, plus 7 metered tools paid per call over x402 in USDC on Base.

Node >= 18. No dependencies, no build step, ~10 KB.

Install / run

npx -y bridge-watch-mcp --tools        # print the live tool list (server reachability check)
npx -y bridge-watch-mcp                # run the stdio bridge (this is what MCP clients call)

MCP client config (Claude Desktop, Cursor, Windsurf, Cline, ...):

{
  "mcpServers": {
    "bridge-watch": {
      "command": "npx",
      "args": ["-y", "bridge-watch-mcp"]
    }
  }
}

Free tier

Every IP gets 3 free tool calls per day, no key and no wallet required. get_label accepts no arguments and returns a real demo result, so a fresh client can see working data on the very first call:

{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_label","arguments":{}}}

Paying

  1. Send USDC (Base) to 0x381cdbb664608bf7b1dd4f9403a572c1c57332c2.
  2. Reuse that same address as the credential:
BRIDGE_WATCH_BEARER=0xYourPayerAddress npx -y bridge-watch-mcp

Live per-call prices are published by the server itself — ask the model to call list_paid_endpoints, or read https://agentsapi.top/.well-known/x402. Prices are never hardcoded in this package.

Environment

VariableDefaultMeaning
BRIDGE_WATCH_URLhttps://agentsapi.top/mcpremote Streamable HTTP endpoint
BRIDGE_WATCH_BEARER–payer address (Bearer credential)
BRIDGE_WATCH_PAYMENT–raw payment-signature header (advanced x402 flows)
BRIDGE_WATCH_TIMEOUT_MS60000per-request timeout

How it works

Reads newline-delimited JSON-RPC on stdin, POSTs each message to the remote Streamable HTTP endpoint, and writes back the (SSE-unwrapped) JSON-RPC responses. Notifications (202 Accepted) produce no output. Nothing is logged, nothing is persisted, and the process exits as soon as stdin closes and every in-flight request is answered.

Remote-first alternative

You do not need this package if your client speaks HTTP: point it at https://agentsapi.top/mcp directly.

License

MIT

0.1.2 (R218, 2026-10-13)

  • Fixed LSP Content-Length framing on stdin: the previous newline-splitting parser glued a payload to the next frame header, which made the bridge forward invalid JSON (server answered HTTP 400 / JSON-RPC -32700) or silently drop messages.
  • Anonymous free tier is now 1 call per tool per IP per day across all 7 tools.

Questions fréquentes

Qu'est-ce que bridge-watch on-chain intelligence ?

Base on-chain address labels (eth-labels 104k category tags), tx explainer, clusters, CCTP USDC.

Comment installer bridge-watch on-chain intelligence ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http bridge-watch-on-chain-intelligence 'https://agentsapi.top/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour bridge-watch on-chain intelligence ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

bridge-watch on-chain intelligence est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient bridge-watch on-chain intelligence ?

Il est publié par LakeSky. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.