MCP server official
Risk level
medium
45/100

Supabase MCP Server ↗

Supabase MCP Server is an officially published MCP server from Supabase. Anomity scores its risk at 45 out of 100 (medium). It matches 1 dangerous capability combination.

database:read database:write network:outbound credentials:access

Analysis summary

Supabase MCP Server is an officially published MCP server from Supabase. Anomity scores its risk at 45 out of 100 (medium). It matches 1 dangerous capability combination.

Supabase's official server, giving an agent access to a project's Postgres database, auth configuration, storage, edge functions, and documentation. It is commonly used to let an assistant write and run queries against a real schema rather than guessing at table names.

Database read and write, credential access, and outbound network access is a combination that includes Anomity's database-exfiltration pattern: an agent that can query your tables and also reach the network can move data out in one step, whether deliberately or because a prompt injection told it to. Point it at a development branch by default. If it must touch production, use a role restricted to the tables the assistant genuinely needs and treat every query it writes as code to be reviewed.

Why this entry scored 45 out of 100

This profile starts at the catalog's neutral base of 50. Because the entry is officially published, trust adjusts the score by -40. Declared high-risk capabilities add +20 (capped at +30). It matches 1 dangerous capability combination, which contributes additional severity weight. The clamped result is 45, placing it in the medium band.

See the full scoring formula →

Findings

  • Published by the vendor Trust offset
    Contribution to score: -40
  • 2 high-risk capabilities: database:write, credentials:access Critical
    Contribution to score: +20
  • Database exfiltration risk (high) High
    Evidence
    Database read combined with outbound network can exfiltrate production data.
    Contribution to score: +15

Capabilities

Every capability the entry declares, with the security implication of each.

  • database:read Database read
    Reads from connected databases. Useful for query and analytics agents; risky when combined with outbound network.
  • database:write Database write
    Writes to connected databases. High-impact; combined with outbound network is treated as exfiltration-class.
  • network:outbound Outbound network
    Can make outbound network requests. Required for hosted model providers and remote APIs; also the path for data exfiltration if combined with read access.
  • credentials:access Credentials access
    Reads provider API keys, OAuth tokens, or other secrets from the host keychain or environment.

Dangerous combinations matched

Capability pairings that compound into well-known attack patterns.

  • Database exfiltration risk high
    Database read combined with outbound network can exfiltrate production data.
    database:read network:outbound