NebulaScan
https://nebula-scan-ten.vercel.app
Registry code: 20f8ec183279028d
Explore NebulaScan bridge monitoring via tools/list.
- endpoint
- https://nebula-scan-ten.vercel.app/mcp
- protocol
- streamable-http ·2024-11-05
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is NebulaScan live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is NebulaScan free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does NebulaScan have?
- 5 tools: flow_analytics, bridge_monitor, exploit_scanner, peg_checker, relay_health.
- Is NebulaScan 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.
90 days 99%· all time 99%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- monitor bridge inflows and outflows
- scan bridges for exploit patterns
- check wrapped asset peg
- check bridge relay health
- takes → gives
- text → data
- tools
- 5 reads
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.
through this hub
successful
what callers paid
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.
relay_health reads open 10h ago
Check the health and latency of bridge relay nodes connecting to Base.
{ "type": "object", "required": [ "chain" ], "properties": { "chain": { "enum": [ "ethereum", "arbitrum", "optimism", "polygon", "all" ], "type": "string", "description": "Source chain" } } }arguments 19 linesflow_analytics reads unknown never probed
Aggregate and analyze cross-chain capital flow patterns over a given period.
{ "type": "object", "required": [ "period" ], "properties": { "period": { "enum": [ "1h", "24h", "7d", "30d" ], "type": "string", "description": "Analysis period" } } }arguments 18 linesbridge_monitor reads unknown never probed
Track real-time inflows and outflows for all major bridges connected to Base.
{ "type": "object", "required": [ "bridge" ], "properties": { "bridge": { "enum": [ "official", "stargate", "across", "hop", "all" ], "type": "string", "description": "Bridge to monitor" }, "min_value_usd": { "type": "number", "description": "Minimum transfer value in USD" } } }arguments 23 linesexploit_scanner reads unknown never probed
Scan for known bridge exploit patterns including reentrancy, oracle manipulation, and relay fraud.
{ "type": "object", "required": [ "target" ], "properties": { "depth": { "enum": [ "surface", "deep" ], "type": "string", "description": "Scan depth" }, "target": { "type": "string", "description": "Bridge contract address or name" } } }arguments 20 linespeg_checker reads unknown never probed
Validate the peg integrity of wrapped/bridged assets against their canonical counterparts.
{ "type": "object", "required": [ "asset" ], "properties": { "asset": { "type": "string", "description": "Wrapped asset symbol (e.g., WETH, USDbC)" } } }arguments 12 lines
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.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id20f8ec183279028d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/20f8ec183279028d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/20f8ec183279028d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.