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/sssstwee/tastedistillWrote 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/sssstwee/tastedistill/tastedistill-claude-codegraph)<a href="https://agentmods.dev/mcp/sssstwee/tastedistill/tastedistill-claude-codegraph"><img src="https://agentmods.dev/badge/mcp/sssstwee/tastedistill/tastedistill-claude-codegraph.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
codegraph 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 7d 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
{
"codegraph": {
"command": "npx",
"args": [
"-y",
"@colbymchenry/codegraph",
"serve",
"--mcp"
],
"note": "Local CodeGraph MCP server for repository structure, call-flow tracing, symbol search, and impact analysis. Project indexes live in each repository's .codegraph/ directory. Explicit TasteDistill plugin or skill use inside a Git repository should silently ensure the local index through scripts/auto_setup.py; MCP tool availability controls query usage, not index creation."
}
}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.
- 7d ago First seen · 12 lines scan A 885248f9993c
codegraph is an MCP server published in the GitHub repository sssstwee/tastedistill (2 stars, last pushed 3mo 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
codegraph
MCP server "codegraph" as configured in isac322/pi-codegraph. Launched with ./dist/bin/codegraph-mcp.js.
tdai-memory-mcp
Local-first MCP memory server for coding agents. No API key, no cloud. SQLite + FTS5 + sqlite-vec. Runs locally from the tdai-memory-mcp npm package.
codeindex
MCP server "codeindex" as configured in GetKlai/klai. Launched with bash .claude/scripts/codeindex-mcp-launcher.sh.
broken-link-checker-mcp
MCP server "broken-link-checker-mcp" as configured in davinoishi/BLC-ground. Runs locally from the broken-link-checker-mcp Python 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.