Skip to content

Trust Gate MCP server

io.github.CWNApps/trust-gate-mcpCWNAppsstreamable-httpv0.2.0Scanned

Post-quantum, tamper-evident receipts for agent actions. Ed25519 + ML-DSA-65, offline verify.

16 tools: 11 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 11 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

11 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Trust Gate MCP server can do

The Trust Gate MCP server is published by the GitHub account CWNApps. It has 16 tools. It can create or change data (11 tools: mint_receipt_for_record_change, audit_my_agent_inventory, mint_action_receipt, verify_receipt and 7 more), but cannot delete data. 5 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

16 tools

Changes things 11Claude Code: ask
  • audit_my_agent_inventoryRank a CALLER-PROVIDED list of MCP tools by worst-regret if they act (a name-based heuristic that weights a name's first word most).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Rank a CALLER-PROVIDED list of MCP tools by worst-regret if they act (a name-based heuristic that weights a name's first word most). Read-only: it mints no receipt. Cannot auto-discover the inventory -- MCP does not allow that; the caller must pass it in.
  • check_egressEgress classification check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Egress classification check. Scans a data sample for a finite list of sensitivity markers and classifies as NO_MARKERS_FOUND / INTERNAL / CONFIDENTIAL / RESTRICTED. RESTRICTED sets blocked=true; this tool cannot block anything itself, and NO_MARKERS_FOUND is not clearance to send. Returns classification, retention info, and a tamper-evident receipt.
  • export_acceptance_packAcceptance-pack export for one or more cases, optionally mapped to one control id and version you name.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Acceptance-pack export for one or more cases, optionally mapped to one control id and version you name. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.
  • gate_decisionTwo-phase decision gate with a real verdict.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Two-phase decision gate with a real verdict. PREVIEW returns ALLOW, DENY or ESCALATE with the risk tier and reasons, plus a preview_id, without acting. COMMIT re-evaluates the same inputs and mints a signed receipt for the verdict. Only ALLOW returns a GRANTED permit; DENY returns DENIED; ESCALATE returns WITHHELD_PENDING_HUMAN and a human must decide outside this tool. Applies only to actions the caller routes through it: it does not observe or block what an agent does. Verb-tier heuristic on the action name and resource, not a proof. Stateless. Optional attestation: triggered_by_type, triggered_by_source, decision_model.
  • mint_action_receiptMint a signed receipt (Ed25519, plus ML-DSA-65 when the post-quantum backend is available) for an arbitrary consequential agent action.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Mint a signed receipt (Ed25519, plus ML-DSA-65 when the post-quantum backend is available) for an arbitrary consequential agent action. Optional attestation: triggered_by_type (human/agent/script), triggered_by_source (api/cli/cron), decision_model (the LLM model used). Attestation values are caller claims: allowlisted to safe characters, signed, not verified. Decisions that contain a gate verdict word are reserved for gate_decision.
  • mint_receipt_for_record_changeMint a signed receipt (Ed25519, plus ML-DSA-65 when the post-quantum backend is available) for one CRM record change.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Mint a signed receipt (Ed25519, plus ML-DSA-65 when the post-quantum backend is available) for one CRM record change. Old/new values are carried as SHA-256 hashes. Works with any CRM (Relaticle, hosted CRMs, custom).
  • propose_requalificationImpact and a requalification PROPOSAL for a change, over the graph you supply.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Impact and a requalification PROPOSAL for a change, over the graph you supply. It never runs a retest. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.
  • propose_role_questionQuestions routed to a role for one oversight case, from the records and source lookups you supply.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Questions routed to a role for one oversight case, from the records and source lookups you supply. It proposes; it never asks anyone. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.
  • replay_decisionReplay of a decision's evidence path over the records you supply.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Replay of a decision's evidence path over the records you supply. It replays records; it executes nothing. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.
  • run_exit_drillVendor exit readiness drill.No findings

    Why it is in this group

    • The name "run_exit_drill" says "run": a word for a change.
    Description, as the server wrote it
    Vendor exit readiness drill. Checks local signing key, local model access (Ollama). Returns step-by-step results and a tamper-evident receipt. Informational; it signs one receipt, which creates the signing key on a host that has none yet.
  • verify_receiptVerify a TrustGate receipt from the certificate alone (offline).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a TrustGate receipt from the certificate alone (offline). ok=true means unchanged since signing, signed, kid consistent with the embedded key, and (require_pq default on) at least one post-quantum leg verified; unsigned receipts fail. It does not prove who signed: pass expected_kid to pin the signer's Ed25519 key; a pin counts only when that key's own signature verifies (see signer_pinned). The post-quantum keys in a receipt are not covered by the kid.
Only reads 5Show 5 read-only tools
  • compare_qualification_changeStatus of each proposed retest after a change (current, not current or unbound), from the proposal inputs and results you supply.No findings

    Why it is in this group

    • The name "compare_qualification_change" says "compare": a word for reading.
    Description, as the server wrote it
    Status of each proposed retest after a change (current, not current or unbound), from the proposal inputs and results you supply. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.
  • get_decision_evidenceEvidence view, verdict and open questions for one decision and the facts you supply.No findings

    Why it is in this group

    • The name "get_decision_evidence" says "get": a word for reading.
    Description, as the server wrote it
    Evidence view, verdict and open questions for one decision and the facts you supply. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.
  • get_intervention_evidenceEvidence for whether an intervention could be shown to have taken effect, from the records you supply.No findings

    Why it is in this group

    • The name "get_intervention_evidence" says "get": a word for reading.
    Description, as the server wrote it
    Evidence for whether an intervention could be shown to have taken effect, from the records you supply. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.
  • get_receipt_evidenceEvidence view of one receipt you supply, with what the service could and could not check.No findings

    Why it is in this group

    • The name "get_receipt_evidence" says "get": a word for reading.
    Description, as the server wrote it
    Evidence view of one receipt you supply, with what the service could and could not check. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.
  • inspect_oversight_caseReadiness report for one oversight case, computed from the records you supply.No findings

    Why it is in this group

    • The name "inspect_oversight_case" says "inspect": a word for reading.
    Description, as the server wrote it
    Readiness report for one oversight case, computed from the records you supply. Read-only view of the records you supply; it writes, signs and executes nothing. Needs TRUST_GATE_API_URL, TRUST_GATE_API_KEY and TRUST_GATE_TENANT_ID to be set, and the tenant comes from that setting, never from an argument. Returns status OK, REFUSED or UNAVAILABLE (a missing setting, a surface that is off, or an error is UNAVAILABLE, never made-up data). The TrustGate API must be a version that serves this view; it returns UNAVAILABLE until then. A mapping or readout is not a compliance finding.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:57 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://trust-gate-mcp.onrender.com/mcp: tools/list returned 16 tools to an anonymous client, including mint_receipt_for_record_change (write), audit_my_agent_inventory (write), mint_action_receipt (write), verify_receipt (write), gate_decision (write) and 6 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 7 to 11

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools9 added, 1 changed.+9 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 11.View diff
    • Tools that change things, listed without credentials: 7 to 11

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http trust-gate https://trust-gate-mcp.onrender.com/mcp
claude mcp add --transport http trust-gate https://trust-gate-mcp.onrender.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__trust-gate__inspect_oversight_case",
      "mcp__trust-gate__get_intervention_evidence",
      "mcp__trust-gate__compare_qualification_change",
      "mcp__trust-gate__get_receipt_evidence",
      "mcp__trust-gate__get_decision_evidence"
    ],
    "ask": [
      "mcp__trust-gate__mint_receipt_for_record_change",
      "mcp__trust-gate__audit_my_agent_inventory",
      "mcp__trust-gate__mint_action_receipt",
      "mcp__trust-gate__verify_receipt",
      "mcp__trust-gate__gate_decision",
      "mcp__trust-gate__check_egress",
      "mcp__trust-gate__run_exit_drill",
      "mcp__trust-gate__propose_role_question",
      "mcp__trust-gate__export_acceptance_pack",
      "mcp__trust-gate__replay_decision",
      "mcp__trust-gate__propose_requalification"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as trust-gate. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.CWNApps/trust-gate-mcp/verify?hash=db3eb493c13e04d27e4565061fd1a85ba1b08efd1ec40eecd667d2d9303445b6" | jq -e '.changed == false'

Pinned hash db3eb493c13e, from Nov 15, 2026, 18:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.CWNApps/trust-gate-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.CWNApps/trust-gate-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.CWNApps/trust-gate-mcp.svg)](https://radar.anlyon.com/servers/io.github.CWNApps/trust-gate-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.

Trust Gate MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Trust Gate MCP server safe?

No scan can promise that. What its definitions show: 16 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Trust Gate MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Trust Gate MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Trust Gate MCP server have?

16 tools: 11 write, 5 read. mint_receipt_for_record_change, audit_my_agent_inventory, mint_action_receipt, verify_receipt, gate_decision, check_egress, run_exit_drill, propose_role_question and 8 more.

Does the Trust Gate MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Trust Gate MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Trust Gate MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.