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/paullukic/coographWrote 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/paullukic/coograph/code-graph)<a href="https://agentmods.dev/mcp/paullukic/coograph/code-graph"><img src="https://agentmods.dev/badge/mcp/paullukic/coograph/code-graph/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/paullukic/coograph/code-graph"><img src="https://agentmods.dev/badge/mcp/paullukic/coograph/code-graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
Grade A, and why
code-graph 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.
What it actually says
{
"code-graph": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"-p",
">=3.10",
"--with-requirements",
".github/code-graph/requirements.txt",
".github/code-graph/server.py"
],
"env": {
"UV_NO_MANAGED_PYTHON": "1",
"UV_PYTHON_DOWNLOADS": "never"
}
}
}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 Changed · +4 lines 4a4f54d85a14
- 23d ago Changed · +3 lines 3ef96124f870
- 1mo ago Changed 4e72eb831c0a
- 1mo ago First seen · 11 lines scan A 1e27b9e1d80f
code-graph is an MCP server published in the GitHub repository paullukic/coograph (17 stars, last pushed 12d 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-30.
Other mcp servers, from other repositories
code-review-graph
Local-first knowledge graph for token-efficient code review through MCP and CLI. Runs locally from the code-review-graph Python package.
plantuml
MCP server for generating PlantUML diagrams. Runs locally from the plantuml-mcp-server npm package. Needs 1 environment variable to run.
shadcn
Add components to your apps. Runs locally from the shadcn npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm --prefix test/mcp run start-stdio.