Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Kx402

by Kali123411version 0.1.1i★ –iRuns on your computer
Registry nameio.github.Kali123411/kx402

Install

Overview

Description from the maker (original English)

Kaspa x402 agent payer — pay x402 v2 services on Kaspa (KAS) per call, no account or API key

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: KASPA_X402_KASPA_WASM_MODULE, KASPA_X402_FUNDING_WALLET

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: KASPA_X402_KASPA_WASM_MODULE, KASPA_X402_FUNDING_WALLET, KASPA_X402_NETWORK

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

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 mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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.

Open in VS Code

Or copy the settings yourself

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.

Values you fill in

  • KASPA_X402_KASPA_WASM_MODULE required env
    Path to the rusty-kaspa v2.0.0 nodejs WASM SDK (kaspa.js). Get it with the repo's `npm run fetch-sdk`.
  • KASPA_X402_FUNDING_WALLET secret required env
    Funding key: wallet-key: to a 0600 file holding a 64-hex private key, or a raw 64-hex key.
  • KASPA_X402_NETWORK env
    kaspa:mainnet or kaspa:testnet-10 (default testnet-10).

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Kali123411, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 19014 servers in this category
  • Published to the registry more recently than 16% of the other 19014 servers in this category
  • Basic checks equal to or better than 100% of the other 19014 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Kx402 safe?

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.

What keys or codes does it need?

You need to fill in: KASPA_X402_KASPA_WASM_MODULE, KASPA_X402_FUNDING_WALLET

Does it run on my computer or in the cloud?

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

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, ONE — pagos en Monero y trueque de cómputo

Alternatives

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

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated today

Runs in the cloud✓ desktopcommander.app

README from the maker

Open the README

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.

kx402 — Kaspa x402 agent payer

An agent-centric payer for x402 services settled on Kaspa L1. One package, three surfaces over the same proven payment core:

  • SDK — import { openWallet, payExact } from "kx402" to pay x402 offers from your own code.
  • CLI — kx402 offer|pay|balance|addr for humans and scripts.
  • MCP server — drop 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 pay spends real funds. Use testnet-10 first. Keep funding keys in 0600 files, never in git.

What it solves

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:

  • No account, no API key, no signup. The agent pays the exact price for each call on the spot; it needs no relationship with the service.
  • Micropayments cards can't do. Credit cards have a ~30¢ floor. Settling in KAS on Kaspa makes fractions-of-a-cent, per-call payments practical.
  • A wallet built for software, not fingers. It builds, signs, sends, and proves a payment programmatically in about a second, with no human in the loop.
  • Guardrails so it can't run wild. Every payment is capped at the offer's own price, paid only to that service, up to a limit you set — autonomy without the risk of overspending or paying the wrong party.

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.

Install

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.

Configure

Copy .env.example to .env and fill it in (or pass any of these as flags / env vars):

VariableMeaning
KASPA_X402_KASPA_WASM_MODULEPath to the v2.0.0 nodejs WASM SDK kaspa.js
KASPA_X402_FUNDING_WALLETwallet-key:/path/to/wallet.key or a raw 64-hex key
KASPA_X402_NETWORKkaspa:mainnet or kaspa:testnet-10 (default)
KASPA_X402_RPC_URLOptional; a public PNN node is resolved automatically if unset

CLI

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.

SDK

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.

MCP server

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" } } } }

How it settles

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.

Related

  • @kaspa-x402 — the Kaspa x402 binding this builds on.
  • kaspa-402.org — the marketplace of x402-payable services on Kaspa.

License

MIT

Ask PopNx