bridge-watch on-chain intelligence
REMOTE · AGENTSAPI.TOP · SCANNED OCT 9
On-chain address labels (100k+ entities), Base tx explainer, funding clusters, CCTP USDC tracking.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 441 tokens (~73/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the bridge-watch on-chain intelligence MCP server?
bridge-watch on-chain intelligence is a hosted endpoint at https://agentsapi.top/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agentsapi.top
claude mcp add --transport http top-agentsapi-bridge-watch 'https://agentsapi.top/mcp'
{
"mcpServers": {
"top-agentsapi-bridge-watch": {
"url": "https://agentsapi.top/mcp"
}
}
} {
"servers": {
"top-agentsapi-bridge-watch": {
"type": "http",
"url": "https://agentsapi.top/mcp"
}
}
} [mcp_servers.top-agentsapi-bridge-watch] url = "https://agentsapi.top/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"top-agentsapi-bridge-watch": {
"type": "remote",
"url": "https://agentsapi.top/mcp",
"enabled": true
}
}
} openclaw mcp add top-agentsapi-bridge-watch --url 'https://agentsapi.top/mcp' --transport streamable-http
mcp_servers:
top-agentsapi-bridge-watch:
url: "https://agentsapi.top/mcp" {
"McpServers": {
"top-agentsapi-bridge-watch": {
"Transport": "http",
"Url": "https://agentsapi.top/mcp"
}
}
} assistant mcp add top-agentsapi-bridge-watch -t streamable-http -u 'https://agentsapi.top/mcp'
{
"mcpServers": {
"top-agentsapi-bridge-watch": {
"type": "http",
"url": "https://agentsapi.top/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 9 Oct 2026 · Probed https://agentsapi.top/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentsapi.top | CN=YE1,O=Let's Encrypt,C=US | 9 Sept 2026 | 8 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6d307ceb814a7de4f4a9814936a80b76c8a |
| SANs: agentsapi.top | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agentsapi.top. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| top. | present | 26780, 41508 | 8, 13 | Verified |
| agentsapi.top. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agentsapi.top/mcp | Verified | 200 | |
| http (plaintext) | http://agentsapi.top/mcp | HTTPS enforced | 308 | https://agentsapi.top/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
alert_stats ~53
获取告警统计概览：总数、按类型/严重程度/地址分布、最新告警时间
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | 统计最近 N 小时的告警，不填则全部 |
No output schema declared.
No examples provided.
detect_cluster ~55
检测一个出资方地址资助的地址集合（共享资金来源聚类），用于女巫/实体识别
| Name | Type | Req | Description |
|---|---|---|---|
| funder | string | yes | 0x 开头的出资方地址 |
No output schema declared.
No examples provided.
explain_transaction ~61
解释一笔交易做了什么：状态、发起方/接收方（含身份标签）、转账明细、是否疑似跨链桥操作
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | 0x 开头的交易哈希 |
No output schema declared.
No examples provided.
get_label ~84
查询一个 EVM 地址的身份标签（10 万实体标签库：交易所/桥/协议/诈骗等），返回该地址属于哪个实体
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x 开头的地址，如 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
No output schema declared.
No examples provided.
query_alerts ~104
查询历史告警记录，可按地址、规则类型、严重程度、时间范围过滤
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | 按监控地址过滤（0x 开头） |
| hours | integer | – | 查询最近 N 小时的告警 |
| kind | string | – | 按告警类型过滤 |
| limit | integer | – | 返回条数（默认 20，最多 100） |
| severity | string | – | 按严重程度过滤 |
No output schema declared.
No examples provided.
track_cctp ~84
CCTP 跨链卡单追踪：输入源链交易哈希，查询这是哪笔跨链、转了多少、目标链是哪条、是否已到账。支持 Base → Ethereum 等 CCTP 支持的链。
| Name | Type | Req | Description |
|---|---|---|---|
| txHash | string | yes | 源链上的交易哈希（0x 开头，66 字符） |
No output schema declared.
No examples provided.
What is the bridge-watch on-chain intelligence MCP server?
bridge-watch on-chain intelligence is an MCP server listed in the public MCP registry as top.agentsapi/bridge-watch. On-chain address labels (100k+ entities), Base tx explainer, funding clusters, CCTP USDC tracking. This page covers its hosted endpoint (https://agentsapi.top/mcp).
Is the bridge-watch on-chain intelligence MCP server safe to use?
bridge-watch on-chain intelligence scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the bridge-watch on-chain intelligence MCP server expose?
bridge-watch on-chain intelligence exposes 6 tools: get_label, explain_transaction, detect_cluster, query_alerts, alert_stats, track_cctp. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the bridge-watch on-chain intelligence MCP server require authentication?
No. We connected to bridge-watch on-chain intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the bridge-watch on-chain intelligence MCP server still maintained?
bridge-watch on-chain intelligence is still listed as active in the MCP registry. We last reached this channel on 9 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.