VERAX
The body an agent asks before it acts: decide, approve, and keep a signed record on your machine.
Topics: Security
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (npm 0.9.0)
Package: npm @verax-ai/body
VERAX_ISSUERrequired — Issuer the agent's token must carry. The body refuses to start without one; `verax doctor` names what is missing.VERAX_JWKS_URLrequired — Where the body fetches the keys that verify that token.VERAX_AUDIENCErequired — Audience the token must name, so a token minted for something else is refused.VERAX_STATE_DIRrequired — Directory the ledger, keys and approvals live in. It stays on this machine.VERAX_POLICY_FILErequired — 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.
Related servers
semgrep
Scan code for security vulnerabilities using Semgrep.
ida-pro-mcp
IDA Pro plugin for binary analysis: decompilation, disassembly and automatic malware analysis reports.
lauriewired/ghidramcp
Autonomous reverse engineering with Ghidra: decompile binaries, rename methods and data, and list methods, classes, imports and exports.
jadx-ai-mcp
JADX decompiler plugin providing live, LLM-assisted reverse engineering.
beelzebub
Honeypot framework for building decoy MCP tools that an agent would never use in normal work, to detect prompt injection and malicious…
jshookmcp
Search-first MCP server for JavaScript reverse engineering: 736 tools across 36 domains.
Listed in punkpeye/awesome-mcp-servers (MIT)
Data from the Official MCP Registry