Vérifie les endpoints x402 pour fournir un verdict, un score de risque et une analyse détaillée de leur état de fonctionnement, de la cohérence de leurs prix et de leur sécurité lors de l'appel.
Aussi connu sous plus8bit/deadchannel, deadchannel-mcp, hosaka-mcp
- Étoiles
- 1
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- 0.1.1
- Dernier commit
- 5 sept. 2026
- Licence
- —
Qu'est-ce que deadchannel MCP ?
Vérifie les endpoints x402 pour fournir un verdict, un score de risque et une analyse détaillée de leur état de fonctionnement, de la cohérence de leurs prix et de leur sécurité lors de l'appel.
Résumé généré à partir du README du projet
À propos du MCP server deadchannel
deadchannel permet de vérifier que les endpoints x402 sont fonctionnels et sûrs avant qu'un agent ne mobilise des fonds. Il agit comme un oracle de risque pour les développeurs et les agents IA interagissant avec l'écosystème x402, en fournissant un verdict, un score de risque et une analyse détaillée pour déterminer si une URL spécifique est active, honnêtement tarifée et sécurisée.
Les utilisateurs peuvent exécuter le service via une CLI ou l'intégrer à leurs workflows pour éviter de dépenser de l'argent sur des endpoints inactifs ou trompeurs. L'outil analyse divers signaux, notamment la joignabilité, la détection de bots, la stabilité des prix et la conformité de l'endpoint aux exigences de paiement spécifiques. Il identifie des problèmes tels que les endpoints dont la porte est fermée mais qui affichent des prix non appliqués, ou les réseaux de testnet incapables d'accepter de la valeur réelle.
L'installation du serveur nécessite Node 22+ et ne comporte aucune dépendance au runtime ni étape de build complexe. Bien que la sonde elle-même coûte 0,005 $ en USDC sur Base, les vérifications initiales sont gratuites. Cela permet aux agents d'auditer un catalogue de ressources sans engager de frais avant d'effectuer une sonde formelle.
Ce que vous pouvez faire avec
- 1Prévenir le gaspillage de paiementsUn agent IA peut vérifier un endpoint pour s'assurer qu'il ne s'agit pas d'un piège ou d'un lien mort avant de tenter une transaction.
- 2Valider l'intégrité des prixLes développeurs peuvent utiliser l'outil pour confirmer que le prix annoncé d'un endpoint est stable et respecte un budget raisonnable.
- 3Automatiser l'audit des endpointsIntégrez le service dans un pipeline CI pour empêcher le déploiement d'agents pointant vers des endpoints invalides ou défectueux.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer deadchannel MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller deadchannel MCP dans Claude Code
$ claude mcp add --env 'DEADCHANNEL_PRIVATE_KEY=<YOUR_DEADCHANNEL_PRIVATE_KEY>' deadchannel -- npx -y deadchannel-mcpInstaller deadchannel MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"deadchannel": {
"command": "npx",
"args": [
"-y",
"deadchannel-mcp"
],
"env": {
"DEADCHANNEL_PRIVATE_KEY": "<YOUR_DEADCHANNEL_PRIVATE_KEY>"
}
}
}
}Installer deadchannel MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"deadchannel": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"deadchannel-mcp"
],
"env": {
"DEADCHANNEL_PRIVATE_KEY": "<YOUR_DEADCHANNEL_PRIVATE_KEY>"
}
}
}
}Installer deadchannel MCP dans VS Code CLI
$ code --add-mcp '{"name":"deadchannel","type":"stdio","command":"npx","args":["-y","deadchannel-mcp"],"env":{"DEADCHANNEL_PRIVATE_KEY":"<YOUR_DEADCHANNEL_PRIVATE_KEY>"}}'Installer deadchannel MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"deadchannel": {
"command": "npx",
"args": [
"-y",
"deadchannel-mcp"
],
"env": {
"DEADCHANNEL_PRIVATE_KEY": "<YOUR_DEADCHANNEL_PRIVATE_KEY>"
}
}
}
}Installer deadchannel MCP dans Codex
$ codex mcp add deadchannel --env 'DEADCHANNEL_PRIVATE_KEY=<YOUR_DEADCHANNEL_PRIVATE_KEY>' -- npx -y deadchannel-mcpInstaller deadchannel MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.deadchannel] command = "npx" args = ["-y", "deadchannel-mcp"] [mcp_servers.deadchannel.env] DEADCHANNEL_PRIVATE_KEY = "<YOUR_DEADCHANNEL_PRIVATE_KEY>"
Installer deadchannel MCP dans Gemini CLI
$ gemini mcp add -s user -e 'DEADCHANNEL_PRIVATE_KEY=<YOUR_DEADCHANNEL_PRIVATE_KEY>' deadchannel npx -- -y deadchannel-mcpInstaller deadchannel MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"deadchannel": {
"command": "npx",
"args": [
"-y",
"deadchannel-mcp"
],
"env": {
"DEADCHANNEL_PRIVATE_KEY": "<YOUR_DEADCHANNEL_PRIVATE_KEY>"
}
}
}
}Configuration
DEADCHANNEL_PRIVATE_KEYSecretPrivate 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.
DEADCHANNEL_URLOverride the service endpoint. Defaults to https://deadchannel.vercel.app
HOSAKA_PRIVATE_KEY
| Nom | Description | Type |
|---|---|---|
| DEADCHANNEL_PRIVATE_KEY | 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. | Secret |
| DEADCHANNEL_URL | Override the service endpoint. Defaults to https://deadchannel.vercel.app | |
| HOSAKA_PRIVATE_KEY | — |
Vérifications automatisées
Exécuté le 15 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessibleplus8bit/deadchannel is public and reachablegithub.com/plus8bit/deadchannel ↗Réussi
- Le nom du package correspond au dépôt sourcedeadchannel-mcp, hosaka-mcp name plus8bit/deadchannel as sourcenpmjs.com/package/deadchannel-mcp ↗Réussi
- Provenance du build (attestation Sigstore)No build attestation published for this releaseNon vérifié
- Licence open source (OSI)No licenseFaille
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-09-05github.com/plus8bit/deadchannel ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNo popular package one edit away from deadchannel-mcp, hosaka-mcpRéussi
- Aucun avis critique dans le package ou ses dépendances18 resolved dependencies checked; no critical advisoryosv.dev ↗Réussi
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHubdeadchannel & Hosaka
Two services that sell to AI agents over x402, paid per call in USDC. No signup, no API key, no subscription — an agent calls, pays, and gets an answer.
| what it sells | price | |
|---|---|---|
| Hosaka | which third-party vendors a company uses, proven from its own DNS, plus contacts | $0.005 – $0.40 |
| deadchannel | whether an x402 endpoint is alive, honestly priced and safe to call | $0.005 |
Agents can install Hosaka as a skill, which tells them what it is for and when to reach for it:
npx skills add plus8bit/deadchannel/skills/hosaka --yes
Hosaka — company data for agents
Available as an MCP server, so any MCP client can buy from it directly:
npx -y hosaka-mcp
{
"mcpServers": {
"hosaka": {
"command": "npx",
"args": ["-y", "hosaka-mcp"],
"env": { "HOSAKA_PRIVATE_KEY": "0x…" }
}
}
}
HOSAKA_PRIVATE_KEY is a wallet holding a little USDC on Base. Four tools at
four prices, so a cheap question never pays for an expensive answer:
| tool | price | what you get |
|---|---|---|
hosaka_lookup |
$0.005 | domain age, registrar, mail and DNS provider, DMARC, HTTPS, vendor count |
hosaka_contacts |
$0.02 | the dossier, plus the emails and phones the company publishes about itself |
hosaka_dossier |
$0.02 | every third-party vendor the company can be proven to use, each with its proof |
hosaka_people |
$0.35 | the dossier, plus named people who work there |
Why the dossier is worth having. A company proves it owns its domain to every SaaS product it buys by placing a DNS verification record, and authorises every sender it uses in its SPF record. Those two lists are a purchase history the company published itself.
Asking for figma.com returns Anthropic, OpenAI, Adobe, Atlassian, MongoDB
Atlas, Greenhouse, Docusign, Stripe, Notion, Dropbox and Zendesk — each with the
exact record that proves it, so a buyer can check rather than trust.
Page fingerprints require a loaded script or CDN host, never a mention: a site listing a vendor's logo among its integrations is not a site that uses it.
Live at hosaka-agents.vercel.app.
deadchannel — a risk oracle for x402 endpoints
Give it a URL, it tells an agent whether that endpoint is alive, honestly priced, and safe to call — without spending a cent.
Roughly 17% of probed x402 endpoints are dead or traps, and the Bazaar discovery layer ships no ranking, quality, or reputation signal by its own admission. An agent picking from that catalog is guessing with real money.
What it checks
Every verdict comes from unpaid 402 responses, which is what makes it cheap
enough to run across a whole catalog.
| Signal | What it catches |
|---|---|
reachable |
Endpoint answers at all, consistently |
bot-gate |
A bot wall answers agents while browsers get a clean 402 — the endpoint is invisible to indexers |
speaks-402 |
Returns parseable payment requirements (v1 body and v2 payment-required header) |
gate-closed |
Advertises a price it does not enforce — anyone can take the content free |
price-sane |
Price sits inside $0.0001–$5; above the ceiling one call can drain a budget |
price-stable |
Quote does not move between probes taken seconds apart |
pay-to-valid |
Payout address is well formed for its chain and is not a burn address |
network-mainnet |
Settles somewhere that can hold real value, not testnet only |
network-known |
Chain identifier is recognizable (CAIP-2 or friendly name) |
schema-advertised |
Agent can know the response shape before paying |
bazaar-metadata |
Publishes serviceName / tags so topic search can find it |
latency |
p99 inside the 5s budget agents typically allow |
spec-clean |
Payload matches the documented shape; deviations are reported, not swallowed |
Verdicts: live, degraded, trap, testnet, dead, unknown, plus a
bounded 0–100 risk score.
Use
Requires Node 22+. There are no runtime dependencies — types are stripped natively, so there is no build step and nothing to audit but this repo.
node src/cli.ts https://x402.org/protected
node src/cli.ts --quiet --samples 5 url-a url-b url-c
node src/cli.ts --json url > verdict.json
Exit code is non-zero when any target is a trap or dead, so it drops into CI
as a guard against shipping an agent pointed at a bad endpoint.
TESTNET risk 80 $0.01 355ms p99 https://x402.org/protected
x network-mainnet Only testnet networks offered (base-sepolia, solana-devnet).
This endpoint cannot accept real value.
! schema-advertised No input or output schema. An agent has to pay before it
can find out what it gets back.
First full catalog scan — 20 Aug 2026
node src/scan.ts --live 150 pulls every resource the public Bazaar facilitators
publish and audits it. Results over 14,979 resources:
| catalog held by the top 3 payout addresses | 18.4%, receiving 1 call in 80 |
| publish no discovery tags | 40.9% — an agent searching by topic never finds them |
| pass every check | 56.8% |
| of the 150 busiest, live right now | 91.3% |
| of the busiest, genuinely dead | 2.0% |
Median price $0.01, range $0 to $1,000, 316,927 paid calls in 30 days.
The catalog is in better shape than the folklore suggests. What it is not is evenly distributed: three addresses list 2,750 resources between them and receive one call in eighty, which makes them roughly 15x over-represented relative to the demand they serve. Catalog size is not catalog depth.

A correction, and the guard against repeating it
An earlier version of this table claimed 89.8% of the catalog published no tags.
That was wrong. The loader read extensions.bazaar.tags only, while most
publishers put tags on the item root — the real figure is 40.9%.
The bug survived review because nothing asserted the positive count. A check
that only ever counts what is missing cannot tell "publishers omit this" apart
from "we are looking in the wrong place." test/catalog.test.ts now hand-counts
tags across all three known locations in a captured 200-item slice of the live
catalog and asserts the loader matches exactly, in both directions.
Notes from the wild
Built against live endpoints, not the spec alone:
- v2 moves payment requirements into a base64
payment-requiredheader and leaves the body as{}. A parser that only reads the body marks the official reference endpoint as dead. - v2 sends CAIP-2 network ids (
eip155:84532,solana:EtWTRA…) where v1 sent friendly names. Both are live simultaneously. - v2 renames
maxAmountRequiredtoamountand hoists sharedresourcemetadata to the payload root. - Several servers omit the top-level
x402Versionthe reference implementations all send, and some nestaccepts[]one level deeper than documented. Both are parsed and reported as warnings rather than rejected. - Most resources are POST. Probing them with GET returns 404/405, which looks exactly like a dead endpoint — it put our first live-probe dead rate at 25% when the real figure is 2.7%. The verb comes from the catalog now, with a POST retry when it is unknown. Any x402 index reporting a high dead rate is worth checking for this.
- Discovery metadata is scattered. The spec puts
serviceName/tagson the ResourceInfo object, the CDP catalog flattens them onto the item root, and a minority nest them underextensions.bazaar. Read one location and you will undercount by half. - Brokered rails exist. AWS Marketplace resources name the payee with a URN
under an
aws:basenetwork instead of a chain address. That is legitimate, but the funds go to the broker, so it is reported as a warning rather than scored as an invalid payout.
Selling
The service sells its own check over x402. src/server/ implements the seller
side of the v2 HTTP transport: PAYMENT-REQUIRED out, PAYMENT-SIGNATURE in,
PAYMENT-RESPONSE back, in the authorization flow — verify, run the resource,
then settle.
No private key is involved. A seller declares where settlement should land;
the buyer signs and the facilitator broadcasts. The payout address is therefore
public information and lives in deadchannel.config.json, where anyone can
audit it, rather than in a dashboard where nobody can.
Settlement runs only after the probe produced a result, so a failure on our side costs the buyer nothing.
GET / service card, free
GET /health liveness, free
GET /facilitator proves credentials are accepted, free, moves no money
POST /probe the check, $0.005 in USDC on Base
GET /facilitator exists because a wrong credential otherwise stays invisible
until someone tries to pay, and the first to discover it would be a customer.
Live
The service is deployed at https://deadchannel.vercel.app, selling on Base mainnet at $0.005 per call and settling through the Coinbase facilitator.
First settled payment: 0x6ac4a22c,
block 50230005, 20 Aug 2026. Gas was paid by the facilitator, not the buyer —
in x402 the buyer only signs, so a wallet holding nothing but USDC can pay.
npm run validate re-runs the 25 preflight checks the Bazaar applies before it
will index a resource, and reports whether the listing is currently active. It
needs no key and moves no money.
resource : https://deadchannel.vercel.app/probe
valid : true
accepted : accepted
checks : 25/25 passed
indexed : active=true
Hosaka
A second shop on the same payout address, selling company facts to agents.
POST /lookup $0.005 domain age, registrar, mail and DNS provider, DMARC, HTTPS
POST /dossier $0.02 every third-party vendor we can prove, with the proof
Live at https://hosaka-agents.vercel.app, settling on Base mainnet.
Profiles are assembled from four sources that need no key and no supplier: DNS over HTTPS, the RDAP registry, the TLS handshake and the homepage. Cost per profile is zero — the margin is in the assembly.
The interesting part is vendor detection. A company proves ownership to every SaaS product it buys by placing a DNS verification record, and authorises every sender it uses in its SPF record. Those two lists are a purchase history the company published itself. Every claim carries the record that proves it, so a buyer can check rather than trust.
Using it from Claude or ChatGPT
The Bazaar's search ignores the query and ranks by unique payers, so a new shop is invisible there regardless of quality. MCP is the channel that works on day one — the agent is already in a client that speaks it.
{
"mcpServers": {
"hosaka": {
"command": "node",
"args": ["/absolute/path/to/src/hosaka/mcp/server.ts"],
"env": { "HOSAKA_PRIVATE_KEY": "0x…" }
}
}
}
The buyer brings their own wallet: the key signs the payment locally and never leaves the machine. Without it the tools say what is missing instead of failing mid-conversation.
Development
npm install # typescript only, for typechecking
npm test # 18 tests, no network required
npm run typecheck
License
MIT
Questions sur deadchannel MCP
Comment ajouter deadchannel MCP à Claude Code ?
Exécutez claude mcp add --env 'DEADCHANNEL_PRIVATE_KEY=<YOUR_DEADCHANNEL_PRIVATE_KEY>' deadchannel -- npx -y deadchannel-mcp dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter deadchannel MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Que vérifie deadchannel ?
Il vérifie si un endpoint est joignable, recherche la présence de bot gates, s'assure qu'il utilise le protocole x402, valide la stabilité et la cohérence des prix, et confirme les détails du réseau et du schéma.
Quel est le coût d'utilisation ?
Le service coûte 0,005 $ en USDC par sonde (probe).
Faut-il une clé API ou une inscription ?
Non, aucune inscription, aucune clé API et aucun abonnement n'est requis ; les agents paient par appel via un wallet.