# Airlock RLS (npm · airlock-rls-mcp)

Scan a deployed site for an exposed Supabase service_role key and audit Row Level Security.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `airlock-rls-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/mateuszingano-airlock-rls-mcp/airlock-rls-mcp.md), [page](https://verifymcp.io/servers/mateuszingano-airlock-rls-mcp/airlock-rls-mcp)

## Channel facts

- Registry: `npm`
- Package: `airlock-rls-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## 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-10-17.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 7 of 23 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 399 tokens (~199/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Airlock RLS MCP server?

Airlock RLS runs locally as an npm package, launched with npx -y airlock-rls-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mateuszingano-airlock-rls-mcp -- npx -y airlock-rls-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mateuszingano-airlock-rls-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "airlock-rls-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mateuszingano-airlock-rls-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "airlock-rls-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mateuszingano-airlock-rls-mcp -- npx -y airlock-rls-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mateuszingano-airlock-rls-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "airlock-rls-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mateuszingano-airlock-rls-mcp --command npx --arg -y --arg airlock-rls-mcp
```

### Hermes

```yaml
mcp_servers:
  mateuszingano-airlock-rls-mcp:
    command: "npx"
    args: ["-y", "airlock-rls-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mateuszingano-airlock-rls-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "airlock-rls-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mateuszingano-airlock-rls-mcp -t stdio -c npx -a -y airlock-rls-mcp
```

### Other

```json
{
  "mcpServers": {
    "mateuszingano-airlock-rls-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "airlock-rls-mcp"
      ]
    }
  }
}
```

## 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-10-16 (score 71, +1)

No change was recorded against any check on this day. Supply Chain Security went from 98 to 99.

### 2026-10-14 (score 70)

First indexed and scored.

## MCP tools (2)

### `scan_site_for_exposed_key` (~192 tokens)

Scan a DEPLOYED website's HTML and JavaScript bundles for an exposed Supabase service_role key (a service_role JWT or an sb_secret_... key). Needs only the public URL — no database, no credentials. A found key is a critical leak: it bypasses ALL Row Level Security, giving anyone who reads it full read/write to the database. Use this right after deploying a Supabase app, or whenever an AI-generated app might have bundled a secret into the frontend. Never prints the full key.

Input parameters:

- `max_scripts` (integer): How many JS bundles to read (default 50). If the site has more, the result says how many went unscanned instead of implying it looked at all.
- `site_url` (string, required): Public https URL of the deployed site to scan (e.g. https://myapp.com). Only public http(s) hosts are allowed.

### `audit_supabase_rls` (~207 tokens)

Audit a Supabase/Postgres database's Row Level Security. Fails when a table has RLS disabled, when a policy is permissive (USING (true) / WITH CHECK (true) or anything that reduces to always-true), when an anon or authenticated policy does not scope rows to the caller (tenant leak), and on exposed materialized views. Reads ONLY catalog metadata (pg_tables, pg_policies, grants, functions, views) — never your row data. A read-only connection string is enough.

Input parameters:

- `allow` (array): Policy names that are intentionally permissive (e.g. a public status page). Prefer the qualified form "table.policy".
- `db_url` (string, required): Postgres connection string for the project to audit (e.g. postgresql://... — get it from `supabase status` locally or your project's connection settings). A read-only role is enough.
- `schema` (string): Schema to audit (default: public).

## Diagnostics

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

## Score history

- 2026-10-17: 71
- 2026-10-16: 71
- 2026-10-15: 70
- 2026-10-14: 70

## Common questions

### What is the Airlock RLS MCP server?

Airlock RLS is an MCP server listed in the public MCP registry as io.github.mateuszingano/airlock-rls-mcp. Scan a deployed site for an exposed Supabase service_role key and audit Row Level Security. This page covers its npm package (airlock-rls-mcp).

### Is the Airlock RLS MCP server safe to use?

Airlock RLS scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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.

### What tools does the Airlock RLS MCP server expose?

Airlock RLS exposes 2 tools: scan_site_for_exposed_key, audit_supabase_rls. Their descriptions and schemas cost roughly 399 tokens of context every time the server is loaded.

### Is the Airlock RLS MCP server still maintained?

Airlock RLS is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Airlock RLS MCP server under?

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

## Links

- npm package: https://www.npmjs.com/package/airlock-rls-mcp
- Socket report: https://socket.dev/npm/package/airlock-rls-mcp
- Repository: https://github.com/mateuszingano/airlock-rls-mcp
- Website: https://shipsealed.com/?utm_source=mcp-registry&utm_medium=referral&utm_campaign=airlock-rls-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mateuszingano-airlock-rls-mcp/airlock-rls-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mateuszingano-airlock-rls-mcp/airlock-rls-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mateuszingano-airlock-rls-mcp/airlock-rls-mcp