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.
npx agentmods add mcp/node2flow-th/supabase-mcp-community/supabase-mcpgit 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.svg" alt="Measured on agentmods" 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 3d 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.
- 3d 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 6mo 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
mcp
Provision Postgres databases + webhooks from AI coding agents in one HTTP call. Runs locally from the @instanode/mcp npm package. Needs 2 environment variables to run.
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.
airtable-mcp
MCP server for Airtable API — manage records, bases, tables, fields, and webhooks through 18 tools. Runs locally from the @node2flow/airtable-mcp npm package.
21st
MCP server "21st", hosted remotely at 21st.dev, as configured in 21st-dev/magic-mcp.
mako-ai
Agentmako is a local project intelligence CLI and MCP server for codebases and databases, with repo-aware indexing, schema snapshots, and secure live database connectivity. Runs locally from the agentmako npm package.
astravue-mcp
Manage projects, tasks, time tracking, and team collaboration through natural language. Remote server at api.astravue.com.