Supabase (cloud9-labs) MCP Server
@cloud9-labs/mcp-supabase
npm
v0.1.0
Published by @cloud9-labs — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server for Supabase API integration
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 3
high Sensitive-source and external-sink co-existMTC-FLOW-004
Tools that read sensitive data ([supabase_list_files, supabase_execute_sql]) and tools that can send data out ([supabase_upload_file]) are exposed together. An agent can move private data to the sink.
Evidence: sources [supabase_list_files, supabase_execute_sql] → sinks [supabase_upload_file]
Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.
Location: flow supabase_list_files → supabase_upload_file
medium Tool "supabase_delete_file" can modify the filesystemMTC-CAP-002
Tool "supabase_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool supabase_delete_file
low Mutating tool "supabase_delete_file" declares no destructiveHintMTC-CAP-005
Tool "supabase_delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool supabase_delete_file
Tools 12
Each tool and what it can reach — statically extracted from the published source.
supabase_delete_filewrites filessupabase_execute_sqlreads sensitive datasupabase_list_filesreads sensitive datasupabase_upload_filenetwork egresssupabase_deleteno sensitive capabilitysupabase_get_table_schemano sensitive capabilitysupabase_insertno sensitive capabilitysupabase_list_bucketsno sensitive capabilitysupabase_list_tablesno sensitive capabilitysupabase_queryno sensitive capability
Show 2 more tools ↓
supabase_rpcno sensitive capabilitysupabase_updateno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (12 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.0 latest |
A 92/100 | 3 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @cloud9-labs/mcp-supabase --onlineOther implementations of Supabase 11
Independent packages implementing the same tool, scanned with the same engine. Compare all 12 side by side →
MCP utilities
Supabase’s official MCP server: manage projects, run SQL and inspect your database.
MCP server for Supabase CRUD operations
MCP server for Supabase — 31 tools for database CRUD, storage, auth admin, project management, edge functions, and secrets via REST + Management APIs
Community Supabase MCP server that enables Cursor and Windsurf to end-to-end manage your Supabase project, execute SQL queries, and more.
MCP server for interacting with Supabase
More in Databases
Security scan results for the A5sql MCP server.
Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.
MCP server for Aiven cloud data platform - manage PostgreSQL, Kafka, and other services
MCP Server for All-Inkl.com hosting via KAS API
Structured aquarium, marine, terrarium and paludarium data for AI agents.
MCP server that gives your AI agent real vehicle data — specs, representative images, federal recalls, owner complaints, service bulletins, defect investigations, and OBD-II DTC reference — from the CarVector API.