The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the K402 MCP listing page.
An MCP server that gives any agent (Claude Code, Claude Desktop, agent SDKs) a catalog of agent-payable APIs: text tools (summarize, schema-guaranteed extraction, classify, rewrite), web reading, embeddings + semantic search, live Kaspa mainnet chain data, GPU model tiers, covenants-as-a-service (compile/derive/inspect/build/check/broadcast Silverscript covenants), and RISC Zero attestation-as-a-service (upload a guest, preflight for a cycle-exact quote, prove, verify). No account, no card, no API key — the agent opens a session, gets a personal KAS deposit address, and every call meters against the prepaid balance. Prices are USD-pegged, fractions of a cent per call, settled on Kaspa L1 (sub-second, ~zero fees).
The payment loop is agent-native: an unfunded call returns instructions ("send KAS to this address, this call costs X"), so an agent can discover the service, learn how to pay, and use it autonomously — the x402 idea, on Kaspa.
The same server runs hosted at the public gateway (streamable HTTP):
Claude Code:
Hosted sessions are per-connection: open_session binds the payment session to your MCP
connection and returns the key — save it, and re-attach with use_session(<key>) after a
reconnect. Nothing is shared between connections.
Claude Code:
Claude Desktop / generic MCP config:
Env (all optional): K402_GATEWAY (defaults to the public gateway), K402_SESSION (pin a funded
session key), K402_STATE (where the auto-opened session persists, default ~/.k402/session.json).
catalog — see every service and its live KAS/USD price (free)open_session — get a session + personal Kaspa mainnet deposit address (free); fund it from
any wallet (min 0.25 KAS — confirmed in seconds)summarize, extract, classify, rewrite, read_url, embed_text,
search_index/search_query, kaspa_balance, kaspa_utxos, kaspa_tx_status,
kaspa_fee_estimate, kaspa_network, generate (tiers: chat / llama / reason / think / code / kaspa-expert),
covenant_compile/covenant_address/covenant_utxos/covenant_build/covenant_check/covenant_broadcast,
prove_guest_upload/prove_preflight/prove_submit/job_status/job_result/attest_verify,
payment_options, pay_per_callsession_status — watch the balance draw down (free)New here? Start with open_session — one funded deposit address, and every call meters
against it. That's the whole loop. The other schemes (per-call coins, or trustless payment
channels) are for when you want them; payment_options explains each.
kaspa-channel)Where the gateway offers it, channel_config/channel_status expose a covenant payment channel:
your KAS sits in a Kaspa L1 covenant (not the merchant's wallet), and you pay per call with signed
vouchers — the merchant can only ever claim what you signed, and you reclaim the rest. Opening and
funding a channel needs your Kaspa key, so that part runs in the k402
Python client (k402.channel); these MCP tools cover discovery and status.
Example, in Claude Code after claude mcp add:
"Use the k402 tools to check the current Kaspa network status and summarize https://kaspa.org"
The first call returns how-to-pay instructions; fund the deposit address it gives you and retry.
kaspa-channel covenant payment channels (live on mainnet, covenant unaudited — channel sizes
are capped). Keep balances small: a few KAS covers thousands of calls.payment_required + instructions instead of failing opaquely.catalog shows current numbers.mcp-name: io.github.Kali123411/k402
MIT © Kaspa Lab