TrigGuard
NPM · @TRIGGUARD/MCP · SCANNED SEP 25
Deterministic execution authorization for AI agents and automated systems.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 35 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 659 tokens (~65/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the TrigGuard MCP server?
TrigGuard runs locally as an npm package, launched with npx -y @trigguard/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @trigguard/mcp
claude mcp add trigguard-ai-trigguard -- npx -y @trigguard/mcp
{
"mcpServers": {
"trigguard-ai-trigguard": {
"command": "npx",
"args": [
"-y",
"@trigguard/mcp"
]
}
}
} {
"servers": {
"trigguard-ai-trigguard": {
"command": "npx",
"args": [
"-y",
"@trigguard/mcp"
]
}
}
} codex mcp add trigguard-ai-trigguard -- npx -y @trigguard/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trigguard-ai-trigguard": {
"type": "local",
"command": [
"npx",
"-y",
"@trigguard/mcp"
],
"enabled": true
}
}
} openclaw mcp add trigguard-ai-trigguard --command npx --arg -y --arg @trigguard/mcp
mcp_servers:
trigguard-ai-trigguard:
command: "npx"
args: ["-y", "@trigguard/mcp"] {
"McpServers": {
"trigguard-ai-trigguard": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@trigguard/mcp"
]
}
}
} assistant mcp add trigguard-ai-trigguard -t stdio -c npx -a -y @trigguard/mcp
{
"mcpServers": {
"trigguard-ai-trigguard": {
"command": "npx",
"args": [
"-y",
"@trigguard/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +3
- Stability: unverified → 0.23 ▲ functional
- 9 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 8 Sept 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@trigguard/mcp@1.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 99 packages
| Packages resolved | 99 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
authorize_action ~130
Request TrigGuard authority for an action. Returns PERMIT, DENY, SILENCE, or ESCALATE with execution receipt metadata and v1.1 explanation fields (reason_code, escalation_*, policy_version, evaluation_id). SILENCE is withhold/no-commitment; ESCALATE is an approval lifecycle. Neither is PERMIT. Requires TRIGGUARD_API_KEY (gateway API key).
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Execution context (repository, environment, etc.) |
| subject | string | – | Optional subject digest |
| surface | string | yes | Execution surface (e.g. deploy.release) |
No output schema declared.
No examples provided.
explain_decision ~82
Explain a TrigGuard authority decision using an execution_id and/or a prior authorize_result payload. Returns structured reason_code, missing requirements, and next actions. Read-only — does not authorize.
| Name | Type | Req | Description |
|---|---|---|---|
| authorize_result | object | – | Optional prior authorize / gateway response object still in context |
| execution_id | string | – | Execution id (exec_…) from authorize_action |
No output schema declared.
No examples provided.
get_policy ~55
Read human-readable policy metadata for a surface from the bundled policy artifact. Does NOT evaluate live org policy — call authorize_action for PERMIT/DENY/SILENCE/ESCALATE.
| Name | Type | Req | Description |
|---|---|---|---|
| surface | string | yes | Surface id |
No output schema declared.
No examples provided.
get_surface ~34
Read execution surface registry metadata for one surface id (read-only, no policy evaluation).
| Name | Type | Req | Description |
|---|---|---|---|
| surface | string | yes | Surface id |
No output schema declared.
No examples provided.
health_check ~57
Check TrigGuard gateway reachability, policy engine status, registry hash, and whether API key / session JWT env vars are present (values are never returned).
| Name | Type | Req | Description |
|---|---|---|---|
| detailed | boolean | – | When true, include raw /health body under details |
No output schema declared.
No examples provided.
list_org_policies ~52
List org policies from the TrigGuard control plane Policy Platform. Requires TRIGGUARD_SESSION_TOKEN + TRIGGUARD_ORG_ID (session JWT rail — not gateway API key alone). Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_pending_policy_changes ~37
List pending policy change requests awaiting approval. Requires TRIGGUARD_SESSION_TOKEN + TRIGGUARD_ORG_ID. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_surfaces ~60
List registered execution surfaces from the gateway well-known registry (or local registry override). Read-only discovery.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max surfaces to return (default 50, max 200) |
| prefix | string | – | Optional surface id prefix filter |
No output schema declared.
No examples provided.
preview_policy_intent ~67
Compile-only preview of a policy intent against the Policy Platform. Requires TRIGGUARD_SESSION_TOKEN + TRIGGUARD_ORG_ID. Does not persist. Not a substitute for authorize_action.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | object | yes | Policy intent JSON (same shape as tg policy --file) |
No output schema declared.
No examples provided.
verify_receipt ~85
Verify a TrigGuard execution receipt by execution id. Optional include_receipt (default false) returns the receipt body. Requires gateway API key for authenticated lookup when the gateway enforces auth.
| Name | Type | Req | Description |
|---|---|---|---|
| execution_id | string | yes | Execution id (exec_…) |
| include_receipt | boolean | – | When true, include the receipt document in the response (v1.1) |
No output schema declared.
No examples provided.
What is the TrigGuard MCP server?
TrigGuard is an MCP server listed in the public MCP registry as io.github.TrigGuard-AI/trigguard. Deterministic execution authorization for AI agents and automated systems. This page covers its npm package (@trigguard/mcp).
Is the TrigGuard MCP server safe to use?
TrigGuard scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TrigGuard MCP server expose?
TrigGuard exposes 10 tools: authorize_action, verify_receipt, explain_decision, get_surface, list_surfaces, and 5 more. Their descriptions and schemas cost roughly 659 tokens of context every time the server is loaded.
Is the TrigGuard MCP server still maintained?
TrigGuard is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TrigGuard MCP server under?
TrigGuard declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.