Platform · Claude Code

Your compliance copilot, in your editor.

Vallorix speaks MCP. Connect it to Claude Code — or any MCP client — and run your compliance program from the terminal: see open gaps, check framework readiness, get grounded remediation, and fix failing controls as code. Every call runs against your own Vallorix instance, so evidence never leaves your boundary.

claude code — /vallorix:compliance-status
4 open gaps · grouped by framework
Encryption at rest SOC 2 · ISO 27001
Access review overdue · Finance HIGH
MFA enforced · all users MET
Change management 1 FIX
Works with Claude CodeCursorAny MCP clientOAuth2 & API keysSelf-hosted
What it does

Five commands for your whole program

Ask in plain language, or run the commands. Each one reads (and, with your confirmation, writes) your real compliance data through the Vallorix MCP server.

/vallorix:compliance-status

Every open gap — unimplemented measures and open findings — ranked by what's fixable from this repo, grouped by framework.

/vallorix:framework-readiness

“How ready are we for SOC 2 / ISO 27001 / HIPAA / CMMC?” — a real readiness %, the blocking findings, and the shortest path to green.

/vallorix:remediate

A fix grounded in the real control requirement and the evidence it needs — minimal, security-safe, never a generic guess.

/vallorix:fix

Scans your repo, generates the minimal change, and opens a PR attributed to the control it satisfies — then updates the measure in Vallorix.

/vallorix:evidence-check

Flags evidence that's expiring, still manual, or missing — so nothing lapses the week before your audit.

Runs in your boundary

The copilot talks only to your Vallorix instance — self-hosted or hosted. Your controls and evidence never go to a vendor's cloud.

Setup

Install in about a minute

The plugin is open source. Point it at your instance with a scoped Personal API Key — its permissions follow your Vallorix role.

terminal
# 1 · add the plugin from GitHub
/plugin marketplace add Bhenderlong/vallorix-mcp-plugin
/plugin install vallorix@vallorix-plugin
# 2 · point it at your instance + a scoped key
export VALLORIX_API_KEY=<your personal api key>
# self-hosted? also set VALLORIX_MCP_URL to your instance
# 3 · run it
/vallorix:compliance-status
View on GitHub →
Sovereign by design

The copilot that never sees a vendor cloud

Every other GRC copilot runs against the vendor's hosted platform. Vallorix is self-hostable, so the MCP endpoint points at your own instance — remediation is computed from your controls and evidence, and none of it leaves your infrastructure.

  • Your controls, your evidence, your boundary
  • Scoped OAuth2 & API keys, audit-logged
  • Built for CMMC, DORA, and air-gapped teams
Why self-hosted →
claude code — /vallorix:remediate m_7af…
Control CC6.1 — encryption at rest grounded
→ Minimal Terraform change proposed. Opens a PR: “Satisfies: Vallorix measure m_7af… — CC6.1 (SOC 2)”.
Evidence to attach kms_key_policy
FAQ

Vallorix for Claude Code

What is MCP?+
The Model Context Protocol — an open standard that lets AI tools like Claude Code securely call external systems. Vallorix ships an MCP server, so a coding agent can read and act on your compliance program.
Does my data leave my infrastructure?+
No. The plugin connects to your own Vallorix instance (hosted or self-hosted). Remediation is computed from your controls and evidence inside your boundary — nothing is sent to a third-party cloud.
How is it authenticated?+
A scoped Personal API Key (or OAuth2). Permissions follow the key's grants and your Vallorix role — the copilot can only see and change what you can, and every action is audit-logged.
Which clients work?+
Claude Code via the published plugin, and any MCP-compatible client pointed at your Vallorix MCP endpoint.

Drive compliance from your editor.

Open source, MCP-native, and sovereign — your compliance copilot, running against infrastructure you control.

V
Vallorix AssistantAI · answers about compliance & the product
AI assistant · not a human · answers may be imperfect