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/raysonmeng/agent-bridgeWrote 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/raysonmeng/agent-bridge/code-review-graph)<a href="https://agentmods.dev/mcp/raysonmeng/agent-bridge/code-review-graph"><img src="https://agentmods.dev/badge/mcp/raysonmeng/agent-bridge/code-review-graph.svg" alt="Measured on agentmods" height="20"></a>- Socket warn
Grade A, and why
code-review-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 yesterday.
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.
This is a copy
92% identical to code-review-graph — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"code-review-graph": {
"command": "uvx",
"args": [
"code-review-graph",
"serve"
],
"type": "stdio"
}
}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.
- yesterday First seen · 10 lines scan A 62b3f9e9de80
code-review-graph is an MCP server published in the GitHub repository raysonmeng/agent-bridge (330 stars, last pushed today), 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. It is 92% identical to code-review-graph, differing in 3 lines, and is treated as a copy.
Other mcp servers, from other repositories
otito
Deterministic local repository context, impact analysis, and merge-readiness evidence for AI agents. Runs locally from the @bashbop/otito npm package.
memorywhale
MCP server "memorywhale" as configured in wuisabel-gif/MemWhale. Launched with mw-mcp.
acr
ACRCms is an open source Python web content management system based on Turbogears and libacr. Runs locally from the acr Python package.
audit
Score any public GitHub repo 0-100 against the commit.show audit rubric. Runs locally from the commitshow-mcp npm package.
codex-channels-local
MCP server "codex-channels-local" as configured in cafitac/codex-channels. Runs ./packages/cli/dist/index.js with node. Needs 2 environment variables to run.
src-mcp
MCP server for semantic code search and codebase analysis — Treesitter parsing, AST extraction, and embedding-based indexing for any LLM that supports MCP. Runs locally from the src-mcp npm package.