updated 2026-10-11 04:08 UTC

Supabase MCP Server

Repository Website by supabase

Connect Supabase to your AI assistants

MCP Servers TypeScript Listed Apache-2.0

Is Supabase MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.5 / 10
Provenance Attested
Signed commits 88%
Last push 2d ago
Advisories None known
Compare Supabase MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Supabase MCP Server scores 88.1/100 (Grade A), ranked #40 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.5/10; 88% of recent commits are signed; no published advisory affects its latest release (@supabase/mcp-server-supabase); last pushed 2026-10-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Supabase MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Supabase MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/supabase/mcp, Apache-2.0, last pushed 2026-10-09. 88% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.5/10 (scanned Oct 8, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection4
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies10
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 4
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 10
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

  4. What you install today No known advisories

    Latest release checked: @supabase/mcp-server-supabase 0.13.0. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-09-03 Package provenance attestation detected

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Supabase MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Supabase MCP Server compares in MCP Servers

  1. #6 SearXNG Search 89.0 +0.9
  2. #7 KiCad MCP Pro 88.9 +0.8
  3. #8 Supabase MCP Server 88.1 this agent
  4. #9 Cap Js MCP Server 88.0 −0.1
  5. #10 Mongodb MCP Server 88.0 −0.1

Bars show each HVTrust score; the tick marks Supabase MCP Server’s 88.1.

Where the 88.1 comes from

HVTrust dimensions vs the MCP Servers average

88.1 / 100 · 100.0% confidence

Supabase MCP Server MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
20.0 / 25
9.6 above avg 10.4
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.5 above avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
14.0 / 17
1.8 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
16.7 / 20
4.5 above avg 12.2
AdoptionLog-scaled stars · package downloads
14.8 / 20
7.4 above avg 7.4

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.
Compare with Mobile MCP Get email alerts for Supabase MCP Server View MCP Servers Report missing data
72.9
Activity sub-score · out of 100
#8
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 04:08 UTC · Repo last pushed 2 days ago

Rank Trend

2026-09-29 2026-10-11

Activity & Reach

Stars
2.9k
Forks
415
Last Push
2026-10-09
2 days ago
Commits (4 wk)
15
Downloads (7d)
67,881
npm
HN mentions (30d)
—
Open Issues
75
Rank Change
=
was #40

Analysis

Activity Inputs

72.9 / 100
StarsRepository reach
20.8 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
15.0 / 25
CommunityFork signal
12.2 / 20

Common questions about Supabase MCP Server

Public supply-chain signals for Supabase MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Supabase MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Supabase MCP Server publish package provenance?
Yes. Supabase MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Supabase MCP Server have an OpenSSF Scorecard?
Supabase MCP Server has an OpenSSF Scorecard score of 6.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Supabase MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does Supabase MCP Server use?
Supabase MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Supabase MCP Server's commits signed?
88% of the last 100 commits to Supabase MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Supabase MCP Server head-to-head

Supabase MCP Server vs Mobile MCP → Supabase MCP Server vs Playwright MCP → Supabase MCP Server vs Codebase Memory MCP →

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Supabase MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Supabase MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-03
Provenance Added
Package provenance attestation detected

Maintain Supabase MCP Server?

For maintainers

HVTrust scores Supabase MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 6HVTrust 1Grade 1Provenance 1
2026-09-03
Provenance Added
Package provenance attestation detected
2026-09-03
Grade Changed
Trust grade B → A
2026-09-03
Rank Moved
Rank rose 164 spots (#183 → #19)
2026-09-03
HVTrust Changed
HVTrust up 17.4pts (71.4 → 88.8)
2026-08-31
Rank Moved
Rank dropped 22 spots (#158 → #180)
2026-08-29
Rank Moved
Rank dropped 11 spots (#154 → #165)
2026-08-26
Rank Moved
Rank dropped 16 spots (#132 → #148)
2026-08-17
Rank Moved
Rank rose 12 spots (#138 → #126)
2026-08-08
Rank Moved
Rank dropped 12 spots (#112 → #124)
GitHub → Website → npm: @supabase/mcp-server-supabase

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 88.1 Grade A
Markdown:
[![HVTrust](https://hvtracker.net/badge/supabase-mcp-server.svg)](https://hvtracker.net/agents/supabase-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/supabase-mcp-server"><img src="https://hvtracker.net/badge/supabase-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON