registry / record

@supabase/mcp-server-supabase

npm / sealed 2026-06-16 / No. 36c39156

Does @supabase/mcp-server-supabase MCP work in Claude Code and Cursor? Throne executed @supabase/mcp-server-supabase mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: needs your API key. Is @supabase/mcp-server-supabase mcp safe? Static security scan: 1 finding(s) to review under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.

re-scan this server gate it in your CI

> throne registry @supabase/mcp-server-supabase sealed

This server runs. It just needs your API keythe server installs and starts, then exits asking for an API key, Please provide a personal access token (PAT) with the --access-token flag or set the SUPABASE_ACCESS_TOKEN environment variable

receiptsealed evidence

scan id: 36c391567b224b139f851b53266f4ae6
target: @supabase/mcp-server-supabase
sealed at: 2026-06-16 18:27:00Z
evidence hash: sha256:844914557dff658bc9a5cbb9e768886f9caa30cf266c78903d440662f338ddd5

01connectFAIL0ms

server never launched: server process exited with code 1 before the MCP handshake, stderr: Please provide a personal access token (PAT) with the --access-token flag or set the SUPABASE_ACCESS_TOKEN environment variable

02discoverSKIPPED0ms

not run, server never launched

03validate_schemasSKIPPED0ms

not run, server never launched

04smoke_test_toolsSKIPPED0ms

not run, server never launched

05error_handlingSKIPPED0ms

not run, server never launched

06streamingSKIPPED0ms

not run, server never launched

07resource_lifecycleSKIPPED0ms

not run, server never launched

08concurrent_callsSKIPPED0ms

not run, server never launched

09reconnectSKIPPED0ms

not run, server never launched

01connectFAIL0ms

server never launched: server process exited with code 1 before the MCP handshake, stderr: Please provide a personal access token (PAT) with the --access-token flag or set the SUPABASE_ACCESS_TOKEN environment variable

02discoverSKIPPED0ms

not run, server never launched

03validate_schemasSKIPPED0ms

not run, server never launched

04smoke_test_toolsSKIPPED0ms

not run, server never launched

05error_handlingSKIPPED0ms

not run, server never launched

06streamingSKIPPED0ms

not run, server never launched

07resource_lifecycleSKIPPED0ms

not run, server never launched

08concurrent_callsSKIPPED0ms

not run, server never launched

09reconnectSKIPPED0ms

not run, server never launched

chatgpt desktop calibratingemulation profile pending real-traffic captureCOMING SOON

SECURITY: REVIEW / 1 finding(s) / review recommended

LOWTHR-NET-05 / Hardcoded outbound endpoints

3 non-local endpoint host(s) referenced in code, verify each is expected for this server's purpose: ai-sdk.dev (package/dist/index.d.ts:884), api.supabase.com (package/dist/chunk-5PS6HETH.js:39), supabase.com (package/dist/chunk-P2KUVMMH.cjs:2)

package/dist/chunk-5PS6HETH.js:39

VERDICT: NEEDS YOUR API KEYSANDBOXED RUN, submitted server executed in a disposable microVM, compatibility not assessable: needs credentials: the server installs and starts, then exits asking for an API key, Please provide a personal access token (PAT) with the --access-token flag or set the SUPABASE_ACCESS_TOKEN environment variable / security: review, 1 finding(s), 0 highsealed by THRONE / No. 36c39156 / 2026-06-16

scopeattestation tuple

target: @supabase/mcp-server-supabase npm
engine: sandboxed
claude code: calibration: partial recorded=9,spec=0,assumed=9
cursor: calibration: partial recorded=11,spec=0,assumed=7
chatgpt desktop: calibration: unavailable recorded=0,spec=2,assumed=16
steps exercised: 18 of 18
test suite: v1.0.0
security ruleset: v1.0.0
sealed at: 2026-06-16 18:27:00Z
evidence hash: sha256:844914557dff658bc9a5cbb9e768886f9caa30cf266c78903d440662f338ddd5
valid until: 2026-09-14

executed in a disposable microVM, created for this scan and destroyed after it. nothing outlives a run.

maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.

this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.