mcpbeat Sign in

VERAX MCP Server

local only

VERAX runs on your own machine — the client starts it, so there is no endpoint to ping. 208 installs a week from npm. Last commit 18 Sep 2026.

The body an agent asks before it acts: decide, approve, and keep a signed record on your machine.

Installs per day peak 208 · avg 6
a month agotoday
208
Installs / week
npm · @verax-ai/body
0
Stars
0 open issues
18 Sep 2026
Last commit
0 releases in 90 days
Apache-2.0
License
TypeScript

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command packages/proxy/perf/check.mjs:16
  const out = spawnSync(process.execPath, [checker], {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add verax -- npx -y @verax-ai/body
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verax": {
      "args": [
        "-y",
        "@verax-ai/body"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verax]
command = "npx"
args = ["-y", "@verax-ai/body"]
.cursor/mcp.json
{
  "mcpServers": {
    "verax": {
      "args": [
        "-y",
        "@verax-ai/body"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verax": {
      "args": [
        "-y",
        "@verax-ai/body"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: VERAX_ISSUER (Issuer the agent's token must carry. The body refuses to start without one; `verax doctor` names what is missing.), VERAX_JWKS_URL (Where the body fetches the keys that verify that token.), VERAX_AUDIENCE (Audience the token must name, so a token minted for something else is refused.), VERAX_STATE_DIR (Directory the ledger, keys and approvals live in. It stays on this machine.), VERAX_POLICY_FILE (Policy the gate applies. @verax-ai/proxy ships policy/default.json, which denies what it does not name.), VERAX_BIND (host:port the body listens on. Anything but loopback needs VERAX_TLS_TERMINATED=1.), VERAX_INVENTORY_FILE (Roster document the body serves; the format is @verax-ai/inventory.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to VERAX

same job, measured the same way
RECOVER — Decide Safely After a Failed Machine Action
by gsterlingpress

Choose the safest next action after an API, MCP, or agent failure before retrying.

1 tools answering
Lauther
by csanadymiklos

Puts Approve/Deny on your phone before an agent acts, and waits for your fingerprint.

39 installs/wk local only
Ratchet
by ratchetgate

Your agent asks before it acts, so the same real-world action is attempted at most once.

261 installs/wk 15 tools answering
Proof
by toremlabs

Govern your AI coding agent: frame the work, review the changes, keep a signed decision record.

45 installs/wk local only
Scrapecheck
by fieldmodellc

Verify before your agent acts on data it paid for. Signed verdicts, checkable offline, via x402.

3 tools answering
Kaval
by usekaval

Verify the facts an agent's action depends on before it acts — ALLOW, REVIEW, or BLOCK.

360 installs/wk local only
Kaval
by lufemc

Verify the facts an agent's action depends on before it acts — ALLOW, REVIEW, or BLOCK.

local only
three.ws Provenance
by nirholas

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

194 installs/wk local only

VERAX — questions

Answers built from our own checks of this server.

Why is there no uptime for VERAX?
VERAX runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @verax-ai/body was installed 208 times last week.
How do I connect VERAX?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @verax-ai/body straight from npm; nothing to host, nothing to sign up for.
How many people use VERAX?
The npm package @verax-ai/body was installed 208 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is VERAX open source?
Yes — it is published under the Apache-2.0 licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.