# mcp-airlock (pypi · mcp-airlock)

Governance proxy for MCP servers: allowlist, forced dry run, human confirmation, blast radius, audit

- Trust score: 35/100 (low)
- Change this week: −15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `mcp-airlock`: 35/100 (this document), [markdown](https://verifymcp.io/servers/shalimov04-mcp-airlock/mcp-airlock.md), [page](https://verifymcp.io/servers/shalimov04-mcp-airlock/mcp-airlock)

## Channel facts

- Registry: `pypi`
- Package: `mcp-airlock`
- Version: `0.2.0`
- Transport: `streamable-http`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs uv_build at install time, a recognised build step with no custom scripting around it.
  - 1 of 36 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Shalimov04/mcp-airlock).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 24 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it.

## Install

### How do I install the mcp-airlock server?

mcp-airlock runs locally as a PyPI package, launched with uvx mcp-airlock --env prod, plus the required --policy and --upstream, which you supply. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add shalimov04-mcp-airlock -- uvx mcp-airlock --env prod
```

Incomplete: the registry marks --policy and --upstream as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Cursor

```json
{
  "mcpServers": {
    "shalimov04-mcp-airlock": {
      "command": "uvx",
      "args": [
        "mcp-airlock",
        "--env",
        "prod"
      ]
    }
  }
}
```

Incomplete: the registry marks --policy and --upstream as required and gives no value we can show, so they are not in this command. Add them before you run it.

### VS Code

```json
{
  "servers": {
    "shalimov04-mcp-airlock": {
      "command": "uvx",
      "args": [
        "mcp-airlock",
        "--env",
        "prod"
      ]
    }
  }
}
```

Incomplete: the registry marks --policy and --upstream as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Codex

```bash
codex mcp add shalimov04-mcp-airlock -- uvx mcp-airlock --env prod
```

Incomplete: the registry marks --policy and --upstream as required and gives no value we can show, so they are not in this command. Add them before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shalimov04-mcp-airlock": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-airlock",
        "--env",
        "prod"
      ],
      "enabled": true
    }
  }
}
```

Incomplete: the registry marks --policy and --upstream as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Hermes

```yaml
mcp_servers:
  shalimov04-mcp-airlock:
    command: "uvx"
    args: ["mcp-airlock", "--env", "prod"]
```

Incomplete: the registry marks --policy and --upstream as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Netclaw

```json
{
  "McpServers": {
    "shalimov04-mcp-airlock": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-airlock",
        "--env",
        "prod"
      ]
    }
  }
}
```

Incomplete: the registry marks --policy and --upstream as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Other

```json
{
  "mcpServers": {
    "shalimov04-mcp-airlock": {
      "command": "uvx",
      "args": [
        "mcp-airlock",
        "--env",
        "prod"
      ]
    }
  }
}
```

Incomplete: the registry marks --policy and --upstream as required and gives no value we can show, so they are not in this command. Add them before you run it.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 35, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-25 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-24 (score 35, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-23 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-13 (score 35, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-12 (score 50, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-28 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 0)

- [functional improvement] License: fail → pass
- [functional] Licence: MIT

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/shalimov04-mcp-airlock/mcp-airlock#diagnostics

## Score history

- 2026-11-05: 35
- 2026-11-04: 50
- 2026-11-03: 50
- 2026-11-02: 50
- 2026-11-01: 50
- 2026-10-31: 50
- 2026-10-30: 50
- 2026-10-29: 50
- 2026-10-28: 50
- 2026-10-27: 50
- 2026-10-26: 50
- 2026-10-25: 50
- 2026-10-24: 35
- 2026-10-23: 50
- 2026-10-22: 35
- 2026-10-21: 35
- 2026-10-20: 35
- 2026-10-19: 35
- 2026-10-18: 35
- 2026-10-17: 35
- 2026-10-16: 35
- 2026-10-15: 35
- 2026-10-14: 35
- 2026-10-13: 35
- 2026-10-12: 50
- 2026-10-05: 35
- 2026-10-04: 35
- 2026-10-03: 35
- 2026-10-02: 35
- 2026-10-01: 35

## Common questions

### What is the mcp-airlock server?

mcp-airlock is listed in the public MCP registry as io.github.Shalimov04/mcp-airlock. Governance proxy for MCP servers: allowlist, forced dry run, human confirmation, blast radius, audit. This page covers its PyPI package (mcp-airlock).

### Is the mcp-airlock server safe to use?

mcp-airlock scores 35 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### Is the mcp-airlock server still maintained?

mcp-airlock is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the mcp-airlock server under?

mcp-airlock declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the mcp-airlock server?

VerifyMCP ran 8 checks on mcp-airlock, covering Known CVEs, Install scripts, Dependency health, Source repository and 4 more. 6 items could not be completed, a gap on our side rather than a finding about mcp-airlock: Malware scan, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/mcp-airlock/
- Socket report: https://socket.dev/pypi/package/mcp-airlock
- Repository: https://github.com/Shalimov04/mcp-airlock
- Changelog RSS feed: https://verifymcp.io/servers/shalimov04-mcp-airlock/mcp-airlock.xml
- Changelog JSON feed: https://verifymcp.io/servers/shalimov04-mcp-airlock/mcp-airlock/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/shalimov04-mcp-airlock/mcp-airlock.json
- HTML version of this page: https://verifymcp.io/servers/shalimov04-mcp-airlock/mcp-airlock