_ registry / mcp streamable-http · checked 2h ago

dev.workers.quietworklabs.ledgerbell/ledgerbell

https://ledgerbell.quietworklabs.workers.dev

Registry code: b289fa54afc2e447

api record

Ledgerbell watches EVM addresses on Base, Ethereum, Arbitrum and Optimism and posts alerts to a webhook (Discord, Slack, Telegram, ntfy or any JSON URL). Watch kinds: wallet (ERC-20 transfers in/out, new token approvals), contract (proxy upgrades, ownership/role changes, pauses, Safe owner/threshold/module changes, timelock and governor events), event (any custom event signature), safe_queue (Pro: Safe transactions queued but not yet executed). Flow: create_api_key once, then add_watch with a webhook URL, then test_watch. Free plan: 3 watches, 50 alerts/day. Pro: 30 watches, 1,000 alerts/day,…

endpoint
https://ledgerbell.quietworklabs.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is dev.workers.quietworklabs.ledgerbell/ledgerbell live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is dev.workers.quietworklabs.ledgerbell/ledgerbell free to use?
Yes — the hub reached it with no key and no payment.
What tools does dev.workers.quietworklabs.ledgerbell/ledgerbell have?
6 tools: create_api_key, test_watch, delete_watch, add_watch, buy_pro_6d, list_watches.
Is dev.workers.quietworklabs.ledgerbell/ledgerbell 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
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
73ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 4 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
1

distinct

settlements
1

last 2026-10-18

received on chain
0.001 USDC

counted from three payers (thin, concentrated, shared-payto)

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 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.

  • create_api_key unknown never probed

    Create a new free-plan API key. Save it: it is the only credential for your watches and cannot be recovered. Free.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • test_watch unknown never probed

    Send a test alert to a watch's webhook (5 per hour). Free.

    mcp-tool

    {
  "type": "object",
  "required": [
    "key",
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer"
    },
    "key": {
      "type": "string",
      "description": "Your Ledgerbell API key (from create_api_key)"
    }
  }
}
    arguments 16 lines
  • delete_watch unknown never probed

    Stop and delete a watch. Free.

    mcp-tool

    {
  "type": "object",
  "required": [
    "key",
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer"
    },
    "key": {
      "type": "string",
      "description": "Your Ledgerbell API key (from create_api_key)"
    }
  }
}
    arguments 16 lines
  • add_watch unknown never probed

    Start watching an address. kind=wallet|contract|event|safe_queue. For kind=event pass event as a signature like Transfer(address,address,uint256) or a topic0. Optional token (wallet kind: only this ERC-20) and label. Free.

    mcp-tool

    {
  "type": "object",
  "required": [
    "key",
    "chain",
    "kind",
    "address",
    "webhook"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Your Ledgerbell API key (from create_api_key)"
    },
    "kind": {
      "enum": [
        "wallet",
        "contract",
        "event",
        "safe_queue"
      ],
      "type": "string"
    },
    "chain": {
      "enum": [
        "base",
        "ethereum",
        "arbitrum",
        "optimism"
      ],
      "type": "string"
    },
    "event": {
      "type": "string"
    },
    "label": {
      "type": "string"
    },
    "token": {
      "type": "string"
    },
    "address": {
      "type": "string",
      "description": "0x address to watch"
    },
    "webhook": {
      "type": "string",
      "description": "Discord/Slack/Telegram/ntfy webhook URL or any HTTPS JSON endpoint"
    }
  }
}
    arguments 51 lines
  • buy_pro_6d unknown never probed

    Adds 6 days of Pro to the given key (or creates a new Pro key if none is given): 30 watches, 1,000 alerts/day, Safe queued-transaction alerts, proxy-upgrade reports. Call again to extend. Price: $1 USDC per call via x402 (Base).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "Existing key to extend (optional)"
    }
  }
}
    arguments 9 lines
  • list_watches unknown 2h ago

    Show plan (free/pro), limits, alerts today and all watches for a key. Free.

    mcp-tool

    {
  "type": "object",
  "required": [
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Your Ledgerbell API key (from create_api_key)"
    }
  }
}
    arguments 12 lines
_ try it 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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b289fa54afc2e447.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b289fa54afc2e447/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b289fa54afc2e447/badge.svg)](https://brick.blue/agent/b289fa54afc2e447?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.

_ how we know
card completeness
100%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ 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 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.