Packages

Wasit ships as three npm packages under the @wasit-dev scope. Install only the ones you need — most people need the first.

Package	What it is
`@wasit-dev/cli`	The `wasit` terminal command, and the interactive dashboard
`@wasit-dev/server`	The MCP server, for Claude Code, Claude Desktop, and other stdio clients
`@wasit-dev/core`	The check suites as a library, for building on top of Wasit directly

The CLI and the MCP server are both thin adapters over core, so there is exactly one implementation of every check: a terminal run and an agent's run can never disagree about the same target.

Run it without installing

bash

npx @wasit-dev/cli test --target https://your-service.example/paid --read-only

Right for a one-off check or a CI job that should pin nothing.

Install it globally

bash

npm install -g @wasit-dev/cli
wasit --version

Right if you will run it more than once. Gives you the bare wasit command, which with no arguments opens the interactive dashboard.

As a dependency

bash

npm install @wasit-dev/core

For calling the check suites from your own code — a custom reporter, a test harness, a service of your own. The Core Guide documents every exported function and result shape.

The MCP server

Not installed by hand. The client launches it, usually through npx, so it stays up to date without a global install:

bash

npx -y @wasit-dev/server

The MCP Guide has the exact registration command for Claude Code and the config file for Claude Desktop.