PCI DSS v4.0.1 Compliance Checker — Claude Code MCP server
PCI DSS v4.0.1 Compliance Checker is an MCP server for Claude Code that scans Go payment service codebases against PCI DSS v4.0.1. Every finding maps to a numbered requirement.
MIT ★ 5 updated 2026-10-19
claude mcp add pci-dss-v401-compliance-checker -- docker run -i --rm ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1What PCI DSS v4.0.1 Compliance Checker does
The server runs 12 scanners over Go code and returns violations tagged with PCI DSS v4.0.1 requirement IDs. It catches HTTP input leaking into logs (supports gin, chi, echo, fiber, slog, zap, logrus), PAN and SAD storage, weak encryption, insecure TLS, hardcoded passwords, missing audit logs, vulnerable dependencies via OSV, and absent CSP on payment pages.
Requires Go 1.25+ on the host for go install; the Docker image runs without local Go. This server does not replace a QSA audit: static analysis covers roughly 6% of the standard; a certified auditor must sign off on the rest. Use Semgrep or CodeQL for broad SAST; this tool targets payment services.
The triage_findings tool runs all scanners and groups results by requirement; generate_compliance_report returns JSON with pass/fail status per requirement. Other tools check individual aspects: scan_pan_data, check_encryption, check_tls_config, audit_log_coverage, and more.
What it helps with
- Check Go payment service code against PCI DSS v4.0.1
- Find PAN and SAD leaks in logs and errors
- Detect weak encryption and hardcoded keys
- Verify audit log coverage on payment operations
- Generate CycloneDX SBOM from
go.mod
Example prompts for the agent
- Run
triage_findingson/home/user/payments-servicewithmin_severity=MEDIUMand group by PCI DSS requirement - Generate a JSON compliance report for
/home/user/payments-servicewith severity counts per requirement - Check
/home/user/payments-servicefor PAN storage in database and logs
How to install PCI DSS v4.0.1 Compliance Checker
Platform CLI
claude mcp add pci-dss-v401-compliance-checker -- docker run -i --rm ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1Platform CLI
codex mcp add pci-dss-v401-compliance-checker -- docker run -i --rm ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1Config file
{
"mcpServers": {
"pci-dss-v401-compliance-checker": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1"
]
}
}
}Config file
{
"servers": {
"pci-dss-v401-compliance-checker": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1"
]
}
}
}Platform CLI
gemini mcp add pci-dss-v401-compliance-checker docker run -i --rm ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about PCI DSS v4.0.1 Compliance Checker
How do I install PCI DSS v4.0.1 Compliance Checker in Claude Code?
Run claude mcp add pci-dss-v401-compliance-checker -- docker run -i --rm ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1. For Cursor, add the configuration to .cursor/mcp.json with command docker and args ["run", "-i", "--rm", "ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1"].
What does PCI DSS v4.0.1 Compliance Checker do?
It runs static analysis on Go payment service code and reports violations of PCI DSS v4.0.1 requirements. It detects card data leaks, weak encryption, insecure TLS settings, hardcoded passwords, missing audit logs, and vulnerable dependencies. Each finding includes the requirement ID from the standard.
Does this server replace a QSA audit?
No. Static analysis covers roughly 6% of PCI DSS v4.0.1 requirements. A certified auditor must validate the rest.