K402 MCP

What Kali123411/k402-mcp MCP server does

Kali123411/k402-mcp MCP server provides an MCP catalog of APIs that agents can discover and pay for per call. Its text services include summarization, schema-constrained extraction, classification, and rewriting. Other services support reading URLs, creating embeddings, semantic search, querying Kaspa mainnet data, using GPU-backed language model tiers, working with Silverscript covenants, and requesting RISC Zero attestations.

The payment model is based on prepaid usage. An agent opens a session and receives a personal Kaspa deposit address. Once the deposit is confirmed, paid calls deduct from the session balance. Calls made without sufficient funding return payment instructions rather than an opaque failure. Prices are USD-pegged and displayed through the catalog, while settlement occurs on Kaspa L1.

How it works

Start with catalog to inspect available services and current KAS/USD prices. Use open_session to create a session, then fund the returned address with a regular Kaspa mainnet transfer. After confirmation, the agent can call the paid tools and use session_status to monitor its remaining balance.

The tool set includes summarize, extract, classify, rewrite, and read_url; embed_text, search_index, and search_query; and Kaspa queries such as kaspa_balance, kaspa_utxos, kaspa_tx_status, kaspa_fee_estimate, and kaspa_network. Model generation is exposed through tiers including chat, llama, reason, think, code, and kaspa-expert.

Covenant workflows cover compilation, address derivation, UTXO inspection, transaction building, checking, and broadcasting. RISC Zero workflows support guest upload, preflight quoting, proof submission, job status and result retrieval, and attestation verification. payment_options and pay_per_call expose additional payment methods, including supported coins and available channel options.

Setup and configuration

Kali123411/k402-mcp MCP server can run locally after installing the k402-mcp Python package. The executable is named k402-mcp, and the README shows it configured as a stdio MCP server for Claude Desktop or other generic MCP clients.

The hosted endpoint is https://x402-compute.68cxgfyr0.workers.dev/mcp and uses streamable HTTP. Hosted sessions are tied to the MCP connection. Save the key returned by open_session and pass it to use_session after reconnecting; sessions are not shared across connections.

The optional K402_GATEWAY variable changes the gateway, K402_SESSION pins a funded session, and K402_STATE selects where an automatically opened session is persisted. The default state file is ~/.k402/session.json.

Limitations and notes

The project describes itself as a prototype. Session payments are custodial-prepaid, while kaspa-channel provides a trustless covenant payment-channel option where offered. Channel functionality is live on mainnet but unaudited, and channel sizes are capped. The README recommends keeping balances small.

Deposits require at least 0.25 KAS and are confirmed in seconds according to the project documentation. The gateway rate-limits requests by IP, and prices can change with the KAS/USD exchange rate, so clients should query catalog before relying on a price. Payment-channel funding requires a Kaspa key and uses the separate k402 Python client for that part of the workflow.