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/kvnpetit/structured-repo-context-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/kvnpetit/structured-repo-context-mcp/src-mcp)<a href="https://agentmods.dev/mcp/kvnpetit/structured-repo-context-mcp/src-mcp"><img src="https://agentmods.dev/badge/mcp/kvnpetit/structured-repo-context-mcp/src-mcp/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/kvnpetit/structured-repo-context-mcp/src-mcp"><img src="https://agentmods.dev/badge/mcp/kvnpetit/structured-repo-context-mcp/src-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
src-mcp 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
{ "src-mcp": { "command": "npx", "args": [ "-y", "src-mcp" ] } }
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 7bf2a22479d9
src-mcp is an MCP server published in the GitHub repository kvnpetit/structured-repo-context-mcp (1 stars, last pushed 6mo ago), 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
codebugs
MCP server "codebugs" as configured in faxik/codebugs. Runs locally from the codebugs Python package.
tech-debt-mcp
MCP Server for analyzing technical debt across multiple programming languages. Runs locally from the tech-debt-mcp npm package.
react-devtools
MCP server "react-devtools" as configured in qbit-ai/qbit. Runs tools/react-devtools-bridge/dist/cli.js with node.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
servicenow
MCP server "servicenow" as configured in serac-labs/serac. Runs locally from the servicenow-mcp-stdio npm package.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Runs in Docker (ghcr.io/verivus-oss/sqry:4.8.16).