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/aliyun/rds-supabase-mcpWrote 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/aliyun/rds-supabase-mcp/supabase-mcp-server)<a href="https://agentmods.dev/mcp/aliyun/rds-supabase-mcp/supabase-mcp-server"><img src="https://agentmods.dev/badge/mcp/aliyun/rds-supabase-mcp/supabase-mcp-server/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/aliyun/rds-supabase-mcp/supabase-mcp-server"><img src="https://agentmods.dev/badge/mcp/aliyun/rds-supabase-mcp/supabase-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
supabase-mcp-server 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 9d 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-server": { "command": "npx", "args": [ "-y", "@aliyun-rds/supabase-mcp-server" ] } }
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.
- 9d ago First seen · 9 lines scan A d725803d24c4
supabase-mcp-server is an MCP server published in the GitHub repository aliyun/rds-supabase-mcp (1 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-08-31.
Other mcp servers, from other repositories
mcp
MCP server for Appwrite: manage projects and their databases, auth, storage, functions, messaging, and sites, and search the official Appwrite documentation. Runs locally from the mcp-server-appwrite Python package.
convex
Client for the Convex Cloud. Runs locally from the convex npm package.
dataverse-mcp
An MCP server for interacting with Microsoft Dataverse environments during development. Runs locally from the dataverse-mcp Python package.
elastic-mcp
Model Context Protocol server for Elasticsearch (search, index inspection, cluster info; read-only by default with optional write tools). Runs locally from the elastic-mcp npm package.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.
mcp-supabase-management
MCP server "mcp-supabase-management" as configured in lyzetam/mcp-supabase-management. Runs locally from the mcp-supabase-management Python package.