Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TrigGuard

NPM · @TRIGGUARD/MCP-SERVER · SCANNED AUG 20

Execution authorization for AI agents and automated systems.

Available components

npm · @trigguard/mcp-server 64
64 Trust /100
Trust breakdown (6 categories)

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 →

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
  • 30 of 98 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 0 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @trigguard/mcp-server

# add to Claude Code
claude mcp add trigguard-ai-trigguard -- npx -y @trigguard/mcp-server
# add to Codex CLI
codex mcp add trigguard-ai-trigguard -- npx -y @trigguard/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trigguard-ai-trigguard": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@trigguard/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add trigguard-ai-trigguard --command npx --arg -y --arg @trigguard/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  trigguard-ai-trigguard:
    command: "npx"
    args: ["-y", "@trigguard/mcp-server"]
// mcp.json
{
  "mcpServers": {
    "trigguard-ai-trigguard": {
      "command": "npx",
      "args": [
        "-y",
        "@trigguard/mcp-server"
      ]
    }
  }
}
Changelog

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.

  • 20 Aug 26 64

    First indexed and scored.

Diagnostics

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 20 Aug 2026 · Analysed npm/@trigguard/mcp-server@1.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 98 packages
Packages resolved 98
Stale 30
Tree resolution Complete
MCP tools · 10 exposed · ~659 tokens

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.

Tool Tokens
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).

NameTypeReqDescription
contextobject–Execution context (repository, environment, etc.)
subjectstring–Optional subject digest
surfacestringyesExecution 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.

NameTypeReqDescription
authorize_resultobject–Optional prior authorize / gateway response object still in context
execution_idstring–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.

NameTypeReqDescription
surfacestringyesSurface 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).

NameTypeReqDescription
surfacestringyesSurface 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).

NameTypeReqDescription
detailedboolean–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.

NameTypeReqDescription
limitnumber–Max surfaces to return (default 50, max 200)
prefixstring–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.

NameTypeReqDescription
intentobjectyesPolicy 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.

NameTypeReqDescription
execution_idstringyesExecution id (exec_…)
include_receiptboolean–When true, include the receipt document in the response (v1.1)

No output schema declared.

No examples provided.