Build a PQC-Authenticated AI Agent via MCP

Evaluate QNSI Vault, KMS, Audit, and Crypto Inventory surfaces through the MCP integration contract. Tool-call signing, audit coverage, plaintext handling, and end-to-end runtime behavior are NOT VERIFIED.

Verification boundary: Package and snippet presence do not prove MCP route reachability, PQC signing, audit effects, secret handling, or deployment behavior; all remain NOT VERIFIED.

NOT VERIFIEDDeployment timing

MCPPrimary SDK

3Source surfaces

MCP Server →

Audit Service →

Quantum-Safe Vault →

Claude Desktop config - add the QNSI MCP serverjson

{
  "mcpServers": {
    "qnsp": {
      "command": "pnpm",
      "args": ["dlx", "@heossihq/qnsi-mcp"],
      "env": {
        "QNSI_API_KEY": "qnsp_pqc_api_..."
      }
    }
  }
}

Programmatic MCP client contracttypescript

import { QnspMcpClient } from "@heossihq/qnsi-mcp";

const mcp = new QnspMcpClient({ apiKey: process.env.QNSI_API_KEY! });

// Source-linked MCP call; ML-DSA signing and audit effects are NOT VERIFIED
const tools = await mcp.listTools();
// → [{ name: "qnsp_vault_get", ... }, { name: "qnsp_kms_sign", ... }]

const result = await mcp.callTool("qnsp_vault_get", {
  secretId: "openai-key",
});
// Returned payload protection and plaintext handling are NOT VERIFIED

Sovereign AI labs →

Multi-tenant SaaS →

Get a free API key Back to all patterns Full API reference

Build a PQC-Authenticated AI Agent via MCP

Stack

Published SDK calls

Inspect the source-linked integration surface