# deadchannel [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/plus8bit/deadchannel  
**GitHub Stars:** 1  
**npm Downloads (last month):** 167  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/deadchannel

## Description
Check an x402 endpoint before you pay it: verdict, risk score and what is wrong. $0.001 in USDC.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What deadchannel does

The deadchannel MCP server evaluates whether an x402 endpoint is reachable, correctly describes its payment requirements, and appears safe for an agent to call. It does this without paying the target endpoint: the checks use unpaid `402` responses. The service itself sells a probe for $0.005 in USDC on Base.

Each result includes a verdict and a bounded risk score from 0 to 100. Possible verdicts are `live`, `degraded`, `trap`, `testnet`, `dead`, and `unknown`. The output also identifies the individual checks that passed, failed, or produced warnings, making it possible to see why an endpoint received its result.

## How it works

The probe examines whether the endpoint answers consistently and whether it returns parseable payment requirements. It understands both v1 response bodies and v2 `payment-required` headers, including v2 CAIP-2 network identifiers and the renamed `amount` field. The implementation also accounts for endpoints that use POST rather than GET, retrying with POST when the catalog does not specify a verb.

Checks cover bot-gating, whether a quoted price is enforced, price limits from $0.0001 to $5, price stability across probes, payout-address validity, mainnet availability, recognizable chain identifiers, response schemas, Bazaar discovery metadata, latency, and documented payload shape. Brokered AWS Marketplace payment rails are reported as warnings rather than automatically treated as invalid payouts.

## Setup and configuration

Node.js 22 or newer is required. The repository states that it has no runtime dependencies and uses native type stripping, so there is no build step. Run a single check with:

```text
node src/cli.ts https://x402.org/protected
```

For multiple targets, specify sampling and quiet output as needed:

```text
node src/cli.ts --quiet --samples 5 url-a url-b url-c
node src/cli.ts --json url > verdict.json
```

The scanner can audit resources published by public Bazaar facilitators with `node src/scan.ts --live 150`. No environment variables or private keys are documented for running the probe. The seller endpoint uses a public payout address in `deadchannel.config.json`; that is separate from operating the checker as a CLI.

## Tools and capabilities

The deadchannel MCP server provides the documented command-line probe and catalog scanner rather than a separately documented MCP tool list. The CLI can:

- Check one or more x402 URLs.
- Repeat probes with a selected sample count.
- Emit machine-readable JSON.
- Return a non-zero exit status when any target is classified as `trap` or `dead`.
- Scan live resources from public Bazaar facilitators.

The service also exposes free `GET /`, `GET /health`, and `GET /facilitator` endpoints, plus a paid `POST /probe` endpoint priced at $0.005 in USDC on Base.

## Limitations and notes

The deadchannel MCP server reports observed signals; it does not guarantee that an endpoint will remain available or safe after the probe. An endpoint may be marked degraded or unknown when its responses are incomplete or inconsistent. GET-only probing can falsely classify POST resources as dead, which is why the catalog verb and POST retry matter.

Discovery metadata may appear on the ResourceInfo object, the catalog item root, or under `extensions.bazaar`; the checker reads these known locations. Some endpoints omit fields or place `accepts[]` differently from the documented shape, so those deviations are reported as warnings. The checker also distinguishes testnet-only settlement from networks that can hold real value.

_Full upstream README: https://allmcps.com/mcp/deadchannel/readme_