PCI DSS v4.0.1 compliance scanner for Go payment services, delivered as an MCP server
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like PCI DSS v4.0.1 Compliance Checker.
Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-shyshlakov-pci-dss-mcp": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-io-github-shyshlakov-pci-dss-mcp"
]
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
PCI DSS v4.0.1 Compliance Checker is an MCP server for PCI DSS v4.0.1 compliance scanner for Go payment services, delivered as an MCP server. It supports STDIO transport.
Use the client-specific config in Install and add it to your MCP-compatible client.
Choose the Claude Desktop tab in Install and copy the config into Claude Desktop's MCP server settings.
Choose the Claude Code tab in Install and copy the config into Claude Code's MCP server settings.
Choose the Codex tab in Install and copy the config into Codex's MCP server settings.
Choose the Cursor or VS Code tab in Install and copy the config into Cursor or VS Code's MCP server settings.
PCI DSS v4.0.1 Compliance Checker uses STDIO transport. Use the package or command config in Install.
PCI DSS v4.0.1 Compliance Checker inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
PCI DSS v4.0.1 Compliance Checker does not advertise a verified auth requirement. If discovery fails, it may still need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
ghcr.io/shyshlakov/pci-dss-mcp:v0.7.1stdio | oci | Not captured | None advertised |