supabase-community/supabase-mcp

No risky behavior detected.

Outbound network 3

Environment variables (config / keys) 2

AI review

This is an official Supabase MCP server extension with no hidden instructions, prompt injection, or data exfiltration mechanisms. The network calls and environment variable access are legitimate for the stated purpose of connecting to Supabase APIs and authenticating users.

low Legitimate API calls to Supabase services — The fetch() calls in release.yml, server.ts, and graphql.ts are expected network operations for publishing releases and communicating with Supabase APIs. No suspicious or unauthorized endpoints detected.
low Environment variable access for authentication — SUPABASE_ACCESS_TOKEN is read from environment variables, which is standard and necessary for authenticating with Supabase services. The CI check in vitest.setup.ts is a common testing pattern.

Model: deepseek-chat

Static findings

Outbound network · Makes outbound network requests

info .github/workflows/release.yml:159 fetch(url)

low packages/mcp-server-postgrest/src/server.ts:55 const response = await fetch(ensureTrailingSlash(apiUrl), {

low packages/mcp-server-supabase/src/content-api/graphql.ts:164 const response = await fetch(url, {

Environment variables (config / keys) · Reads environment variables (config / API keys)

low packages/mcp-server-supabase/src/transports/stdio.ts:51 const accessToken = cliAccessToken ?? process.env.SUPABASE_ACCESS_TOKEN;

low packages/mcp-server-supabase/vitest.setup.ts:5 if (!process.env.CI) {

Scanning every extension your team installs?

Pro & Team add monitoring, private scans, and a CI gate for unsafe extensions.

MCPVet is a heuristic aid, not a security guarantee. A clean grade does not prove an extension is safe; always review code and instructions you don't trust.