bridge-watch on-chain intelligence
Base on-chain address labels (eth-labels 104k category tags), tx explainer, clusters, CCTP USDC.
التثبيت
أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: .cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).
claude mcp add --transport http bridge-watch-on-chain-intelligence 'https://agentsapi.top/mcp'
{
"mcpServers": {
"bridge-watch-on-chain-intelligence": {
"type": "http",
"url": "https://agentsapi.top/mcp"
}
}
}
bridge-watch-mcpclaude 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
{
"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>"
}
}
}
}
متغيرات البيئة
BRIDGE_WATCH_URLRemote Streamable HTTP endpoint (default https://agentsapi.top/mcp).BRIDGE_WATCH_BEARERPayer wallet address that already sent USDC on Base; sent as Bearer credential (100 credits per 1 USDC).
التوثيق
مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.
المحتويات
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
- Send USDC (Base) to
0x381cdbb664608bf7b1dd4f9403a572c1c57332c2. - 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
| Variable | Default | Meaning |
|---|---|---|
BRIDGE_WATCH_URL | https://agentsapi.top/mcp | remote Streamable HTTP endpoint |
BRIDGE_WATCH_BEARER | – | payer address (Bearer credential) |
BRIDGE_WATCH_PAYMENT | – | raw payment-signature header (advanced x402 flows) |
BRIDGE_WATCH_TIMEOUT_MS | 60000 | per-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-Lengthframing 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.
الأسئلة الشائعة
ما هو bridge-watch on-chain intelligence؟
Base on-chain address labels (eth-labels 104k category tags), tx explainer, clusters, CCTP USDC.
كيف أثبّت bridge-watch on-chain intelligence؟
يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http bridge-watch-on-chain-intelligence 'https://agentsapi.top/mcp'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.
هل يحتاج bridge-watch on-chain intelligence إلى مفتاح API؟
لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.
هل bridge-watch on-chain intelligence مفتوح المصدر؟
نعم. شيفرته متاحة على GitHub بترخيص MIT.
من يصون bridge-watch on-chain intelligence؟
ينشره LakeSky. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.
من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.