TrigGuard
io.github.TrigGuard-AIPublished by GitHub account TrigGuard-AIv1.3.1Updated Oct 24, 2026
Deterministic execution authorization for AI agents and automated systems.
Overview
TrigGuard is a local MCP server that adds deterministic execution authorization, letting an assistant check whether an automated action is permitted before it's
- What you can do
- Provides deterministic execution authorization for AI agents and automated systems, so an assistant can request a decision on whether a given action is authorized before carrying it out. It routes authorization requests to a TrigGuard execution gateway, identifying the organization through a consumer header. No individual tools are listed in the supplied material, so the exact operations are not documented here.
- When to use it
- Consider it when an assistant or automated system needs a consistent, policy-driven check on whether an action may proceed before executing it, rather than relying on the model's own judgment.
- Requirements
- Runs locally over stdio, typically via npx from the npm package. Requires a TrigGuard gateway API key in TRIGGUARD_API_KEY, an organization id in TRIGGUARD_ORG_ID, and network access to the gateway; TRIGGUARD_GATEWAY_URL optionally overrides the default gateway origin.
Installation
In SourceWeft
- Open TrigGuard in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.3.1LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.