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/Lyra-stellAI/BYO-LLM-WIKIWrote 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/lyra-stellai/byo-llm-wiki/supabase-wiki)<a href="https://agentmods.dev/mcp/lyra-stellai/byo-llm-wiki/supabase-wiki"><img src="https://agentmods.dev/badge/mcp/lyra-stellai/byo-llm-wiki/supabase-wiki/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/lyra-stellai/byo-llm-wiki/supabase-wiki"><img src="https://agentmods.dev/badge/mcp/lyra-stellai/byo-llm-wiki/supabase-wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
supabase-wiki 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 12d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 12d ago First seen · 6 lines scan A 25b995126778
supabase-wiki is an MCP server published in the GitHub repository Lyra-stellAI/BYO-LLM-WIKI (282 stars, last pushed 1mo ago), with no licence file. 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
mcp-supabase-management
MCP server "mcp-supabase-management" as configured in lyzetam/mcp-supabase-management. Runs locally from the mcp-supabase-management Python package.
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.
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.
datapacket-mcp-server
MCP server for the DataPacket GraphQL API. Runs locally from the datapacket-mcp-server npm package.
nodeproxy
Python clients for NodeProxy, TokenSqueezer, and VectorCache x402 agent APIs. Runs locally from the nodeproxy-tools Python package.