Skip to main content
Glama
pci-dss-mcp

pci-dss-mcp

by shyshlakov

pci-dss-mcp

Statischer Analyse-MCP-Server für Go-Zahlungsdienst-Codebasen. Jeder erkannte Verstoß gegen PCI DSS v4.0.1 in einer Go-Zahlungsdienst-Codebasis wird vor der Bereitstellung des Codes der spezifischen Anforderungsnummer zugeordnet.

Go Report Card License: MIT OpenSSF Scorecard MCP Registry pci-dss-mcp MCP server


Funktionsweise

pci-dss-mcp ist ein stdio-MCP-Server, der 12 Scanner, einen Orchestrator und eine KI-Triage-Engine über einer Go-Zahlungsdienst-Codebasis ausführt. Jeder Befund enthält eine requirement_id, die einem spezifischen PCI DSS v4.0.1-Listenpunkt zugeordnet ist; siehe docs/requirement-mapping.md für die kanonische Regel-zu-Anforderungs-Tabelle und testdata/vulnerable-payment-service/EXPECTED-FINDINGS.md für Live-Beispielausgaben.

Was pci-dss-mcp heute erkennt

  • HTTP-Framework-Datenfluss in Log- / Fehler- / Panic-Senken. Tier-1-Frameworks (gin, chi, gorilla/mux, net/http (Go 1.22+), echo v4, fiber v2) und Tier-1-Logger (log/slog, logrus, zap, zerolog, logr, klog, hclog) sind ab v0.7 enthalten. Tier 2 (kratos, apex/log, charmbracelet/log) folgt in v0.8. Tier 3 (fasthttp, beego, iris, httprouter, projektintern) ist nach der Veröffentlichung über Phase 25 YAML benutzerkonfigurierbar. Siehe docs/http_input_taint.md.

Was pci-dss-mcp NICHT ist

  • Kein Ersatz für umfassende SAST-Tools. Verwenden Sie Semgrep, CodeQL oder gosec für OWASP Top-10 und sprachunabhängige Schwachstellen.

  • Kein Ersatz für LLM-basierte Code-Reviews. pci-dss-mcp ordnet zahlungsspezifische Probleme PCI DSS-Anforderungs-IDs zu; LLM-Agenten erkennen allgemeine Fehler durch logisches Schlussfolgern. Die beiden Ebenen ergänzen sich.

  • Nicht Go-agnostisch. Go-spezifische AST-Muster und die Verfolgung von Taint-Datenflüssen ermöglichen die hohe Präzision.

  • Kein Ersatz für einen QSA. Statische Analysen decken etwa 6 % der PCI DSS v4.0.1-Anforderungen ab. Ein Qualified Security Assessor (QSA) muss den Rest abnehmen.

Related MCP server: secureaudit-mcp

Installation

Go-Installation (primär)

Erfordert Go 1.25+:

go install github.com/shyshlakov/pci-dss-mcp@latest

Die Binärdatei landet unter $(go env GOPATH)/bin/pci-dss-mcp. Siehe docs/install-from-source.md für die PATH-Auflösung, den macOS codesign-Provenienz-Fix, die cosign-Verifizierung und die MCP-Client-JSON-Konfiguration.

Docker (alternativ)

docker pull ghcr.io/shyshlakov/pci-dss-mcp:v0.6.2

Nützlich für CI-Pipelines, QSA-Auditoren, die Go nicht lokal entwickeln, oder Umgebungen ohne Go-Toolchain auf dem Host.

MCP-Registry

Gelistet als io.github.shyshlakov/pci-dss-mcp unter registry.modelcontextprotocol.io. Wird bei jedem Tag automatisch veröffentlicht.

Verwendung

Fügen Sie dies Ihrer MCP-Client-Konfiguration hinzu (Claude Desktop claude_desktop_config.json, Cursor .cursor/mcp.json oder claude mcp add für Claude Code):

{
  "mcpServers": {
    "pci-dss-mcp": {
      "command": "docker",
      "args": ["run", "-i", "--rm",
        "--mount", "type=bind,src=/Users/you/go/src,dst=/Users/you/go/src,readonly",
        "ghcr.io/shyshlakov/pci-dss-mcp:v0.6.2"]
    }
  }
}

src= und dst= spiegeln denselben absoluten Pfad wider, sodass der Container Ihren Code unter demselben Pfad sieht wie Ihr Host; Prompts übergeben den normalen Host-Pfad ohne Übersetzung. Für die go install-Variante und client-spezifische Beispiele siehe docs/usage.md.

Zwei Prompts zum Einfügen in Ihren MCP-Client:

  1. Run pci-dss-mcp triage on /Users/you/payments-service. Use min_severity=MEDIUM and group findings by PCI DSS requirement.

  2. Generate a PCI DSS compliance report for /Users/you/payments-service in JSON format. Show requirement-level pass/fail status and severity counts.

Tools

Tool

Zweck

Dokumentation

triage_findings

Alle Scanner + KI-Klassifizierung + Datei:Zeilen-Kontext in einem Aufruf

docs/triage_findings.md

generate_compliance_report

Rohbericht zu Anforderungs-Erfüllung (Orchestrator über alle Scanner)

docs/generate_compliance_report.md

scan_pan_data

PAN/SAD-Speicherung und Logging (3.3.1, 3.4.1, 3.5.1)

docs/scan_pan_data.md

check_encryption

Schwache Hashing-Verfahren, hartcodierte Schlüssel, unverschlüsseltes HTTP (4.2.1, 6.2.4)

docs/check_encryption.md

check_tls_config

Unsichere TLS-Konfigurationen (4.2.1)

docs/check_tls_config.md

check_secrets_in_configs

Anmeldedaten in Konfigurationsdateien (8.6.2)

docs/check_secrets_in_configs.md

check_error_handling

Fehlerantworten, die sensible Kontexte preisgeben (6.2.4)

docs/check_error_handling.md

check_auth_strength

Hartcodierte Passwörter, schwache Richtlinien, fehlende MFA, Webhook-Signaturen (8.3.1, 8.3.6, 8.4.2, 8.6.2)

docs/check_auth_strength.md

audit_log_coverage

Fehlende Audit-Logs bei Zahlungsabläufen (10.2.1)

docs/audit_log_coverage.md

check_data_retention

Fehlende TTL, sensible Speicherung, fehlendes Nullsetzen (3.2.1, 3.3.1)

docs/check_data_retention.md

check_payment_page_scripts

Fehlende CSP/SRI/Nonce auf Zahlungsseiten (6.4.3, 11.6.1)

docs/check_payment_page_scripts.md

check_dependencies

Anfällige Go-Abhängigkeiten via OSV (6.3.3); govulncheck-style Privatsphäre: keine Modulnamen werden an OSV.dev gesendet. Siehe docs/check_dependencies.md. Deckt auch update_vulnerability_db ab.

docs/check_dependencies.md

generate_sbom

CycloneDX 1.6 SBOM aus go.mod/go.sum (6.3.2)

docs/generate_sbom.md

explain_requirement

Nachschlagen einer PCI DSS v4.0.1-Anforderung nach ID

docs/explain_requirement.md

Alle Tools deklarieren ein typisiertes OutputSchema. Siehe docs/tools.md für den Katalogindex und die Migrationshistorie.

Dokumentation

Status

Aktive Entwicklung, vor v1.0. Siehe ROADMAP.md und CHANGELOG.md.

Lizenz

MIT, siehe LICENSE.


pci-dss-mcp ist ein Tool zur statischen Analyse. Es kann einen Qualified Security Assessor nicht ersetzen. Verwenden Sie die Ausgabe als Input für Ihren Compliance-Prozess, nicht als Compliance selbst.

Available Tools

15 tools
audit_log_coverageA

Scan Go source files for payment handlers missing structured audit logging (PCI DSS 10.2.1). Detects: missing logging, unstructured-only logging (fmt/log), and reports handlers with structured logging. Framework-aware: supports net/http, gin, echo handler signatures. Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns / min_severity / rule_filter for a filtered flat response.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +4 more. Returns: object

check_auth_strengthA

Scan Go source files for weak authentication: hardcoded passwords (PCI DSS 8.3.1), password policy with minimum length below 12 (PCI DSS 8.3.6), and payment routes missing MFA middleware (PCI DSS 8.4.2). Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns / min_severity / rule_filter for a filtered flat response. Maps findings to PCI DSS 8.3.1, 8.3.6, 8.4.2.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +4 more. Returns: object

check_data_retentionA

Scan Go source and config files for unsafe data retention: Redis/DB storage of CVV/PAN without TTL (PCI DSS 3.2.1), config files missing TTL on sensitive keys (PCI DSS 3.3.1), and incorrect memory zeroing timing after authorization. Scans .go, .yaml, .json, .toml files. Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns / min_severity / rule_filter for a filtered flat response. Maps findings to PCI DSS 3.2.1, 3.3.1.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +4 more. Returns: object

check_dependenciesA

Scan go.mod dependencies for known vulnerabilities (PCI DSS 6.3.3). Bulk-downloads the public OSV Go vulnerability snapshot and intersects locally against go.mod, matching the govulncheck privacy model. No module names are sent to OSV.dev. Cache TTL: 24h fresh, 24h-7d revalidate via ETag, >7d force-refresh. Run update_vulnerability_db first to bootstrap the cache for air-gapped environments. Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 1 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use min_severity / rule_filter / positive limit for a filtered flat response. Maps findings to PCI DSS 6.3.3.

Inputs: path (required), mode, cursor, limit, +2 more. Returns: object

check_encryptionA

Scan Go source files for encryption violations: weak hash algorithms (md5/sha1) with context scoring, hardcoded encryption keys/IVs, and plain HTTP URLs. Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns / min_severity / rule_filter for a filtered flat response. Maps findings to PCI DSS 6.2.4, 4.2.1.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +4 more. Returns: object

check_error_handlingA

Scan Go source files for payment handler error disclosure: detects err.Error() in http.Error, fmt.Fprintf with error variables, w.Write with error bytes, and json.Encode of errors. Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns / min_severity / rule_filter for a filtered flat response. Maps findings to PCI DSS 6.2.4.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +4 more. Returns: object

check_payment_page_scriptsA

Scan Go source files and HTML templates for payment page script security violations (PCI DSS 6.4.3, 11.6.1). Detects: missing Content-Security-Policy headers in Go payment handlers, unsafe-inline/unsafe-eval in CSP, external scripts without SRI (integrity attribute) in HTML templates, inline scripts without nonce attribute. Framework-aware: supports net/http, gin, echo handler signatures. Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns / min_severity / rule_filter for a filtered flat response. Maps findings to PCI DSS 6.4.3, 11.6.1.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +4 more. Returns: object

check_secrets_in_configsA

Scan configuration files (.env, .yaml, .json, .toml) for hardcoded secrets: API keys, passwords, tokens, and connection strings with embedded credentials. Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns / min_severity / rule_filter for a filtered flat response. Maps findings to PCI DSS 8.6.2.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +4 more. Returns: object

check_tls_configA

Scan Go source files for TLS configuration violations: InsecureSkipVerify, weak MinVersion (below TLS 1.2), missing MinVersion, and prohibited cipher suites (RC4, 3DES, NULL). Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns / min_severity / rule_filter for a filtered flat response. Maps findings to PCI DSS 4.2.1.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +4 more. Returns: object

explain_requirementA

Look up a PCI DSS v4.0.1 requirement by ID. Returns title, description, and testing procedure.

Inputs: requirement_id (required). Returns: requirement

generate_compliance_reportA

Raw PCI DSS v4.0.1 compliance report without AI triage — intended for CI gates, audit artifacts, and requirement-level pass/fail lists. For interactive "scan this project" prompts call triage_findings instead. Default unfiltered call returns a compact summary (metadata, totals, requirement_statuses, top 20 findings per severity, cursor for follow-up). Supply min_severity / rule_filter / limit to get a paged flat list (60 per page with cursor), or cursor= to resume a prior session (10-minute TTL). min_severity / rule_filter drop the response to shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Taint analysis is ON by default; set include_taint=false for fast dev iteration.

Inputs: path (required), dep_scan_mode, include_tests, include_taint, +4 more. Returns: object

generate_sbomA

Generate a CycloneDX v1.6 SBOM for a Go project. Default behavior: writes sbom.json (or sbom.xml when format=xml) next to the scanned go.mod and returns metadata only (output_path, size_bytes, component_count, unknown_licenses). Override the destination with output_path (must be absolute). Pass inline=true to return the serialized SBOM in the MCP response instead (capped at 64 KB; returns SBOM_TOO_LARGE above that). Parses go.mod + go.sum offline against the local GOMODCACHE; cache-miss modules surface as UNKNOWN-LICENSE. Satisfies PCI DSS 6.3.2 (software inventory, mandatory since March 2025).

Inputs: path (required), format, output_path, inline, +2 more. Returns: mode, bom_format, spec_version, component_count, +9 more

scan_pan_dataA

Default: returns response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 3 per severity findings - plus a pagination.next_cursor for drill-down. Prefer this for mixed queries; min_severity / rule_filter drop to response_shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list. Use include_tests / exclude_patterns for a filtered flat response. Maps findings to PCI DSS 3.3.1, 3.4.1, 3.5.1.

Inputs: path (required), exclude_patterns, include_tests, include_untracked, +5 more. Returns: object

triage_findingsA

Run all PCI DSS v4.0.1 scanners + AI-assisted prioritization + file:line enrichment on a Go project in a single call. Default: response_shape "summary" with by_severity counts, a capped by_rule histogram (top 10 + more_rules), and top 1 per severity enriched finding, plus pagination.next_cursor for drill-down. min_severity / rule_filter drop the response to shape "flat" but still carry summary.by_severity + summary.by_rule for full-scan context. Follow the cursor for the full paginated list.

Inputs: path (required), dep_scan_mode, include_tests, include_taint, +4 more. Returns: object

update_vulnerability_dbA

Download fresh OSV Go vulnerability snapshot to local cache for offline scanning. Downloads from gs://osv-vulnerabilities/Go/all.zip (~7.5MB). This is the ONLY tool that makes network requests. Cache stored at PCI_MCP_CACHE_DIR or ~/.pci-dss-mcp/vuln-cache/ by default.

Inputs: output_path. Returns: cache_path, vuln_count, download_size_bytes, previous_cache_date, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct security check or utility: audit log coverage, authentication strength, data retention, dependencies, encryption, error handling, payment page scripts, secrets, TLS, requirement lookup, compliance report, SBOM, PAN data scan, triage, and vulnerability DB update. No two tools have overlapping purposes.

    Naming Consistency5/5

    Tool names follow a clear verb_noun pattern (e.g., check_*, generate_*, explain_*, update_*, scan_*, triage_). All use consistent snake_case, and the verb clearly indicates the action. The slight deviation of 'audit_log_coverage' is minor and still descriptive.

    Tool Count5/5

    15 tools is well-scoped for a PCI DSS compliance server. It covers a wide range of checks (authentication, encryption, secrets, etc.) plus utilities (SBOM, report, requirement lookup), without being excessive or too few.

    Completeness5/5

    The tool set comprehensively covers PCI DSS requirements relevant to Go source code and configuration, including authentication (8.3), data retention (3.2, 3.3), encryption (4.2, 6.2), error handling (6.2), TLS (4.2), secrets (8.6), dependencies (6.3), and software inventory (6.3). The triage and report tools tie everything together.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      An AppSec-focused MCP server that performs static analysis scans on C/C++ source code for memory-safety vulnerabilities and parses compiled PE/ELF binary headers locally to audit active defensive compiler mitigations (ASLR, DEP/NX, PIE).
      4
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Agent-native "safe to ship?" security gate for AI-generated code. Uses real parsers and inter-rocedural taint analysis (JS/TS, Python, Go) to flag the classes AI coding agents get wrong — secrets, SQL injection, SS, SSRF, path traversal, command injection, weak JWT/CORS — and ranks findings by confidence. Exposes a scan tool over MCP.
      1
      8 npm
      2
      MIT