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.
npx agentmods add mcp/pranavvr/repo_explainer_mcp/github-repo-explainer-mcpgit clone --depth 1 https://github.com/Pranavvr/Repo_Explainer_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/pranavvr/repo_explainer_mcp/github-repo-explainer-mcp)<a href="https://agentmods.dev/mcp/pranavvr/repo_explainer_mcp/github-repo-explainer-mcp"><img src="https://agentmods.dev/badge/mcp/pranavvr/repo_explainer_mcp/github-repo-explainer-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
github-repo-explainer-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 6d 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 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.
- 6d ago First seen · 8 lines scan A 70ffd6e3dbb9
github-repo-explainer-mcp is an MCP server published in the GitHub repository Pranavvr/Repo_Explainer_MCP (0 stars, last pushed 5mo 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-31.
Other mcp servers, from other repositories
gitee-mcp
MCP server "gitee-mcp" as configured in sandraschi/gitee-mcp. Runs locally from the gitee-mcp Python package.
gitpin
Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index. Runs locally from the gitpin npm package. Needs 1 environment variable to run.
github
Lets the agent work with GitHub: search code, read and create issues and pull requests, and manage repositories through the GitHub API. Runs locally from the @modelcontextprotocol/server-github npm package. Needs 1 environment variable to run.
gitlab-mcp
一个用于Cursor IDE的GitLab操作服务. Runs locally from the gitlab-mcp Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.