VERAX MCP Server

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

Packages and local setup

The published npm package is @verax-ai/body, version 0.5.1. Its declared MCP transport is streamable-http.

The package declares VERAX_ISSUER (required): Issuer the agent's token must carry. The body refuses to start without one; verax doctor names what is missing.; VERAX_JWKS_URL (required): Where the body fetches the keys that verify that token.; VERAX_AUDIENCE (required): Audience the token must name, so a token minted for something else is refused.; VERAX_STATE_DIR (required): Directory the ledger, keys and approvals live in. It stays on this machine.; VERAX_POLICY_FILE (required): 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.5.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.