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.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
docker run -i --rm ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
claude mcp add io.github.shyshlakov-pci-dss-mcp -- docker run -i --rm ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1在終端機中執行。
{ "mcpServers": { "io.github.shyshlakov-pci-dss-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
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.
Requires Go 1.25+; use Go 1.26.9 or newer, because Go 1.25 is past end of life:
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 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.
Listed as io.github.shyshlakov/pci-dss-mcp at registry.modelcontextprotocol.io. Auto-published on every tag.
Add to your MCP client config (Claude Desktop claude_desktop_config.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.
Two prompts to paste into your MCP client:
Run pci-dss-mcp triage on /Users/you/payments-service. Use min_severity=MEDIUM and group findings by PCI DSS requirement.Generate a PCI DSS compliance report for /Users/you/payments-service in JSON format. Show requirement-level pass/fail status and severity counts.All tools declare typed OutputSchema. See docs/tools.md for the catalog index and migration history.
Active development, pre v1.0. See ROADMAP.md and CHANGELOG.md.
MIT, see LICENSE.
pci-dss-mcp is a static analysis tool. It cannot replace a Qualified Security Assessor. Use its output as input to your compliance process, not as the compliance itself.
PCI DSS v4.0.1 compliance scanner for Go payment services, delivered as an MCP server
{ "mcpServers": { "io.github.shyshlakov-pci-dss-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1" ] } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
PCI DSS V4.0.1 Compliance Checker 透過 stdio 在本機執行。
上次檢查時間:2026-11-10。 PCI DSS v4.0.1 compliance scanner for Go payment services, delivered as an MCP server