Supabase (theinfosecguy) MCP Server
mcp-server-supabase
npm
v0.0.1-security
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Security research canary — not for production use. Part of an authorized bug bounty research project.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 13 = 87. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −5 | publisher verification (unlocatable) — no provenance and no public repository to inspect |
| −8 | inspection depth (metadata) — how much of the target the scan could see |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
- The implementation source was not read — this reflects registry metadata only. Add --online to fetch and analyze the published package source.
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.0.1-security latest |
B 87/100 | 0 | 1.13.0 | 2026-09-07 |
v0.0.2 |
A 98/100 | 1 | 1.12.1 | 2026-08-20 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-server-supabase --onlineOther implementations of Supabase 11
Independent packages implementing the same tool, scanned with the same engine. Compare all 12 side by side →
MCP utilities
Supabase’s official MCP server: manage projects, run SQL and inspect your database.
MCP server for Supabase CRUD operations
MCP server for Supabase — 31 tools for database CRUD, storage, auth admin, project management, edge functions, and secrets via REST + Management APIs
Community Supabase MCP server that enables Cursor and Windsurf to end-to-end manage your Supabase project, execute SQL queries, and more.
MCP server for interacting with Supabase
More in Learning & Documentation
stdio compatibility bridge for the hosted AgentMail MCP server
MCP server for Alfa documentation retrieval
MCP server providing Alpine.js documentation and reference
Search the official Astro framework documentation.
MCP server providing ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Aurais Research Reader as an MCP server — paste a paper or article, get a structured read with verbatim-verified quotes + a signed Vorion proof chain (via @vorionsys/aurais-core).