# PatchLabs (remote · api.patchlabs.dev)

Finds personal-data leaks in Supabase/Lovable apps: free RLS and headers checks, proven fixes.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.patchlabs.dev`: 79/100, [markdown](https://verifymcp.io/servers/dev-patchlabs-patchlabs/api.md), [page](https://verifymcp.io/servers/dev-patchlabs-patchlabs/api)
- remote · `api.patchlabs.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/dev-patchlabs-patchlabs/mcp-public.md), [page](https://verifymcp.io/servers/dev-patchlabs-patchlabs/mcp-public)

## Channel facts

- Endpoint: `https://api.patchlabs.dev/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 521 tokens (~130/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.

## Install

### How do I install the PatchLabs MCP server?

PatchLabs is a hosted endpoint at https://api.patchlabs.dev/mcp/public, so there is nothing to install locally. 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 --transport http dev-patchlabs-patchlabs 'https://api.patchlabs.dev/mcp/public'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-patchlabs-patchlabs": {
      "url": "https://api.patchlabs.dev/mcp/public"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-patchlabs-patchlabs": {
      "type": "http",
      "url": "https://api.patchlabs.dev/mcp/public"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-patchlabs-patchlabs]
url = "https://api.patchlabs.dev/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-patchlabs-patchlabs": {
      "type": "remote",
      "url": "https://api.patchlabs.dev/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-patchlabs-patchlabs --url 'https://api.patchlabs.dev/mcp/public' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-patchlabs-patchlabs:
    url: "https://api.patchlabs.dev/mcp/public"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-patchlabs-patchlabs": {
      "Transport": "http",
      "Url": "https://api.patchlabs.dev/mcp/public"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-patchlabs-patchlabs -t streamable-http -u 'https://api.patchlabs.dev/mcp/public'
```

### Other

```json
{
  "mcpServers": {
    "dev-patchlabs-patchlabs": {
      "type": "http",
      "url": "https://api.patchlabs.dev/mcp/public"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-21 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-20 (score 75)

First indexed and scored.

## MCP tools (4)

### `rls_check` (~113 tokens)

Static RLS check

Free, no sign-up. Reads a public GitHub repo's supabase/migrations and lists row-level-security mistakes that could let strangers or other users read personal data (findings PL-001..PL-008 and PL-014, each with a fix). Static analysis only: it never connects to the live app or database. Suited to Supabase, Lovable and Bolt repos.

Input parameters:

- `repo` (string, required): Public GitHub repo, e.g. owner/name or https://github.com/owner/name

### `headers_check` (~65 tokens)

Security headers check

Grade a public site's HTTPS, TLS certificate, security headers and cookie flags from one load of its home page (no sign-up). Returns findings PL-027..PL-036 with fixes.

Input parameters:

- `url` (string, required): A public site, e.g. https://app.example.com

### `start_check` (~122 tokens)

Request a full leak check

Request the full lab check: the database is rebuilt from the repo with fake rows, leaks are proven as each kind of user, and a tested fix is written. Creates a check and emails the report address; nothing runs until the repo owner proves ownership with a one-line file. Returns a check id and link. Only call when the user asks for the full check and gives their email.

Input parameters:

- `email` (string, required): Where the report goes
- `repo` (string, required): Public GitHub repo, e.g. owner/name or https://github.com/owner/name

### `get_check` (~142 tokens)

Get a check

Read one check by id. Read-only, safe to call again to poll. Returns status: awaiting_verification (includes the one-line file the repo owner must add, then nothing runs until they do), queued, running, done, no_leaks, needs_review or failed. When finished it also returns the summary (each finding with severity, CWE/OWASP and days open), the plain-English report (report_md) and the tested fix (fix_sql), plus the event timeline. Use after start_check or run_check; poll every minute or so while queued or running.

Input parameters:

- `check_id` (string, required): The check id that start_check or run_check returned

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-patchlabs-patchlabs/mcp-public#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 75

## Common questions

### What is the PatchLabs MCP server?

PatchLabs is an MCP server listed in the public MCP registry as dev.patchlabs/patchlabs. Finds personal-data leaks in Supabase/Lovable apps: free RLS and headers checks, proven fixes. This page covers its hosted endpoint (https://api.patchlabs.dev/mcp/public).

### Is the PatchLabs MCP server safe to use?

PatchLabs scores 76 out of 100 on VerifyMCP. 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 PatchLabs MCP server expose?

PatchLabs exposes 4 tools: rls_check, headers_check, start_check, get_check. Their descriptions and schemas cost roughly 442 tokens of context every time the server is loaded.

### Does the PatchLabs MCP server require authentication?

No. We connected to PatchLabs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PatchLabs MCP server still maintained?

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

### What did VerifyMCP test on the PatchLabs MCP server?

VerifyMCP ran 13 checks on PatchLabs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.patchlabs.dev/mcp/public
- Repository: https://github.com/manra399/patchlabs
- Website: https://patchlabs.dev/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-patchlabs-patchlabs/mcp-public.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-patchlabs-patchlabs/mcp-public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-patchlabs-patchlabs/mcp-public.json
- HTML version of this page: https://verifymcp.io/servers/dev-patchlabs-patchlabs/mcp-public
