io.github.James-Chahwan/repo-graph
PYPI · MCP-REPO-GRAPH
Structural graph map of any codebase so LLMs navigate by structure, not guesswork.
Available components
Last scanned (19 hours ago)
Scores higher than 59% of PyPI servers
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 30 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1691 tokens (~281/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 0.5.3 → 0.5.4 functional
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.5.2 → 0.5.3 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Provenance: unverified → fail ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/mcp-repo-graph@0.5.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 30 packages
| Packages resolved | 30 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find ~249
Turn any text into the ranked nodes that matter — the on-ramp to the graph. A symbol or keyword returns matching nodes; a pasted stacktrace / failing-test id / diff is resolved to the code it implicates and ranked by relevance. Set `expand=true` to fan out to the surrounding neighbourhood (spreading activation). Every row carries `path:line`, so `read` the top hits directly — no grep.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | Max chars in the result. 0 = no cap. |
| expand | boolean | – | Return the relevant neighbourhood (Personalized-PageRank ranked) around the matches, not just the matches themselves. Use to discover what surrounds a seed. |
| kind | string | – | Force the signal type: 'symbol', 'stacktrace', 'test', 'diff', or 'auto' (sniff the shape). |
| query | string | yes | What to locate: a symbol/keyword (e.g. `User`, `checkout`), OR a failure signal — paste a raw stacktrace, a failing-test id (path::test), or a unified diff / changed-file list. |
| top_k | integer | – | Max results. Default 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
impact ~438
Blast radius in one call: fan out from one or more nodes to everything they affect (forward) or depend on / are used by (backward), returned as a deduped, ranked, located closure. Ranking is co-change first where the repo has git history synced, then Personalized PageRank. Each row carries `path:line`, the edge `via` reason it's in scope, and a `⊘` when the engine finds it unreachable from any entry point (likely dead). Structural import/containment fan-out is excluded, so there's no noise. A large radius comes back as the top rows plus the areas and files the rest fall in; page with `offset`, drill in with `scope`. Depth-1 in both directions is a node's immediate neighbours. Pass several comma-separated nodes to assess a whole diff at once.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | Max chars in the result. 0 = no cap. |
| depth | integer | – | How many hops to fan out. Default 4. |
| direction | string | – | 'forward' (what it affects), 'backward' (what it depends on / who uses it), or 'both'. (Aliases: downstream=forward, upstream=backward.) |
| full | boolean | – | Every row, uncut. Can be thousands of rows on a hub node; prefer scope/offset. |
| live_only | boolean | – | Drop nodes not reachable from any entry point (likely-dead code). Default False = show all, marking dead ones ⊘. |
| nodes | string | yes | One or more node names/qnames, comma-separated. A diff touching N symbols is one call. |
| offset | integer | – | Skip the first N ranked rows to read the next page. The footer names the next offset. |
| scope | string | – | Only rows under this repo-relative path or project label. Use an area's scope from the footer to drill into it. |
| top_k | integer | – | Rows to return. 0 = the engine's overview: the top 25 rows plus the areas the rest fall in, so you can drill down with `scope`. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
orient ~209
Get the lay of the land — ALWAYS the first call on a codebase. With no arguments: a counts + entry-points overview plus a `blind spots` note flagging which (language, edge-kind) extractions are partial so you know where to fall back to grep. With `seed=<node>`: the dense structural map scoped to that node's neighbourhood. With `full=true`: the whole-repo dense map (the full context dump). Orient first, then `find` to jump to nodes, `impact` for blast radius, `trace` for flows.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | Max chars in the result. 0 = default cap (~50k for the full map, uncapped otherwise). |
| full | boolean | – | With no seed: return the whole-repo dense structural map instead of the counts overview. Ignored when seed is given. |
| seed | string | – | Optional node/qname to scope the map around (its activated neighbourhood). Blank = repo overview. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read ~229
Return the source code for one or more nodes, sliced from their files by the graph's line spans. Use after `find`/`impact` to read the exact code without grepping — comma-separate several node names to read the whole ranked set in a single call. Each node is a code block headed by its qname and `path:start-end`, plus a `context:` footer with structural facts the source alone doesn't show: HTTP method, cross-stack callers (or, on a WS / gRPC / GraphQL / tRPC client, the host it dials), covering tests, and intent/decision/constraint cells when present.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | Max chars in the result (shared across all nodes when several are given). 0 = no cap. |
| context_lines | integer | – | Lines of padding above and below the node's span. Default 0. |
| node | string | yes | Node name or qname to read. Comma-separate several (e.g. the top-ranked nodes from `find`/`impact`) to slice them all in one call. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
refresh ~194
(Re)build the structural graph with tree-sitter AST parsing across 20 languages, running the cross-stack resolvers (HTTP, gRPC, GraphQL, WebSocket, queues, events, CLI). Incremental by default — only changed files re-parse — so it's cheap to call after edits; set `full=true` to force a clean reparse. Accepts a local path or a git URL (cloned on demand). Call after a major refactor; routine edits are picked up automatically by the file watcher.
| Name | Type | Req | Description |
|---|---|---|---|
| full | boolean | – | Force a full reparse instead of reusing the per-file parse cache. Default False (incremental — only changed files re-parse, so this is cheap after edits). |
| repo_path | string | – | Path or git URL to (re)scan. Blank = the repo the server is serving. A different path/URL retargets the server at it. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
trace ~197
Follow the code across boundaries. One argument: trace a feature end-to-end — the ordered path from entry through the stack, each hop labelled with its mechanism (call / HTTP / queue / event / data), crossing service boundaries (frontend→backend). Two arguments: the shortest path between two specific nodes, hop by hop. This is where the graph beats reading many files — it knows the cross-stack links grep can't see.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | integer | – | Max chars in the result. 0 = no cap. |
| depth | integer | – | Max hops for the cross-stack feature trace. Default 6. |
| from_node | string | yes | A feature/keyword to trace end-to-end (one arg), OR the start node when tracing a path to `to_node`. |
| to_node | string | – | Optional target node. Given → shortest path from_node→to_node. Blank → trace `from_node` as a feature across the stack. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the io.github.James-Chahwan/repo-graph MCP server?
io.github.James-Chahwan/repo-graph runs locally as a PyPI package, launched with uvx mcp-repo-graph. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-repo-graph
claude mcp add james-chahwan-repo-graph -- uvx mcp-repo-graph
What is the io.github.James-Chahwan/repo-graph MCP server?
io.github.James-Chahwan/repo-graph is an MCP server listed in the public MCP registry as io.github.James-Chahwan/repo-graph. Structural graph map of any codebase so LLMs navigate by structure, not guesswork. This page covers its PyPI package (mcp-repo-graph).
Is the io.github.James-Chahwan/repo-graph MCP server safe to use?
io.github.James-Chahwan/repo-graph scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.James-Chahwan/repo-graph MCP server expose?
io.github.James-Chahwan/repo-graph exposes 6 tools: orient, find, impact, trace, read, refresh. Their descriptions and schemas cost roughly 1,516 tokens of context every time the server is loaded.
Is the io.github.James-Chahwan/repo-graph MCP server still maintained?
io.github.James-Chahwan/repo-graph is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.James-Chahwan/repo-graph MCP server under?
io.github.James-Chahwan/repo-graph declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.