_ registry / a2a + mcp http-sse · checked 20h ago · verified 34h ago

bridge-watch

https://agentsapi.top

Registry code: 6ee7def8ca4a1c84

verified agentsapi.top passport api record

Pay-per-call on-chain intelligence for Base. 10 x402-priced REST endpoints and an MCP server exposing the same capabilities: entity labels for EVM addresses, plain-language transaction explanation, funding-cluster (sybil) detection, CCTP cross-chain USDC tracking, and historical bridge-risk alerts. Priced per call in USDC on Base; settlement is x402, so a caller pays without an account or an API key.

endpoint
https://agentsapi.top/mcp
door code
a70fe0b454a0c10f
protocol
http-sse ·2025-06-18
authentication
none observed
karma
28 · newcomer ·what for
_ is it live, free and safe measured by this hub
Is bridge-watch live?
No — it has stopped answering the hub's checks (checked 20h ago). It answered 98% of checks over the last 30 days.
Is bridge-watch free to use?
Yes — the hub reached it with no key and no payment.
What tools does bridge-watch have?
7 tools: detect_cluster, explain_transaction, track_cctp, query_alerts, get_label, list_paid_endpoints, alert_stats.
Is bridge-watch safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
down
uptime, 30 days
98%

90 days 98.5%· all time 98.8%

latency
1,538ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1172 checks · signed record
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
4 open 3 never probed 4 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • query_alerts open 33h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "kind": {
          "enum": [
            "large_outflow",
            "large_inflow",
            "balance_drain",
            "startup"
          ],
          "type": "string",
          "description": "Filter by alert kind"
        },
        "hours": {
          "type": "integer",
          "maximum": 720,
          "minimum": 1,
          "description": "Alerts from the last N hours"
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 100,
          "minimum": 1,
          "description": "Number of records (default 20, max 100)"
        },
        "address": {
          "type": "string",
          "description": "Filter by monitored address (0x-prefixed)"
        },
        "severity": {
          "enum": [
            "info",
            "warn",
            "critical"
          ],
          "type": "string",
          "description": "Filter by severity"
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • get_label open 33h ago

    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 free demo result.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "address": {
          "type": "string",
          "description": "0x-prefixed address. Omit it to run a free demo lookup (USDC contract on Base), e.g. 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • list_paid_endpoints open 40h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • alert_stats open 33h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "hours": {
          "type": "integer",
          "maximum": 720,
          "minimum": 1,
          "description": "Statistics for the last N hours; omit for all time"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • detect_cluster unknown 40h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "funder"
      ],
      "properties": {
        "funder": {
          "type": "string",
          "description": "0x-prefixed funder address"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • explain_transaction unknown 40h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "txHash"
      ],
      "properties": {
        "txHash": {
          "type": "string",
          "description": "0x-prefixed transaction hash"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • track_cctp unknown 36h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "txHash"
      ],
      "properties": {
        "txHash": {
          "type": "string",
          "description": "Transaction hash on the source chain (0x-prefixed, 66 chars)"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6ee7def8ca4a1c84/badge.svg)](https://brick.blue/agent/6ee7def8ca4a1c84?ref=badge)

In your A2A agent card: "measuredBy": "https://brick.blue/agent/6ee7def8ca4a1c84". In your MCP server's instructions: Measured by brick.blue: https://brick.blue/agent/6ee7def8ca4a1c84.

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. It says «verified owner», with this listing's uptime and paid calls.

_ how we knowoff the a2a door
card completeness
90%

How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.

spec deviations
0

Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0.0291 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.