Mcp Blast Radius vs Repo Graph — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mcp Blast Radius vs Repo Graph
In-depth architectural comparison of the Mcp Blast Radius and Repo Graph MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Mcp Blast Radius
Biology & Bioinformatics · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Repo Graph
Biology & Bioinformatics · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mcp Blast Radius if you need specialized Biology & Bioinformatics tools running via a local process. Choose Repo Graph if your workspace requires Biology & Bioinformatics integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Mcp Blast Radius when:
You need dedicated capabilities in the Biology & Bioinformatics domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: AOS_VALIDATOR_TARGET_DIR, AOS_VALIDATOR_MCP_LOG, AOS_VALIDATOR_CALLER.
MCP Blast-Radius Auditor — static blast radius extraction and AOS manifest.json divergence gate (Oracle / Permitted / Prohibited). Stdio MCP (mcp-blast-radius) plus CI blocking gate (mcp-blast-radius-gate). Install: pip install mcp-blast-radius==0.2.0 · PyPI
Structural graph map of any codebase for AI coding assistants. Scans entities, relationships, and feature flows across 13 languages so LLMs navigate by structure instead of grepping through everything.
Category & Scope
Tools & Capabilities Breakdown
Mcp Blast Radius Tools (2)
aos_compliance_validate
scan one MCP server directory (`target_dir` required; `tool_id` optional label)
aos_compliance_self_test
wiring smoke test
Repo Graph Tools (6)
orient
The first call on a repo: node/edge counts, detected kinds, entry points, and a **blind-spots** note flagging which languages/edges are under-linked (so you grep those deliberately). `seed=<node>` → scoped map; `full=true` → whole-repo dense map
find
Turn any text into the ranked nodes that matter — a symbol/keyword, or a pasted stacktrace / failing-test id / diff (resolved to the code it implicates). `expand=true` fans out to the surrounding neighbourhood. Every row carries `path:line
impact
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Mcp Blast Radius is categorized under Biology & Bioinformatics and uses a local stdio subprocess. In contrast, Repo Graph belongs to Biology & Bioinformatics using local stdio subprocess. Select Mcp Blast Radius when you need capabilities focused on biology & bioinformatics and Repo Graph when you require tools for biology & bioinformatics.
Blast radius: what a change affects (`forward`) or depends on / is used by (`backward`), as a ranked, located closure — each row with the edge `via` reason and a `⊘` when the engine finds it unreachable (likely dead). Pass several nodes for a whole-diff radius
trace
One arg: a feature end-to-end across the stack, each hop labelled with its mechanism (call / HTTP / queue / event) and cross-service hops marked. Two args: the shortest path between two nodes
read
A node's exact source, sliced from its file by the graph's line span, plus a `context:` footer (HTTP method, cross-stack callers, covering tests, governing docs). Comma-separate to batch-read a ranked set
refresh
Rebuild the graph (incremental by default — only changed files re-parse). `repo_path` retargets a different path or git URL; `full=true` forces a clean reparse. Routine edits are auto-picked-up by the file watcher