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/guillermoscript/lms-frontWrote 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/guillermoscript/lms-front/supabase)<a href="https://agentmods.dev/mcp/guillermoscript/lms-front/supabase"><img src="https://agentmods.dev/badge/mcp/guillermoscript/lms-front/supabase/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/guillermoscript/lms-front/supabase"><img src="https://agentmods.dev/badge/mcp/guillermoscript/lms-front/supabase.svg" alt="Reviewed on agentmods" width="80" 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 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": {
"type": "http",
"url": "http://localhost:54321/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. 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.
- 1mo ago First seen · 6 lines scan A e73ab1c8ef0b
supabase is an MCP server published in the GitHub repository guillermoscript/lms-front (40 stars, last pushed today), 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-30.
Other mcp servers, from other repositories
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.
clerk
MCP server "clerk", hosted remotely at mcp.clerk.com, as configured in FloB95/qrcodly.
dataverse-mcp
An MCP server for interacting with Microsoft Dataverse environments during development. Runs locally from the dataverse-mcp Python package.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.
nocobase-mcp-server
MCP server for NocoBase — manage collections, UI schemas, flowPage blocks, and JS blocks via AI assistants like Claude. Runs locally from the @reroet/nocobase-mcp-server npm package.