Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PatchLabs

REMOTE · API.PATCHLABS.DEV · 2 COMPONENTS

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

76 Trust /100

Last scanned (23 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 75

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.patchlabs.dev/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.patchlabs.dev CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 9 Nov 2026 9 May 2027 RSA 2048 SHA256-RSA 4446796bae6d8c7f874e05f97743255
SANs: api.patchlabs.dev
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.patchlabs.dev. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
patchlabs.dev. DS published 33313 13 Verified
api.patchlabs.dev. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'; base-uri 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.patchlabs.dev/mcp/public Verified 200
http (plaintext) http://api.patchlabs.dev/mcp/public HTTPS enforced 301 https://api.patchlabs.dev/mcp/public
MCP tools · 4 exposed · ~442 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_check ~142

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.

NameTypeReqDescription
check_idstringyesThe check id that start_check or run_check returned

No output schema declared.

No examples provided.

headers_check ~65

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.

NameTypeReqDescription
urlstringyesA public site, e.g. https://app.example.com

No output schema declared.

No examples provided.

rls_check ~113

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.

NameTypeReqDescription
repostringyesPublic GitHub repo, e.g. owner/name or https://github.com/owner/name

No output schema declared.

No examples provided.

start_check ~122

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.

NameTypeReqDescription
emailstringyesWhere the report goes
repostringyesPublic GitHub repo, e.g. owner/name or https://github.com/owner/name

No output schema declared.

No examples provided.

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.

remote · api.patchlabs.dev

# add to Claude Code
claude mcp add --transport http dev-patchlabs-patchlabs 'https://api.patchlabs.dev/mcp/public'
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.