Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Karry1123/repograph

NPM · REPOGRAPH-CLI

Local architecture maps and caller impact analysis with directory clustering and utility folding.

Available components

+4 this week 62 Trust /100

Last scanned (20 hours ago)

Scores higher than 31% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 32 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability48
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 138 tokens (~46/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 27 Oct 26 +1
    • Security disclosure: fail → unverified ▼ functional
  • 26 Oct 26 57

    First indexed and scored.

Diagnostics

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 npm/repograph-cli@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 111 packages
Packages resolved 111
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~138 tokens

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 →

Tool Tokens
generate_architecture_html ~45

Write a self-contained interactive architecture map of a local codebase.

NameTypeReqDescription
outputPathstring––
pathstringyes–
themestring––

No output schema declared.

No examples provided.

query_impact_path ~43

Find direct and transitive callers of a changed file, with BFS depths and affected clusters.

NameTypeReqDescription
changedFilestringyes–
pathstringyes–

No output schema declared.

No examples provided.

scan_repository_graph ~50

Scan a local codebase into an architecture graph. Test files and external imports are excluded.

NameTypeReqDescription
collapseUtilsboolean––
maxDepthinteger––
pathstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.Karry1123/repograph MCP server?

io.github.Karry1123/repograph runs locally as an npm package, launched with npx -y repograph-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · repograph-cli

# add to Claude Code
claude mcp add karry1123-repograph -- npx -y repograph-cli
Common questions

What is the io.github.Karry1123/repograph MCP server?

io.github.Karry1123/repograph is an MCP server listed in the public MCP registry as io.github.Karry1123/repograph. Local architecture maps and caller impact analysis with directory clustering and utility folding. This page covers its npm package (repograph-cli).

Is the io.github.Karry1123/repograph MCP server safe to use?

io.github.Karry1123/repograph scores 62 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. 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.Karry1123/repograph MCP server expose?

io.github.Karry1123/repograph exposes 3 tools: scan_repository_graph, generate_architecture_html, query_impact_path. Their descriptions and schemas cost roughly 138 tokens of context every time the server is loaded.

Is the io.github.Karry1123/repograph MCP server still maintained?

io.github.Karry1123/repograph 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.Karry1123/repograph MCP server under?

io.github.Karry1123/repograph declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.