Developer · Local MCP server
PQC-Khepra MCP - CMMC Autopilot & AI Security Recorder
Post-quantum CMMC compliance scanner & AI agent attestation. FIPS 140-3, ML-DSA-65, 36K+ mappings.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nouchix/pqc-khepra-mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-06-15
- Updated
- 2026-06-15
- Publisher
- nouchix (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/nouchix) · how
- Repository
- github.com/nouchix/PQC-Khepra-MCP.git
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker)runtime: docker | ghcr.io/nouchix/pqc-khepra-mcp:v1.0.0 | - | stdio |
How to connect PQC-Khepra MCP - CMMC Autopilot & AI Security Recorder
PQC-Khepra MCP - CMMC Autopilot & AI Security Recorder runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/nouchix/pqc-khepra-mcp:v1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e KHEPRA_MODE -e KHEPRA_LICENSE_KEY -e SUPABASE_URL -e SUPABASE_ANON_KEY ghcr.io/nouchix/pqc-khepra-mcp:v1.0.0. It reads these environment variables: KHEPRA_MODE, KHEPRA_LICENSE_KEY (secret), SUPABASE_URL and SUPABASE_ANON_KEY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pqc-khepra-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KHEPRA_MODE",
"-e",
"KHEPRA_LICENSE_KEY",
"-e",
"SUPABASE_URL",
"-e",
"SUPABASE_ANON_KEY",
"ghcr.io/nouchix/pqc-khepra-mcp:v1.0.0"
],
"env": {
"KHEPRA_MODE": "<value>",
"KHEPRA_LICENSE_KEY": "<secret>",
"SUPABASE_URL": "<value>",
"SUPABASE_ANON_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Power Automate MCP Server by Flow StudioDebug, build, and manage Power Automate cloud flows with AI agents. | Remote · HTTPLive check: ✓ handshake |
| Power Portals ProComponent API, code samples and Dataverse metadata for building Power Portals Pro portals. | Local · stdio |
| Powershell MCPHeadless Windows ops over MCP: hidden PowerShell plus in-process SSH, WinRM and SFTP. | Local · stdio |
| Pptmasterdeck MCPA paid remote MCP for ppt-master, built to return verdicts, receipts, usage logs, and audit-ready JS. | Remote · HTTPLive check: ✗ no handshake |
| pqc-scanThe cryptography a JavaScript or TypeScript codebase uses, and which a quantum computer would break. | Local · stdio |
| Pqs MCP ServerPQS scores any prompt before the model runs. 8 dimensions. 5 frameworks. Pre-flight, not post-hoc. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Pramana MCPRead your recorded AI agent runs, and what changed when you swapped a model or prompt. | Local · stdio |
| Predictive DebuggerPredicts where JavaScript and TypeScript code will fail at runtime, for coding agents. | Local · stdio |