Skills/npm/mcp-server-supabase

mcp-server-supabase@0.19.0

VERIFIED· not started

Publisher claims: "MCP server for interacting with Supabase" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher supabase · publishing for 686 daysInstalls 869KLast detonated 34 min ago
$claude mcp add mcp-server-supabase -- npx -y @supabase/mcp-server-supabase
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
SUPABASE_ACCESS_TOKEN or --access-tokenConfiguration, not credentials: SUPABASE_CONTENT_API_URL
Where it talks to
supabase.com, supabase.co, supabase.green (its own)
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for SUPABASE_ACCESS_TOKEN and talks to supabase.com, supabase.co, supabase.green. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets SUPABASE_ACCESS_TOKEN=supabase.com -- npx -y @supabase/mcp-server-supabase

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

What changed since 0.18.0

vet-skills diff mcp-server-supabase 0.18.0 0.19.0

In the sandbox, this version reached for nothing 0.18.0 did not. Compared from the two recorded runs, not from source.

0.18.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 10 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
10sprocessdependency install exit 1 · npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /tmp/ks-detonate-YQ2ZJc/task/home/.npm/_logs/2026-11-20T14_23_26_386Z-debug-0.log
10sclaimednot started: dependency install failed (exit 1); the server itself was not observed
10sprocessscript backend runs setup only
10sprocessno install scripts to re-run

Static findings

MEDIUM
File type combined with upload actiondist/chunk-C4YUF27U.cjs:1 · File type combined with upload action — agent may exfiltrate local data files…y:update":"tsx scripts/registry/update-version.ts && biome format --write server.json","registry:login":"scripts/registry/login.sh","registry:publish":"mcp-publisher publish",test:"vitest","test:unit":"vitest --project unit","test:e2e":"vi…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
MCP server using network transport (SSE/HTTP)dist/index.d.ts:189 · MCP server using network transport (SSE/HTTP) — data sent over networkdeclare function createSupabaseMcpHandler(options: SupabaseMcpServerOptions): _modelcontextprotocol_server.McpHttpHandler;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)dist/chunk-6DARTJRP.js:1 · MCP server using network transport (SSE/HTTP) — data sent over networkvar u={name:"@supabase/mcp-server-supabase",mcpName:"com.supabase/mcp",version:"0.19.0",description:"MCP server for interacting with Supabase",license:"Apache-2.0",repository:{type:"git",url:"https://github.com/supabase/mcp.git"},type:"modu…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)dist/chunk-C4YUF27U.cjs:1 · MCP server using network transport (SSE/HTTP) — data sent over network…...args)); lastAccessLHS = undefined; } } return value; }var u={name:"@supabase/mcp-server-supabase",mcpName:"com.supabase/mcp",version:"0.19.0",description:"MCP server for interacting with Supabase",license:"Apache-2.0",repository:{type:"…Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

Cost to the agent

Instructions loaded
≈52 tok
1 file · 24 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

Not checked against OSV yet; the weekly check has not reached this version.