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

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `deadchannel-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/plus8bit-deadchannel/deadchannel-mcp.md), [page](https://verifymcp.io/servers/plus8bit-deadchannel/deadchannel-mcp)

## Channel facts

- Registry: `npm`
- Package: `deadchannel-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 19 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 22 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add plus8bit-deadchannel -- npx -y deadchannel-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "plus8bit-deadchannel": {
      "command": "npx",
      "args": [
        "-y",
        "deadchannel-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "plus8bit-deadchannel": {
      "command": "npx",
      "args": [
        "-y",
        "deadchannel-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add plus8bit-deadchannel -- npx -y deadchannel-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "plus8bit-deadchannel": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "deadchannel-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add plus8bit-deadchannel --command npx --arg -y --arg deadchannel-mcp
```

### Hermes

```yaml
mcp_servers:
  plus8bit-deadchannel:
    command: "npx"
    args: ["-y", "deadchannel-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "plus8bit-deadchannel": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "deadchannel-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add plus8bit-deadchannel -t stdio -c npx -a -y deadchannel-mcp
```

### Other

```json
{
  "mcpServers": {
    "plus8bit-deadchannel": {
      "command": "npx",
      "args": [
        "-y",
        "deadchannel-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `deadchannel_probe` (~172 tokens)

Check an x402 endpoint before paying it

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.

Input parameters:

- `method` (string): HTTP verb the resource expects, if known
- `samples` (number): Probes to take, 1-5 (default 2)
- `url` (string, required): The x402 resource URL to check

### `deadchannel_health` (~50 tokens)

Is deadchannel itself up

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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/plus8bit-deadchannel/deadchannel-mcp#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 75
- 2026-09-06: 75
- 2026-09-05: 74
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 73
- 2026-09-01: 73
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 70
- 2026-08-26: 70

## Common questions

### 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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.

## Links

- npm package: https://www.npmjs.com/package/deadchannel-mcp
- Socket report: https://socket.dev/npm/package/deadchannel-mcp
- Repository: https://github.com/plus8bit/deadchannel
- Changelog RSS feed: https://verifymcp.io/servers/plus8bit-deadchannel/deadchannel-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/plus8bit-deadchannel/deadchannel-mcp.json
- HTML version of this page: https://verifymcp.io/servers/plus8bit-deadchannel/deadchannel-mcp