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/vibestackdev/vibe-stackWrote 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/vibestackdev/vibe-stack/supabase)<a href="https://agentmods.dev/mcp/vibestackdev/vibe-stack/supabase"><img src="https://agentmods.dev/badge/mcp/vibestackdev/vibe-stack/supabase.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
supabase 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 yesterday.
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": {
"command": "npx",
"args": [
"-y",
"@supabase/mcp-server-supabase@latest",
"--read-only"
],
"env": {
"SUPABASE_ACCESS_TOKEN": "<YOUR_SUPABASE_PAT>"
}
}
}What else mcp.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- yesterday First seen · 13 lines scan A 489c8f2df32d
supabase is an MCP server published in the GitHub repository vibestackdev/vibe-stack (8 stars, last pushed yesterday), 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-09-06.
Other mcp servers, from other repositories
supabase
Supabase CLI. Runs locally from the supabase npm package.
supabase
MCP server "supabase", hosted remotely at localhost, as configured in guillermoscript/lms-front.
dbhub
Minimal, token-efficient Database MCP Server for PostgreSQL, MySQL, SQL Server, SQLite, MariaDB. Runs locally from the @bytebase/dbhub npm package.
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.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.
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.