Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Kaspa x402 agent payer — pay x402 v2 services on Kaspa (KAS) per call, no account or API key
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
KASPA_X402_KASPA_WASM_MODULE, KASPA_X402_FUNDING_WALLET, KASPA_X402_NETWORKValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"kx402": {
"command": "npx",
"args": [
"-y",
"kx402",
"mcp"
],
"env": {
"KASPA_X402_KASPA_WASM_MODULE": "your-value",
"KASPA_X402_FUNDING_WALLET": "your-value",
"KASPA_X402_NETWORK": "your-value"
}
}
}
}Run this in your terminal
claude mcp add kx402 --env KASPA_X402_KASPA_WASM_MODULE=your-value --env KASPA_X402_FUNDING_WALLET=your-value --env KASPA_X402_NETWORK=your-value -- npx -y kx402 mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"kx402": {
"command": "npx",
"args": [
"-y",
"kx402",
"mcp"
],
"env": {
"KASPA_X402_KASPA_WASM_MODULE": "your-value",
"KASPA_X402_FUNDING_WALLET": "your-value",
"KASPA_X402_NETWORK": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"kx402": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"kx402",
"mcp"
],
"env": {
"KASPA_X402_KASPA_WASM_MODULE": "your-value",
"KASPA_X402_FUNDING_WALLET": "your-value",
"KASPA_X402_NETWORK": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
KASPA_X402_NETWORK envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
The registry name was verified with the GitHub account Kali123411, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: KASPA_X402_KASPA_WASM_MODULE, KASPA_X402_FUNDING_WALLET
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, ONE — pagos en Monero y trueque de cómputo
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP del agente ONE: cobros y pagos XMR, libro auditable y trueque de cómputo. AliceLabs LLC.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An agent-centric payer for x402 services settled on Kaspa L1. One package, three surfaces over the same proven payment core:
import { openWallet, payExact } from "kx402" to pay x402 offers from your own code.kx402 offer|pay|balance|addr for humans and scripts.kx402-mcp into an agent (Claude, etc.) so it can pay Kaspa x402 services as a tool.It speaks the x402 v2 exact / `standard-native` flow against the @kaspa-x402 binding — conforming to the standard wire format, not extending it. It's the demand side of the Kaspa·402 marketplace.
⚠️ Alpha, and
payspends real funds. Use testnet-10 first. Keep funding keys in0600files, never in git.
The internet's payment plumbing assumes a *person* is buying: you sign up, get an API key, put a card on file, click "approve." An AI agent can't do any of that — and you don't want to hand it your credit card. So agents can reason and act, but the moment a task needs a paid tool (data, compute, a model, an API), a human has to set up the billing first.
kx402 closes that gap. It gives an agent a wallet it can actually operate, and lets it pay per use on its own:
Think of it as a prepaid card with strict rules baked in: the agent can buy the specific things it needs, in tiny amounts, whenever it needs them, but it physically can't overspend or pay a stranger.
npm install -g kx402 # or: npm install kx402 (for SDK use)
npm run fetch-sdk # downloads the rusty-kaspa v2.0.0 WASM SDK into ./vendor
Kaspa signing needs the official rusty-kaspa v2.0.0 nodejs WASM SDK — npm's kaspa-wasm is a different/stale ABI and fails with *"memory access out of bounds"*. npm run fetch-sdk grabs the right one; then point KASPA_X402_KASPA_WASM_MODULE at the printed kaspa.js path.
Copy .env.example to .env and fill it in (or pass any of these as flags / env vars):
| Variable | Meaning |
|---|---|
KASPA_X402_KASPA_WASM_MODULE | Path to the v2.0.0 nodejs WASM SDK kaspa.js |
KASPA_X402_FUNDING_WALLET | wallet-key:/path/to/wallet.key or a raw 64-hex key |
KASPA_X402_NETWORK | kaspa:mainnet or kaspa:testnet-10 (default) |
KASPA_X402_RPC_URL | Optional; a public PNN node is resolved automatically if unset |
kx402 addr --config-file .env # show the wallet address (fund it first)
kx402 balance --config-file .env # spendable KAS kx402 offer https://host/exact --config-file .env # inspect a 402 offer (no payment) kx402 pay https://host/exact --prompt "hi" --config-file .env # pay and print the result
Input rides in the query on an exact GET — use --text / --prompt / --model / --input as the resource expects. Safety flags: --max caps the spend; --dry builds the signed tx without broadcasting.
import { openWallet, payExact, resolveWalletConfig } from "kx402";
const wallet = await openWallet(resolveWalletConfig()); // reads env / .env const r = await payExact(wallet, "https://host/exact?prompt=hello"); console.log(r.status, r.body, r.settlement); await wallet.close();
Every payment is bounded by a fundingPolicy derived from the offer itself — it will only pay the offer's payTo, at its profile, up to your max.
Run kx402 mcp (or the kx402-mcp bin) — a stdio server exposing kaspa_x402_address, kaspa_x402_balance, kaspa_x402_offer, and kaspa_x402_pay (which spends real funds, bounded by max_sompi). Example client config:
{
"mcpServers": { "kx402": { "command": "npx", "args": ["-y", "kx402", "mcp"], "env": { "KASPA_X402_KASPA_WASM_MODULE": "/abs/path/vendor/kaspa-wasm32-sdk/nodejs/kaspa/kaspa.js", "KASPA_X402_FUNDING_WALLET": "wallet-key:/abs/path/wallet.key", "KASPA_X402_NETWORK": "kaspa:testnet-10" } } } }
On mainnet, kx402 uses non-hosted settlement: it broadcasts the signed tx itself, waits for acceptance on the same REST indexer the gateway verifies against, then presents the PAYMENT-SIGNATURE — so the gateway settles by *observing* the accepted tx and never needs to broadcast. All within the standard x402 v2 lifecycle.
@kaspa-x402 — the Kaspa x402 binding this builds on.MIT