proofgate-runtime
Related Servers
Alternatives to proofgate-runtime
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables agents to cryptographically attest and verify identity and execution state through RFC 7519 JWT HMAC-SHA256 signature checks, claims and expiration validation, constant-time secret comparison, SHA-256 Merkle inclusion proofs, Schnorr zero-knowledge identification, and sliding-window nonce replay protection. It runs as a zero-dependency Python MCP server over stdio, so it can be attached to Claude Desktop, Cursor, or Windsurf without external libraries.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to cryptographically verify JWT HMAC-SHA256 signatures, validate claims and enforce expiration, and perform Merkle inclusion proofs, Schnorr zero-knowledge identification, and nonce replay protection. Runs as a zero-dependency stdio MCP server so clients like Claude Desktop, Cursor, and Windsurf can attest execution state without OpenSSL or external libraries.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to construct SHA-256 Merkle trees and generate/verify inclusion proofs, validate JWT HMAC-SHA256 claims, run Schnorr zero-knowledge identification, and enforce constant-time secret comparison with nonce replay protection for tamper-evident state attestation. It runs as a zero-dependency, stdlib-only MCP stdio server for clients such as Claude Desktop, Cursor, and Windsurf.7MIT
- AlicenseBqualityCmaintenancePrivacy-first, tamper-evident receipts for MCP tool calls. It hashes and signs arguments/results so you can verify what ran, when, without storing raw payloads.2MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables real-time injection fuzzing, exfiltration canary detection, least-privilege tool sandboxing, and cryptographic audit proofs for untrusted prompts, RAG context, and agent actions over MCP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables enterprise MCP security auditing through 12 deterministic no-LLM tools for evidence-gated claims, skill/prompt supply-chain audits, token profiling, and server auth-mode checks.MIT
TDQS
Scored across 5 tools
Each tool has a distinct target: claims verification, receipt creation, receipt verification, injection filtering, and runtime metadata. The only mild overlap is between verify_claims and verify_receipt, where an agent must read descriptions to know which object is being verified.
Four of five tools follow a clean verb_noun pattern (verify_claims, make_receipt, verify_receipt, check_injection). runtime_info breaks the pattern as a noun-only name, but the overall convention is predictable and readable.
Five tools is well-scoped for a proof/verification runtime, with each tool earning its place. No redundant or filler tools are present.
The core lifecycle—verify claims, issue receipts, verify receipts, screen input, report capabilities—is covered. The notable gap is that receipt signing is only available via CLI, and there is no listing or lookup of existing receipts, though agents can work around the signing gap.