mcp-airlock vs io.github.coderifts/api-governance
mcp-airlock is an MCP server published by Shalimov04. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.coderifts/api-governance is an MCP server published by coderifts. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  mcp-airlock |  io.github.coderifts/api-governance |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Downloads/month (PyPI): 442 Downloads/week (PyPI): 92 Forks (GitHub): 7 Stars (GitHub): 15 Not marked · First seen |
Listed Version: 1.0.3 Forks (GitHub): 0 Stars (GitHub): 0 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 | mcp-airlock | io.github.coderifts/api-governance |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 15 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-airlock) | Remote server (app.coderifts.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 2 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/shalimov04/mcp-airlock | github.com/coderifts/api-governance |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-23 |
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
mcp-airlock
Governance proxy for MCP servers: allowlist, forced dry run, human confirmation, blast radius, audit
io.github.coderifts/api-governance
Signed, offline-verifiable contract-change authorization. Only a granted change can proceed.
How to run each
mcp-airlock
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: AIRLOCK_JWT_SECRET (secret), AIRLOCK_SECRET (secret), --policy, --upstream
io.github.coderifts/api-governance As a remote MCP server
claude mcp add --transport http api-governance https://app.coderifts.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.coderifts/api-governance has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.coderifts/api-governance publish no settings it asks for, so we do not compare settings.
What it can do: mcp-airlock · What it can do: io.github.coderifts/api-governance · 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.