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/yifanyifan897645/codescan-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/yifanyifan897645/codescan-mcp/codescan)<a href="https://agentmods.dev/mcp/yifanyifan897645/codescan-mcp/codescan"><img src="https://agentmods.dev/badge/mcp/yifanyifan897645/codescan-mcp/codescan/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/yifanyifan897645/codescan-mcp/codescan"><img src="https://agentmods.dev/badge/mcp/yifanyifan897645/codescan-mcp/codescan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
codescan 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
{
"codescan": {
"command": "npx",
"args": [
"-y",
"codescan-mcp"
],
"env": {}
}
}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 · 10 lines scan A fb0debbabb30
codescan is an MCP server published in the GitHub repository yifanyifan897645/codescan-mcp (0 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
paparats-mcp
Local-first semantic code search across all your repos. Private context for AI coding assistants. Runs locally from the @paparats/cli npm package.
idencify
Whole-repo code graph for AI agents: impact analysis, dead code, cycles, semantic search — 14 tools. Remote server at mcp.idencify.com.
wechat-devtools-mcp
A local service that lets an AI assistant control WeChat Developer Tools through the Model Context Protocol (MCP), a standard way for assistants to call external tools. It runs from the wechat-devtools-mcp Python package.
telegram-dev
MCP server "telegram-dev" as configured in leshchenko1979/fast-mcp-telegram. Runs src.server with python3.
transcriptor-mcp
MCP server "transcriptor-mcp" as configured in samson-art/transcriptor-mcp. Runs in Docker (docker.io/artsamsonov/transcriptor-mcp:1.5.9).
code-graph
Index any TypeScript/React repo (incl. monorepos) into a queryable code graph — npx CLI, HTTP/WS server, and MCP server. Reverse queries (who-renders/who-calls/find-references), blast-radius, cycles, dead-code orphans, symbol signatures, external (nodemo. Runs locally from the code-graph-indexer npm package.