Compliance verdicts, inside Claude
Give Claude access to your audit trail, compliance status, and PHI reports. Code and check compliance in the same session. No context-switching.
Two products, one workflow
Claude Code captures what happens. Verdict evaluates it. Ask Claude about compliance — right in your coding session.
Capture
Claude Code writes code. The Verdict hook captures every session — prompts, file changes, commands, git context — into structured Change Records.
Evaluate
Verdict runs PHI detection, policy evaluation, and compliance mapping locally. Every session gets a pass/fail verdict against SOC 2, HIPAA, and HITRUST controls.
Query (same session)
Ask Claude Code about compliance mid-session. It calls Verdict tools to get real-time answers from your local data. No context-switching.
See it in action
Mid-session compliance check in Claude Code. Describe what you need, Claude takes action.
I'm about to merge PR #42 for the patient intake form. Is it compliant?
Let me check the compliance status for PR #42.
verdict.get_compliance_verdictPR #42 passes all compliance checks. Two sessions were captured totaling 45 minutes. The change is authorized via ticket EHR-1847, no PHI was detected, and all framework controls are satisfied. Safe to merge.
Were there any PHI issues across the team this week?
verdict.check_phi_exposureClean week. 47 sessions across the team with zero PHI detections. No action needed.
Describe the outcome. Claude takes action.
Six tools that Claude can call on your behalf. You approve each one. Results come from your local Verdict database in real time.
get_compliance_verdictCompliance Verdict
Full pass/fail status for a PR or branch — policy results, control mappings, and evidence summary.
“Is PR #42 ready to merge?”
check_phi_exposurePHI Exposure Check
Scan sessions for PHI in prompts, file reads, or modifications. Risk levels and redaction status.
“Any PHI risks this sprint?”
get_audit_trailAudit Trail
Complete audit log for a session, developer, or time range. Formatted for auditor review.
“Show the audit trail for last week”
get_change_recordChange Record
Full provenance for a session — developer, agent, model, files modified, commands run, git context.
“What happened in session abc123?”
query_sessionsSession Query
Search and filter sessions by any dimension — date, developer, repo, status, or PHI detections.
“How many sessions this month?”
export_compliance_reportCompliance Report
Audit-ready report mapped to SOC 2, HIPAA, or HITRUST controls. JSON or summary format.
“Generate a SOC 2 report for Q1”
Set up in 2 minutes
Install Verdict, add one config block, restart Claude. Done.
Install Verdict
$ brew install verdictAdd to Claude Code
{
"mcpServers": {
"verdict": {
"command": "verdict",
"args": ["mcp", "serve"]
}
}
}Start asking
Start a Claude Code session. Verdict tools are available immediately. Ask about compliance anytime mid-session.
Built for every role
Different people, same interface. Ask Claude what you need in plain English.
Check compliance before merging
"Is my PR compliant? Can I merge?" — get a pass/fail in seconds without opening a dashboard.
Monitor team compliance posture
"Show me all sessions with policy warnings this sprint" — spot patterns and address issues early.
Query audit evidence on demand
"Generate a HIPAA compliance report for March" — structured evidence, no developer interruptions.
Review evidence mapped to controls
"Show me SOC 2 CC8.1 evidence for Q1" — get exactly the documentation needed, instantly.
Model Context Protocol
MCP is Anthropic's open standard for connecting AI to external tools. Think of it as a USB-C port for AI — one universal interface that works across Claude Code, Claude Desktop, and any MCP-compatible client.
Verdict publishes an MCP server. Claude knows how to call it. You get compliance answers without leaving your conversation.
Get Verdict for Claude
Join healthcare IT teams using Verdict in Claude Code to stay compliant while shipping faster with AI agents.