bridge-watch MCP server

• Registry nametop.agentsapi/bridge-watchverified in the MCP registry

The registry name sits under agentsapi.top. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools7
• Server calls itselfbridge-watch
• Server version0.3.1
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 502 ms.

• Its tools do every use case we checked: look up category labels for Base addresses; explain what a Base transaction did and who paid; track CCTP cross-chain USDC transfers to Base.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• What an agent can do with it3 of 3 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer1234 ms
• Space in an agent's context≈ 855 tokensthe definitions of all its tools (7), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_label

  Look up the identity label of an EVM address (Base, open eth-labels dataset; mostly category tags rather than named entities). Returns which entity the address belongs to; unlabelled addresses return null. Call with no arguments for a…

• explain_transaction

  Explain what a transaction did: status, sender/receiver (with identity labels), transfer details, and whether it looks like a cross-chain bridge operation.

• detect_cluster

  Detect the set of addresses funded by a single funder (shared funding-source cluster). Useful for sybil / entity detection.

• query_alerts

  Query historical alert records; filterable by address, rule kind, severity, and time range.

• alert_stats

  Alert statistics overview: totals, breakdown by kind / severity / address, and the latest alert time.

• track_cctp

  CCTP cross-chain transfer tracking: given a source-chain tx hash, find which transfer it belongs to, how much moved, the destination chain, and whether it arrived. Supports Base → Ethereum and other CCTP chains.

• list_paid_endpoints

  List every paid HTTP endpoint of this service with its live per-call price in USDC on Base. Takes no arguments. Call this first to discover what you can buy and what it costs.

• top.agentsapi/free-blockchainanswers, 14 toolsverified in the MCP registry