Ext Ops Panel
Open dashboard
Comparison

io.github.Kali123411/kx402 vs AiFinPay

io.github.Kali123411/kx402 is an MCP server published by Kali123411. Marketplaces we read that list it: 1 (Official MCP Registry). AiFinPay is an MCP server published by daochild. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.Kali123411/kx402AiFinPay
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (npm): 100
Downloads/week (npm): 41
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.2.2
Downloads/month (npm): 3 040
Downloads/week (npm): 886
Forks (GitHub): 2
Stars (GitHub): 3
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 2.16.2
Downloads/month (npm): 3 040
Downloads/week (npm): 886
Forks (GitHub): 2
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.Kali123411/kx402 vs AiFinPay
Factio.github.Kali123411/kx402AiFinPay
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last release (differs)Not published2026-11-05
Where it runs (differs)On your machine (kx402)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for3, secrets among them: 13, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/kali123411/kx402github.com/aifinpay/sdk
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 18 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.Kali123411/kx402

In its own words, on Official MCP Registry:

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

AiFinPay

In its own words, on Official MCP Registry:

Pay for any HTTP API in stablecoins on Polygon and Solana with one MCP call.

How to run each

io.github.Kali123411/kx402 As a local MCP server: npm package

Claude Code
claude mcp add --env "KASPA_X402_FUNDING_WALLET=<YOUR_KASPA_X402_FUNDING_WALLET>" --env "KASPA_X402_KASPA_WASM_MODULE=<YOUR_KASPA_X402_KASPA_WASM_MODULE>" --transport stdio kx402 -- npx -y kx402 mcp

Requires: KASPA_X402_FUNDING_WALLET (secret), KASPA_X402_KASPA_WASM_MODULE

AiFinPay As a remote MCP server

Claude Code
claude mcp add --transport http aifinpay https://mcp.aifinpay.io/mcp

Requires: AIFINPAY_AGENT_SECRET (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only AiFinPay has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.Kali123411/kx402 asks for

  • KASPA_X402_FUNDING_WALLET (secret)
  • KASPA_X402_KASPA_WASM_MODULE
  • KASPA_X402_NETWORK

Only AiFinPay asks for

  • AIFINPAY_AGENT_SECRET (secret)
  • AIFINPAY_BASE_URL
  • AIFINPAY_MAX_USD

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.Kali123411/kx402 · What it can do: AiFinPay · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built