TrigGuard vs io.github.inkog-io/inkog
TrigGuard is an MCP server published by TrigGuard-AI. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.inkog-io/inkog is an MCP server published by inkog-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  TrigGuard |  io.github.inkog-io/inkog |
|---|---|---|
| Official MCP Registry | Listed Version: 1.3.1 Downloads/month (npm): 83 Downloads/week (npm): 13 Not marked · First seen |
Listed Version: 1.0.20 Downloads/month (npm): 528 Downloads/week (npm): 55 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | TrigGuard | io.github.inkog-io/inkog |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 3 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@trigguard/mcp) | On your machine (@inkog-io/mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/trigguard-ai/trigguard | github.com/inkog-io/inkog-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
TrigGuard
Deterministic execution authorization for AI agents and automated systems.
io.github.inkog-io/inkog
Security co-pilot for AI agents. Scan for vulnerabilities, audit MCP servers, verify governance.
How to run each
TrigGuard As a local MCP server: npm package
claude mcp add --env "TRIGGUARD_API_KEY=<YOUR_TRIGGUARD_API_KEY>" --env "TRIGGUARD_ORG_ID=<YOUR_TRIGGUARD_ORG_ID>" --transport stdio trigguard -- npx -y @trigguard/mcpRequires: TRIGGUARD_API_KEY (secret), TRIGGUARD_ORG_ID
io.github.inkog-io/inkog As a local MCP server: npm package
claude mcp add --env "INKOG_API_KEY=<YOUR_INKOG_API_KEY>" --transport stdio inkog -- npx -y @inkog-io/mcpRequires: INKOG_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only TrigGuard asks for
TRIGGUARD_API_KEY (secret)TRIGGUARD_GATEWAY_URLTRIGGUARD_ORG_ID
Only io.github.inkog-io/inkog asks for
INKOG_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: TrigGuard · What it can do: io.github.inkog-io/inkog · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.