deadchannel-mcp

MCPcommunity
v0.1.1io.github.plus8bitMITUpdated 1mo agonpmGitHub

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

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Reads these credentials
  • DEADCHANNEL_PRIVATE_KEYAPI keyoptional

    Private key of a wallet holding a little USDC on Base. It signs payments locally and never leaves the machine. Not needed for the free health check.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.plus8bit
LicenseMIT
Version0.1.1
Sourcenpm+mcp-registry
npmdeadchannel-mcp
GitHubplus8bit/deadchannel
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 19 resolved · none vulnerable
Tool surface2 tools · none privileged
Security scan✓ Cleanv0.1.1 · 11d agoHow well does this scan work?
EvalsNone
IndexedAug 27, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged
Statically extracted from the published packagev0.1.1 · 11d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

deadchannel_probeNo description published

This tool published no description. Forge does not invent one.

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

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.

No input schema was published for this tool.

1 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

2 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-23 — observed resolution, not a publisher declaration.

19 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.