Is Supabase MCP Server safe to use?

Supabase MCP Server has an HVTrust score of 71.1/100 (Grade B), ranked #124 of 1204 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Supabase MCP Server?

Supabase MCP Server scores 71.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 2.9k GitHub stars and is categorized under MCP Servers.

Supabase MCP Server

supabase/mcp

Connect Supabase to your AI assistants

MCP Servers TypeScript Grade B Listed Apache-2.0

71.1/100

Rank #124 of 1204

Compare Supabase MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-09 · 0d ago

Recent change

Rank +2

Is Supabase MCP Server safe? Supabase MCP Server scores 71.1/100 (Grade B), ranked #124 of 1204 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.5/10; 70% of recent commits are signed; last pushed 2026-08-09. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#20 AWS MCP Servers — 71.6 (B) → #21 Sentry MCP — 71.5 (B) → #23 Openzim MCP — 70.8 (B) → #24 Anytype MCP — 70.6 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-08-08

Rank Moved

Rank dropped 12 spots (#112 → #124)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, Postgres

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.5/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Supabase MCP Server View MCP Servers Report missing data

72.0

Activity sub-score · out of 100

#22

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 B 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 →

Activity & Reach

Stars

2.9k

Forks

389

Last Push

2026-08-09

today

Commits (4 wk)

13?

Downloads (7d)

64,805

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #124

Analysis

HVTrust Dimensions vs MCP Servers

71.1 / 100 · 100.0% confidence

Supabase MCP Server MCP Servers average (718 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.6 / 25

6.5 above avg 5.1

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.5 below avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

14.0 / 17

5.2 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

14.3 / 20

1.8 above avg 12.5

AdoptionLog-scaled stars · package downloads

14.7 / 20

9.2 above avg 5.5

Activity Inputs

72.0 / 100

StarsRepository reach

20.7 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

14.3 / 25

CommunityFork signal

12.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

6.5 / 10

OpenSSF Scorecard · scanned Aug 9, 2026

Signed Commits

70%

of last 100 commits verified

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

Is Supabase MCP Server safe?

Supabase MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Supabase MCP Server publish package provenance?

No published build provenance is currently detected for Supabase MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

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 1 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?

70% 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.

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.

Supabase

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-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, Postgres

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Postgres, Supabase

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

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

2026-08-08

Rank Moved

Rank dropped 12 spots (#112 → #124)

2026-08-07

Tool Surface Changed

Detected tool/plugin surface changed: extension-based → declared

2026-08-07

Provider Removed

Runtime surface shrank — no longer detected: Anthropic, Postgres

2026-07-13

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-07-13

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, Postgres, Supabase

2026-07-13

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-07-13

Activity Resumed

Activity resumed

2026-07-13

Grade Changed

Trust grade D → B

2026-07-13

Rank Moved

Rank rose 231 spots (#342 → #111)

2026-07-13

HVTrust Changed

HVTrust up 60.3pts (8.1 → 68.4)

2026-07-13

Activity Score Changed

Activity score up 66pts (0 → 66)

2026-07-12

Newly Listed

First tracked at rank #342

GitHub → npm: @supabase/mcp-server-supabase

Embed Badge Badge guide for maintainers →

For maintainers

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.2 · Raw JSON