Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/node2flow-th/supabase-mcp-communityWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/node2flow-th/supabase-mcp-community/supabase-mcp)<a href="https://agentmods.dev/mcp/node2flow-th/supabase-mcp-community/supabase-mcp"><img src="https://agentmods.dev/badge/mcp/node2flow-th/supabase-mcp-community/supabase-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/node2flow-th/supabase-mcp-community/supabase-mcp"><img src="https://agentmods.dev/badge/mcp/node2flow-th/supabase-mcp-community/supabase-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
supabase-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{ "supabase-mcp": { "command": "npx", "args": [ "-y", "@node2flow/supabase-mcp" ] } }
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A d0543ebc7109
supabase-mcp is an MCP server published in the GitHub repository node2flow-th/supabase-mcp-community (0 stars, last pushed 8mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
postgrest-mcp
MCP server for PostgREST — 10 tools for CRUD operations, filtering, resource embedding, and RPC on PostgreSQL databases via REST API. Runs locally from the @node2flow/postgrest-mcp npm package.
supabase
Supabase CLI. Runs locally from the supabase npm package.
mcp
MCP server for Run402 — full-stack backend infrastructure for AI agents: Postgres, auth, storage, serverless functions and atomic deploys. Paid with x402/MPP. Includes $0.03 image generation. Runs locally from the run402-mcp npm package. Needs 2 environment variables to run.
dataverse
73 tools for Microsoft Dataverse: CRUD, FetchXML, metadata, audit, batch, role privileges and more. Runs locally from the mcp-dataverse npm package. Needs 2 environment variables to run.
supabase
Lets the agent manage Supabase projects: inspect tables, run SQL, handle migrations and read logs. Runs locally from the @supabase/mcp-server-supabase npm package. Needs 1 environment variable to run.
database-mcp-mysql
MCP server for MySQL. Read-only by default, row caps, statement timeouts, secrets never logged. Runs locally from the @database-mcp/mysql npm package. Needs 4 environment variables to run.