Trust Gate MCP
Related Servers
Alternatives to Trust Gate MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to sign decisions with post-quantum cryptographic proofs and maintain secure audit trails for compliance. It provides tools for stamping events, verifying chain integrity, and exporting audit data across industries like finance and healthcare.439 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides cryptographic governance receipts for AI agents, enabling pre-execution evaluation and signed verdicts (EXECUTE/BLOCK/REVIEW/SHADOW) with offline-verifiable audit trails.MIT
- FlicenseNot gradedqualityCmaintenanceSuperseded. Earlier version of the DCL product (MCP endpoint at /sse with API key, plus an offline desktop audit trail). Not the current path for agents. Use the hosted DCL Trust Oracle: https://github.com/Fronesis-Labs/dcl-webhook (MCP endpoint https://mcp.fronesislabs.com/mcp, Streamable HTTP, x402 payment, no API key).-
- AlicenseAqualityCmaintenanceProvides tools to issue, verify, and export cryptographically signed receipts for AI agent actions, enabling tamper-proof audit trails for compliance with regulations like the EU AI Act.435 npm1MIT

evermint-mcpofficial
AlicenseNot gradedqualityDmaintenanceTamper-evident receipts for AI agent actions. The notary layer for agent-to-agent transactions.22 npm1MIT- AlicenseNot gradedqualityBmaintenanceIssue and verify signed receipts for agent actions, enabling durable, independently checkable proof of policy decisions. Supports offline verification via get_keyset and verify_receipt tools without an account.0Inno Setup
TDQS
Scored across 7 tools
Receipt minting appears in mint_receipt_for_record_change, mint_action_receipt, gate_decision, and implicitly check_egress/run_exit_drill, but detailed descriptions separate CRM record changes from arbitrary actions and gate verdicts. A caller might still momentarily confuse mint_action_receipt with gate_decision when an action involves a gate verdict word, though the reserved-word note mitigates this.
Almost all names use snake_case with a leading verb (verify_, mint_, audit_, check_, run_), and the pattern is easy to scan. Minor deviations: gate_decision reads more like a noun phrase than a verb_noun action, and audit_my_agent_inventory adds 'my' and is longer than the others.
Seven tools is well within the ideal 3-15 range for a narrowly scoped trust/receipt server. Each tool covers a distinct operation — verify, mint two receipt types, gate, egress classify, audit inventory, exit drill — so none feels redundant or purely ornamental.
Core receipt lifecycle is present: mint signed receipts, verify offline, gate decisions, egress classification, inventory audit, and exit drill. Missing a few ancillary lifecycle operations such as explicit key management/rotation, receipt listing/retrieval, or a post-escalation human decision path, but these are either outside scope or intentionally external.