Local MCP server/Development

Bridge Watch MCP server

Local MCP server

Bridge Watch is an on-chain data service with 104,209 address labels for Base and Ethereum, funding-cluster and CCTP tracing, transaction explanation, and 7 metered tools paid per call over x402 in USDC on Base. The repository ships a zero-dependency stdio bridge, npx -y bridge-watch-mcp, for Node 18 or newer; a remote Streamable HTTP endpoint also exists at https://agentsapi.top/mcp. The free tier allows 3 anonymous calls a day, and paid calls use the payer wallet address as a Bearer credential.

No key for the 3-call/day free tier; paid x402 calls use the payer wallet address as a Bearer credential Local install path Reviewed 2026-11-16
About

Where it fits

Developers and analysts working with Base or Ethereum addresses who want a lightweight local bridge.

  • Look up an on-chain address label.
  • Trace funding clusters or CCTP transfers.
  • Call a metered tool with an x402 payer credential.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local stdio bridge

Node.js 18 or newer. The free tier allows 3 anonymous calls a day; paid x402 calls require the payer wallet address as a Bearer credential. npx -y bridge-watch-mcp --tools prints the live tool list.

  1. Check the tool list

    Print the live tools before wiring the client.

    npx -y bridge-watch-mcp --tools
  2. Add the stdio command

    Register npx -y bridge-watch-mcp as a local stdio server in Claude Desktop, Cursor, Windsurf, or Cline.

  3. Choose free or paid calls

    Anonymous calls are limited to 3 a day. For the 7 x402-metered tools, use the payer wallet address as the Bearer credential.

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider source

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Bridge Watch repositoryhttps://github.com/LakeSky/bridge-watch-mcp