io.github.plus8bit/deadchannel
NPM · DEADCHANNEL-MCP
Check an x402 endpoint before you pay it: verdict, risk score and what is wrong. $0.005 in USDC.
Available components
Last scanned (28 minutes ago)
Scores higher than 82% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 20 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 68 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 340 tokens (~170/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 +3
- CVE-2023-54404 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 24 Oct 26 −3
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.77 functional
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 5 Nov 2026 · Analysed npm/deadchannel-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 20 packages
| Packages resolved | 20 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
deadchannel_health Is deadchannel itself up ~50
Reports whether the risk checker is running and able to settle payments. Free, and needs no wallet — use it to tell 'the service is down' apart from 'my key is wrong' before probing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deadchannel_probe Check an x402 endpoint before paying it ~172
Grades an x402 endpoint you are considering paying. Returns a verdict (live, degraded, trap, testnet, dead), a 0-100 risk score, the price it actually challenges for, the networks it settles on, and the specific problems found — a testnet address advertised as mainnet, a price that no longer matches its listing, a challenge that never settles. Use it whenever the seller is unfamiliar, especially when the payment is larger than a few cents. Costs $0.005 in USDC, which is less than the smallest payment it protects.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | HTTP verb the resource expects, if known |
| samples | number | – | Probes to take, 1-5 (default 2) |
| url | string | yes | The x402 resource URL to check |
No output schema declared.
No examples provided.
How do I install the io.github.plus8bit/deadchannel MCP server?
io.github.plus8bit/deadchannel runs locally as an npm package, launched with npx -y deadchannel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · deadchannel-mcp
claude mcp add plus8bit-deadchannel -- npx -y deadchannel-mcp
What is the io.github.plus8bit/deadchannel MCP server?
io.github.plus8bit/deadchannel is an MCP server listed in the public MCP registry as io.github.plus8bit/deadchannel. Check an x402 endpoint before you pay it: verdict, risk score and what is wrong. $0.005 in USDC. This page covers its npm package (deadchannel-mcp).
Is the io.github.plus8bit/deadchannel MCP server safe to use?
io.github.plus8bit/deadchannel scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.plus8bit/deadchannel MCP server expose?
io.github.plus8bit/deadchannel exposes 2 tools: deadchannel_probe, deadchannel_health. Their descriptions and schemas cost roughly 222 tokens of context every time the server is loaded.
Is the io.github.plus8bit/deadchannel MCP server still maintained?
io.github.plus8bit/deadchannel is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.plus8bit/deadchannel MCP server under?
io.github.plus8bit/deadchannel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.