mcp-airlock
io.github.Shalimov04/mcp-airlock
About mcp-airlock
mcp-airlock is an MCP server published by the GitHub account Shalimov04. Governance proxy for MCP servers: allowlist, forced dry run, human confirmation, blast radius, audit
It runs on your own machine: your AI client starts it from the PyPI package mcp-airlock at version 0.2.0.
It asks for 2 secrets: AIRLOCK_JWT_SECRET and AIRLOCK_SECRET. Give it a key with the least access that still works.
Version 0.2.0 was published on 16 September 2026, and the source code is public, so you can read it before installing.
Written from the registry entry. 9 automated checks on the registry entry and the package code: 7 pass, 0 warn, 0 fail, 2 info. How we check.
What it asks for
| Variable | Required | Secret | Description |
|---|---|---|---|
AIRLOCK_JWT_SECRET | No | Yes | HS256 secret for verifying bearer tokens (or set AIRLOCK_JWKS_URL for OIDC) |
AIRLOCK_SECRET | No | Yes | Key for signing confirmation tokens; set it when running more than one replica |
Checks
| Check | Result | Detail |
|---|---|---|
| Source repository linked | Pass | https://github.com/Shalimov04/mcp-airlock |
| Version pinned | Pass | Every package has an explicit version |
| Secrets requested | Info | Asks for 2 secrets: AIRLOCK_JWT_SECRET, AIRLOCK_SECRET |
| Known package registry | Pass | All packages come from npm, PyPI, OCI, NuGet or MCPB |
| Namespace ownership | Info | Name verified via GitHub account Shalimov04 |
| Registry text aimed at the AI | Pass | Description and settings contain no hidden characters or instructions to the AI |
| Install scripts | Pass | mcp-airlock 0.2.0 has no setup.py; nothing runs at install |
| Code red flags | Pass | Read 13 files in mcp-airlock 0.2.0: no obfuscation, encoded execution, credential reads or data-collection endpoints found |
| Text aimed at the AI | Pass | No hidden characters or instructions to the AI in 13 files, including comments and the README |
Popularity & health: 71 / 100
Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.
7 forks, 58 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.
What people say
No Hacker News threads link to its source code.
Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.
Facts
| Registry name | io.github.Shalimov04/mcp-airlock |
|---|---|
| Publisher | GitHub account Shalimov04 |
| How the name is verified | Name verified via GitHub account Shalimov04. The registry ties the name prefix to that account or domain; it does not check the code. |
| Type | Local: runs on your machine from a package |
| Packages | pypi mcp-airlock 0.2.0 (streamable-http) |
| Version | 0.2.0 |
| Published | |
| Last updated | |
| Source repository | https://github.com/Shalimov04/mcp-airlock |
| Website | None linked |
| Category | Agent safety & governance (assigned by keyword rule, not by hand) |
Related servers in Agent safety & governance
- sidclaw-governance-mcp7/7Governance proxy for MCP servers — policy evaluation, human…
- Agent Blast Radius7/7Scan what an AI agent running as you can reach; optionally verify…
- Spiderbrain8/8Deterministic context layer for your codebase: change impact, blast…
- kcp-harness — KCP compliance proxy7/7MCP compliance proxy between agent and tools: deterministic…
- aiglare7/7Audit AI/LLM features for governance guardrails: confidence,…
- Rail7/7Budgets, propose-then-approve, and receipts for agents that buy for…