Ledgerbell onchain alerts
REMOTE · LEDGERBELL.QUIETWORKLABS.WORKERS.DEV
Webhook alerts for EVM wallets, contract admin changes, Safe queues and custom events.
Available components
Last scanned (21 minutes ago)
Scores higher than 46% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Crypto and Web3
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_watch). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 582 tokens (~97/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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "test_watch" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 7 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
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Oct 26 57
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 23 Oct 2026 · Probed https://ledgerbell.quietworklabs.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quietworklabs.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6203662d048034ad6156b34972b93b5ae9a |
| SANs: *.quietworklabs.workers.dev, quietworklabs.workers.dev | ||||||
| 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 ledgerbell.quietworklabs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://ledgerbell.quietworklabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://ledgerbell.quietworklabs.workers.dev/mcp | Inconclusive | 405 |
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 →
add_watch Watch an address and alert a webhook ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x address to watch |
| chain | string | yes | – |
| event | string | – | – |
| key | string | yes | Your Ledgerbell API key (from create_api_key) |
| kind | string | yes | – |
| label | string | – | – |
| token | string | – | – |
| webhook | string | yes | Discord/Slack/Telegram/ntfy webhook URL or any HTTPS JSON endpoint |
No output schema declared.
No examples provided.
buy_pro_6d Add 6 days of Ledgerbell Pro ~87
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).
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | Existing key to extend (optional) |
No output schema declared.
No examples provided.
create_api_key Create a Ledgerbell API key ~35
Create a new free-plan API key. Save it: it is the only credential for your watches and cannot be recovered. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_watch Delete a watch ~40
Stop and delete a watch. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| key | string | yes | Your Ledgerbell API key (from create_api_key) |
No output schema declared.
No examples provided.
list_watches List watches and plan ~45
Show plan (free/pro), limits, alerts today and all watches for a key. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Your Ledgerbell API key (from create_api_key) |
No output schema declared.
No examples provided.
test_watch Send a test alert ~48
Send a test alert to a watch's webhook (5 per hour). Free.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
| key | string | yes | Your Ledgerbell API key (from create_api_key) |
No output schema declared.
No examples provided.
How do I install the Ledgerbell onchain alerts MCP server?
Ledgerbell onchain alerts is a hosted endpoint at https://ledgerbell.quietworklabs.workers.dev/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 · ledgerbell.quietworklabs.workers.dev
claude mcp add --transport http dev-workers-quietworklabs-ledgerbell-ledgerbell 'https://ledgerbell.quietworklabs.workers.dev/mcp'
What is the Ledgerbell onchain alerts MCP server?
Ledgerbell onchain alerts is an MCP server listed in the public MCP registry as dev.workers.quietworklabs.ledgerbell/ledgerbell. Webhook alerts for EVM wallets, contract admin changes, Safe queues and custom events. This page covers its hosted endpoint (https://ledgerbell.quietworklabs.workers.dev/mcp).
Is the Ledgerbell onchain alerts MCP server safe to use?
Ledgerbell onchain alerts scores 59 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 Ledgerbell onchain alerts MCP server expose?
Ledgerbell onchain alerts exposes 6 tools: create_api_key, add_watch, list_watches, test_watch, delete_watch, buy_pro_6d. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.
Does the Ledgerbell onchain alerts MCP server require authentication?
No. We connected to Ledgerbell onchain alerts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ledgerbell onchain alerts MCP server still maintained?
Ledgerbell onchain alerts is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.