Trust Gate MCP — First post-quantum MCP server. Policy-gated AI agent decisions with hybrid Ed25519 + ML-DSA-65 (NIST FIPS 204) cryptographic receipts. No Receipt. No Trust.

Name: Trust Gate MCP — First post-quantum MCP server. Policy-gated AI agent decisions with hybrid Ed25519 + ML-DSA-65 (NIST FIPS 204) cryptographic receipts. No Receipt. No Trust.
Author: Cyber-Warrior-Network

@Cyber-Warrior-Network

代码仓库

关于 Trust Gate MCP — First post-quantum MCP server. Policy-gated AI agent decisions with hybrid Ed25519 + ML-DSA-65 (NIST FIPS 204) cryptographic receipts. No Receipt. No Trust.

The first production MCP server with NIST FIPS 204 post-quantum receipts. Every AI agent tool call is policy-gated, hybrid-signed (Ed25519 + ML-DSA-65), and forensically provable — offline, forever. Fail-closed architecture: if the Trust Gate backend is unreachable, every decisio

#mcp #ai-safety #post-quantum #trust #cryptography #fips-204 #eu-ai-act #agent-firewall #prompt-injection #ml-dsa

基本信息

分类

AI 与智能体

传输方式

stdio

发布者

Cyber-Warrior-Network

提交者

CWNApps

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "trust-gate": {
      "command": "uvx",
      "args": [
        "trust-gate-mcp"
      ],
      "env": {
        "TRUST_GATE_API_KEY": "your-api-key"
      }
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is Trust Gate MCP?

Trust Gate MCP is the first production MCP server implementing NIST FIPS 204 post-quantum receipts. It policy-gates every AI agent tool call and produces hybrid Ed25519 + ML-DSA-65 signed receipts, making each decision provable offline, forever. It is designed for AI agents that require auditable, quantum-resistant proof of their actions.

How to use Trust Gate MCP?

Add to Claude Desktop via a JSON configuration entry with command: "uvx" and args: ["trust-gate-mcp"], set the environment variable TRUST_GATE_API_KEY. For Claude Code, run claude mcp add trust-gate -- uvx trust-gate-mcp. Alternatively, install with pip install trust-gate-mcp and run with the API key set. The server exposes four tools: gate_decision, verify_receipt, check_policy, and health.

Key features of Trust Gate MCP

Hybrid Ed25519 + ML-DSA-65 (NIST FIPS 204) signing
Policy-gated AI agent decisions with risk scores
Offline post-quantum receipt verification
Three-layer security: sanitization, policy, fail-closed
Fail-closed guarantee: outage makes system more conservative
47 passing unit tests, 51 OWASP ASI checks passed

Use cases of Trust Gate MCP

Compliance: meeting EU AI Act Article 50 transparency obligations
Quantum-proof auditing: retain verifiable receipts beyond the quantum computing era
Security: prevent tool poisoning, injection, and exfiltration attacks
Deployment guard: gate code deploys, data writes, or user-facing actions

FAQ from Trust Gate MCP

How does Trust Gate MCP achieve post-quantum security?

Every receipt is hybrid-signed: Ed25519 (classical) and ML-DSA-65 (NIST FIPS 204, security level 3) over the same evidence hash, simultaneously. Both signatures and the ML-DSA-65 public key are embedded in the receipt.

Can receipts be verified offline?

Yes. Provide the ml_dsa_signature and ml_dsa_public_key from the receipt to verify the ML-DSA-65 signature. No backend call or network access is required, and verification remains valid even against a quantum adversary.