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/SiTouhemi/BackendgenWrote 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/sitouhemi/backendgen/mcp-distribution-backendgen)<a href="https://agentmods.dev/mcp/sitouhemi/backendgen/mcp-distribution-backendgen"><img src="https://agentmods.dev/badge/mcp/sitouhemi/backendgen/mcp-distribution-backendgen/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/sitouhemi/backendgen/mcp-distribution-backendgen"><img src="https://agentmods.dev/badge/mcp/sitouhemi/backendgen/mcp-distribution-backendgen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
backendgen 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
{
"backendgen": {
"command": "npx",
"args": [
"-y",
"@2hemi/backendgen-mcp"
],
"env": {
"BACKENDGEN_ALLOWED_ROOTS": ""
}
}
}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 · 12 lines scan A 81b3927b7e8f
backendgen is an MCP server published in the GitHub repository SiTouhemi/Backendgen (0 stars, last pushed 1mo ago), licensed Apache-2.0. 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
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.
age_mcp_server
Apache AGE MCP Server. Runs locally from the age_mcp_server Python package.
cloud
The agent-native cloud: database, functions, AI, storage, computers. 50 tools, one API key. Remote server at api.scalix.world.
mcpbridge
MCP server "mcpbridge" as configured in manulthanura/MCPBridge. Runs /absolute/path/to/mcpbridge/dist/main.js with node. Needs 3 environment variables to run.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.