MCP.Market

PCI DSS v4.0.1 Compliance Checker MCP server

by shyshlakov·io.github.shyshlakov/pci-dss-mcp·v0.7.1·3 stars

PCI DSS v4.0.1 compliance scanner for Go payment services, delivered as an MCP server

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

3 stars

Reviews

Write one

Nobody has reviewed PCI DSS v4.0.1 Compliance Checker yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PCI DSS v4.0.1 Compliance Checker tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 35 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How PCI DSS v4.0.1 Compliance Checker compares

Against every graded Finance MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 65% of 1,761 Finance servers
GitHub stars
3
more than 83% of 946 Finance servers

Install PCI DSS v4.0.1 Compliance Checker in Claude Code, Cursor or VS Code

claude mcp add pci-dss-mcp -- docker run -i --rm ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1
Add to Cursor

What the publisher says

From the PCI DSS v4.0.1 Compliance Checker repository's README, as published. We do not edit it. Read it on GitHub

pci-dss-mcp

Static analysis MCP server for Go payment service codebases. Every detected PCI DSS v4.0.1 violation in a Go payment service codebase is mapped to the specific requirement number before the code ships.

What it does

pci-dss-mcp is a stdio MCP server that runs 12 scanners, an orchestrator, and an AI triage engine over a Go payment service codebase. Each finding carries a requirement_id mapped to a specific PCI DSS v4.0.1 line item; see docs/requirement-mapping.md for the canonical rule-to-requirement table and testdata/vulnerable-payment-service/EXPECTED-FINDINGS.md for live golden output.

What pci-dss-mcp catches today

  • HTTP framework input flow into log / error / panic sinks. Tier 1 frameworks (gin, chi, gorilla/mux, net/http (Go 1.22+), echo v4, fiber v2) and Tier 1 loggers (log/slog, logrus, zap, zerolog, logr, klog, hclog) ship in v0.7. Tier 2 (kratos, apex/log, charmbracelet/log) lands in v0.8. Tier 3 (fasthttp, beego, iris, httprouter, project-internal) is user-configurable via Phase 25 YAML once shipped. See docs/httpinputtaint.md.

What pci-dss-mcp is NOT

  • Not a replacement for broad SAST. Use Semgrep, CodeQL, or gosec for OWASP Top-10 and language-agnostic vulnerabilities.
  • Not a replacement for LLM-based code review. pci-dss-mcp maps payment-specific issues to PCI DSS requirement IDs; LLM agents catch broad bugs via reasoning. The two layers compose.
  • Not Go-agnostic. Go-specific AST patterns and taint flow tracing are what make the precision possible.
  • Not a QSA replacement. Static analysis covers ~6% of PCI DSS v4.0.1 requirements. A Qualified Security Assessor must sign off on the rest.

Install

Go install (primary)

Requires Go 1.25+:

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

The binary lands at $(go env GOPATH)/bin/pci-dss-mcp. See docs/install-from-source.md for PATH resolution, the macOS codesign provenance fix, cosign verification, and the MCP client JSON config.

Docker (alternative)

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

Useful for CI pipelines, QSA auditors who do not develop Go locally, or any environment without a host Go toolchain.

MCP Registry

Listed as io.github.shyshlakov/pci-dss-mcp at registry.modelcontextprotocol.io. Auto-published on every tag.

Usage

Add to your MCP client config (Claude Desktop claudedesktopconfig.json, Cursor .cursor/mcp.json, or claude mcp add for 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= and dst= mirror the same absolute path so the container sees your code at the same path your host uses; prompts pass the normal host path with no translation. For the go install variant and per-client examples, see docs/usage.md.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

PCI DSS v4.0.1 Compliance Checker: common questions

Is PCI DSS v4.0.1 Compliance Checker MCP server safe?
Mostly: it is graded B (80/100). Read the PCI DSS v4.0.1 Compliance Checker safety report
How do I install PCI DSS v4.0.1 Compliance Checker?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does PCI DSS v4.0.1 Compliance Checker need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is PCI DSS v4.0.1 Compliance Checker maintained?
The last commit was 72 days ago (2026-08-24). The latest release is v0.7.1.
What can I use instead of PCI DSS v4.0.1 Compliance Checker?
Servers from other publishers that do the same job: three.ws Agent Payments MCP server, Yolfi Payments MCP server and X402 List MCP server.
How does PCI DSS v4.0.1 Compliance Checker compare with other Finance MCP servers?
safety score 80/100 (higher than 65% of 1,761 Finance servers); github stars 3 (more than 83% of 946 Finance servers). Full comparison.

Alternatives to PCI DSS v4.0.1 Compliance Checker

Same job from other publishers: the closest match first, then the best rated.