VERAX
Open-source MCP gate that signs an allow, deny or hold before each agent tool call
- Pricing
- Open source
- Platforms
- CLI, self-hosted, API
- Runs
- Remotely
- Version
- 0.8.2
- Listing updated
- 3 days ago
About VERAX
VERAX is an open-source MCP server for security. It runs as a hosted remote server, so there is nothing to install locally.
Think of it as a flight recorder for agents. Verax sits between an agent and its tools, and every call passes a policy gate that writes a signed decision before anything runs. Refusals are signed just like approvals, calls with no token are turned away and counted without a record, and the body will not start until authorization is configured, since there is no default token.
Calls the policy will not decide alone are held until an operator approves them at the machine or from another device with a passkey. Calls that ran leave an effect row that is later reconciled against the record. The ledger, keys and approvals stay in a local state directory, and a single-file verifier can read the ledger back without the service.
Setup needs Node 22.6 or newer and an issuer, JWKS URL, audience, state directory and policy file; the bundled default policy denies what it does not name. The demo is run with npx -y @verax-ai/body demo. The project is the gate in a family with Conarium for data masking, Tugra for memory and Cedulon for spend approvals, and the README offers a bounty of USD 100 per valid bypass report up to USD 500.
Install
Run in a terminal
claude mcp add verax --env VERAX_ISSUER='<VERAX_ISSUER>' --env VERAX_JWKS_URL='<VERAX_JWKS_URL>' --env VERAX_AUDIENCE='<VERAX_AUDIENCE>' --env VERAX_STATE_DIR='<VERAX_STATE_DIR>' --env VERAX_POLICY_FILE='<VERAX_POLICY_FILE>' -- npx -y @verax-ai/bodyAdd to claude_desktop_config.json
{
"mcpServers": {
"verax": {
"command": "npx",
"args": [
"-y",
"@verax-ai/body"
],
"env": {
"VERAX_ISSUER": "<VERAX_ISSUER>",
"VERAX_JWKS_URL": "<VERAX_JWKS_URL>",
"VERAX_AUDIENCE": "<VERAX_AUDIENCE>",
"VERAX_STATE_DIR": "<VERAX_STATE_DIR>",
"VERAX_POLICY_FILE": "<VERAX_POLICY_FILE>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"verax": {
"command": "npx",
"args": [
"-y",
"@verax-ai/body"
],
"env": {
"VERAX_ISSUER": "<VERAX_ISSUER>",
"VERAX_JWKS_URL": "<VERAX_JWKS_URL>",
"VERAX_AUDIENCE": "<VERAX_AUDIENCE>",
"VERAX_STATE_DIR": "<VERAX_STATE_DIR>",
"VERAX_POLICY_FILE": "<VERAX_POLICY_FILE>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"verax": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@verax-ai/body"
],
"env": {
"VERAX_ISSUER": "<VERAX_ISSUER>",
"VERAX_JWKS_URL": "<VERAX_JWKS_URL>",
"VERAX_AUDIENCE": "<VERAX_AUDIENCE>",
"VERAX_STATE_DIR": "<VERAX_STATE_DIR>",
"VERAX_POLICY_FILE": "<VERAX_POLICY_FILE>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"verax": {
"command": "npx",
"args": [
"-y",
"@verax-ai/body"
],
"env": {
"VERAX_ISSUER": "<VERAX_ISSUER>",
"VERAX_JWKS_URL": "<VERAX_JWKS_URL>",
"VERAX_AUDIENCE": "<VERAX_AUDIENCE>",
"VERAX_STATE_DIR": "<VERAX_STATE_DIR>",
"VERAX_POLICY_FILE": "<VERAX_POLICY_FILE>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"verax": {
"command": "npx",
"args": [
"-y",
"@verax-ai/body"
],
"env": {
"VERAX_ISSUER": "<VERAX_ISSUER>",
"VERAX_JWKS_URL": "<VERAX_JWKS_URL>",
"VERAX_AUDIENCE": "<VERAX_AUDIENCE>",
"VERAX_STATE_DIR": "<VERAX_STATE_DIR>",
"VERAX_POLICY_FILE": "<VERAX_POLICY_FILE>"
}
}
}
}Configuration
VERAX_ISSUERIssuer the agent's token must carry. The body refuses to start without one; `verax doctor` names what is missing.RequiredVERAX_JWKS_URLWhere the body fetches the keys that verify that token.RequiredVERAX_AUDIENCEAudience the token must name, so a token minted for something else is refused.RequiredVERAX_STATE_DIRDirectory the ledger, keys and approvals live in. It stays on this machine.RequiredVERAX_POLICY_FILEPolicy the gate applies. @verax-ai/proxy ships policy/default.json, which denies what it does not name.RequiredVERAX_BINDhost:port the body listens on. Anything but loopback needs VERAX_TLS_TERMINATED=1.VERAX_INVENTORY_FILERoster document the body serves; the format is @verax-ai/inventory.
What it does
- Signed decision records
- Every tool call gets a signed allow, deny or defer before it runs.
- Scoped permissions
- Read, memory, act, pay, approve and audit scopes are granted one by one.
- Human approval holds
- Sensitive calls such as spending wait for an operator, via CLI or passkey.
- Effect reconciliation
- Calls that ran are checked against their decision records afterwards.
- Local ledger
- Ledger, keys and approvals stay on the machine; verification does not need the service.
- Demo command
- npx -y @verax-ai/body demo runs a temporary body and prints the signed records.
Good for
- Put a policy gate in front of an agent's tools
- Require human approval before an agent spends money
- Keep a tamper-evident audit trail of agent actions
- Refuse unauthorised calls and still record the refusal
Pricing
Open source
Prices change. Check verax-ai.com before you buy.
VERAX FAQ
What does it need to run?
Node 22.6 or newer and settings for token issuer, JWKS URL, audience, state directory and policy file.
Where is data stored?
The ledger stays on the machine the body runs on, in the configured state directory.
What happens to a call with no token?
It is counted and turned away, and nothing is written to the ledger.
Is it open source?
The website describes the Verax body as an open-source MCP gate.
Is VERAX free?
Yes. VERAX is open source, so you can use and self-host it for free.
How do I add VERAX to Claude Code?
Run this command in your terminal: claude mcp add verax --env VERAX_ISSUER='<VERAX_ISSUER>' --env VERAX_JWKS_URL='<VERAX_JWKS_URL>' --env VERAX_AUDIENCE='<VERAX_AUDIENCE>' --env VERAX_STATE_DIR='<VERAX_STATE_DIR>' --env VERAX_POLICY_FILE='<VERAX_POLICY_FILE>' -- npx -y @verax-ai/body
What are the best alternatives to VERAX?
The closest alternatives to VERAX are REA, Codebase Memory, GitHub, Serena MCP: the IDE for your agent and XERJ.
Alternatives to VERAX

REA
MCP serverCLI and MCP server that lets coding agents reverse engineer apps and binaries
Runs locally- Open source
- 464K GitHub stars
- Developer tools

Codebase Memory
MCP serverLocal MCP server that builds a code knowledge graph for AI coding agents
Runs locally- Open source
- 48.7K GitHub stars
- Knowledge and memory

GitHub
MCP serverOfficial MCP server connecting AI assistants to GitHub repos, issues and workflows
Not checked yet- Remote
- Open source
- 34.5K GitHub stars
- Developer tools

Serena MCP: the IDE for your agent
MCP serverMCP toolkit giving coding agents symbol-level code retrieval and editing
Runs locally- Open source
- 31.5K GitHub stars
- Developer tools

XERJ
MCP serverLocal search engine for AI agents with cited answers over your code and docs
Runs locally- Open source
- 19.2K GitHub stars
- Knowledge and memory

Ouroboros
MCP serverSpec-first layer that pins requirements and verifies results of AI coding agent work
Runs locally- Open source
- 6.4K GitHub stars
- Developer tools