Requirements

Wasit is a Node command-line tool and an MCP server. There is nothing to compile, no native dependency, and no service to run.

Runtime

  • Node.js 22 or newer. All three packages declare "node": ">=22".
  • npm, which ships with Node.
  • macOS, Linux, or Windows. Nothing in Wasit is platform-specific.

Continuous integration builds and tests on Node 22 and Node 24. Node 26 works too — the full build, typecheck and test suite has been run on it.

Note — Wasit is testnet-only. Every check, and every key it reads, targets Stellar testnet. There is no mainnet mode and no flag that enables one.

A Stellar testnet account

Only for the checks that move money. The read-only x402 checks (X402-01–05) need no key, no funds, and no account — that is the whole point of starting there.

This table is about what you have to obtain. For the authoritative list of which environment variable each check reads — including MPP_STELLAR_NETWORK and the extra opt-in MPP-13 needs — see What each check needs.

You want to runYou need to have
X402-01–05Nothing at all
X402-06, 07A testnet account funded with XLM and the asset the target charges in, usually USDC
MPP-01A testnet account funded with XLM and USDC
MPP-10–14A commitment signing key — no funds, no account

wasit wallet create generates any of these and wasit wallet fund funds them from Friendbot — see Quick setup.

AI clients, for the MCP server

The MCP server speaks stdio, so it needs a client that can launch a local server process. A client that only supports remote HTTP connectors cannot run it at all.

ClientWorks with Wasit
Claude CodeVerified — exact claude mcp add command in the MCP Guide
Claude DesktopVerified — config file snippet in the MCP Guide
VS Code (GitHub Copilot)Compatible, not yet verified — supports local stdio servers
CursorCompatible, not yet verified — supports local stdio servers
ChatGPTNot compatible — its connectors are remote HTTP only

Note — "Verified" means the exact steps in the MCP Guide were run against this package. "Compatible, not yet verified" means the client documents support for local stdio MCP servers, which is all Wasit needs, but nobody has run it there yet. If you do, the repo would welcome the report.

The CLI needs none of this. Only the MCP server does.