The body an agent asks before it acts: decide, approve, and keep a signed record on your machine.
To add VERAX to Claude, run the install command below or copy the ready-made config for Claude Code, Claude Desktop, Cursor and VS Code further down. Restart your client after adding it and its tools show up in your next conversation. It declares 7 environment variables, listed below.
Install
npx -y @verax-ai/body@0.8.0Environment variables
VERAX_ISSUERSet in your MCP configVERAX_JWKS_URLSet in your MCP configVERAX_AUDIENCESet in your MCP configVERAX_STATE_DIRSet in your MCP configVERAX_POLICY_FILESet in your MCP configVERAX_BINDSet in your MCP configVERAX_INVENTORY_FILESet in your MCP configSet only if the maker requires them; this listing does not flag any of them as required.
Install with your client
claude mcp add verax --env VERAX_ISSUER=<YOUR_VERAX_ISSUER> --env VERAX_JWKS_URL=<YOUR_VERAX_JWKS_URL> --env VERAX_AUDIENCE=<YOUR_VERAX_AUDIENCE> --env VERAX_STATE_DIR=<YOUR_VERAX_STATE_DIR> --env VERAX_POLICY_FILE=<YOUR_VERAX_POLICY_FILE> --env VERAX_BIND=<YOUR_VERAX_BIND> --env VERAX_INVENTORY_FILE=<YOUR_VERAX_INVENTORY_FILE> -- npx -y @verax-ai/body@0.8.0
Run this in a terminal to add the server to Claude Code.
What this does
VERAX exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.
Requirements
This server declares the following environment variables. Set only the ones the maker requires for your setup; this listing does not flag any of them as required:
VERAX_ISSUER VERAX_JWKS_URL VERAX_AUDIENCE VERAX_STATE_DIR VERAX_POLICY_FILE VERAX_BIND VERAX_INVENTORY_FILE
Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).
Frequently asked questions
How do I install VERAX?
Run the Claude Code command in the install section to add VERAX to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.
Which clients work with VERAX?
This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to VERAX as well.
Does VERAX need an API key?
This listing does not flag an API key as required. The server can use these environment variables: VERAX_ISSUER, VERAX_JWKS_URL, VERAX_AUDIENCE, VERAX_STATE_DIR, VERAX_POLICY_FILE, VERAX_BIND, VERAX_INVENTORY_FILE; the maker's docs say which of them your setup needs. They go in the env block of your MCP config.
Imported from the Official MCP Registry. The details above come from the registry entry; the maker can claim this listing to correct them, add docs, and see its traffic.
Is this your MCP server?
Claim this listing to see its traffic, fix details yourself, and skip the review queue on future updates.
Add this badge to your README
Show visitors this server is listed in the ClaudeRules directory. The badge links straight to this listing.
[](https://clauderules.net/mcp/io-github-verax-ai-verax)<a href="https://clauderules.net/mcp/io-github-verax-ai-verax" target="_blank" rel="noopener noreferrer"><img src="https://clauderules.net/api/badge/io-github-verax-ai-verax" alt="Listed on clauderules.net" /></a>More AI MCP servers
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Serena MCP: the IDE for your agent
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
MCP Toolbox for Databases
MCP Toolbox for Databases enables your agent to connect to your database.
Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.