Log inSubmit server
Deadchannel logo

Deadchannel

Audits x402 endpoints for availability, payment correctness, pricing, network, metadata, latency, and safety signals.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Deadchannel

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "deadchannel": {
      "command": "npx",
      "args": [
        "-y",
        "hosaka-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The deadchannel MCP server checks x402 endpoints for availability, payment requirements, pricing, network details, metadata, latency, and specification errors. It probes unpaid 402 responses, produces a verdict such as live, degraded, trap, testnet, dead, or unknown, and assigns a 0–100 risk score. Reach for it before directing an agent to an unfamiliar x402 resource or before adding endpoint checks to CI.

Use cases

  • Audit an x402 endpoint before an agent pays it
  • Block dead or trap endpoints in CI
  • Scan Bazaar resources for payment and metadata problems
  • Inspect endpoint risk with repeated probes
  • Export verdicts as JSON for automation

Key features

  • Unpaid 402-response probing
  • 0–100 risk scoring and endpoint verdicts
  • v1 and v2 x402 payment parsing
  • Pricing, payout, network, schema, and metadata checks
  • JSON output and CI exit codes
  • Bazaar catalog scanning

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · hosaka-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads167Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.

How Deadchannel works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Deadchannel

deadchannel is an MCP server that connects to x402 endpoints and checks whether they are reachable, correctly priced, payment-compatible, and safe to call. Its main tools are the CLI probe for individual URLs and the catalog scanner for Bazaar resources. Results include a verdict, risk score, and failed or warning checks.

Run it with Node.js 22 or newer using `node src/cli.ts https://x402.org/protected`. The repository states that no runtime dependencies or build step are required. Add `--json` for machine-readable output, or use `--samples 5` to repeat probes.

Yes, deadchannel returns a non-zero exit code when any target receives a `trap` or `dead` verdict. A CI job can therefore fail when a configured endpoint is unavailable or appears unsafe. JSON output is available with the `--json` option for additional automation.

It checks reachability, bot gates, v1 and v2 payment requirements, price enforcement, price range and stability, payout validity, network type, chain recognition, response schema, Bazaar metadata, latency, and payload conformance. It combines these signals into a verdict and a 0–100 risk score.

No, the checker does not require a private key. It evaluates unpaid 402 responses, while the seller configuration uses a public payout address. The service charges $0.005 in USDC on Base for its own probe.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDeadchannel AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/deadchannel?style=directory)](https://allmcps.com/mcp/deadchannel)
HTML Embed
<a href="https://allmcps.com/mcp/deadchannel"><img src="https://allmcps.com/api/badge/deadchannel?style=directory" alt="Deadchannel on AllMCPs" /></a>