io.github.builditwithgk/repo-cartographer
NPM · REPO-CARTOGRAPHER
Maps any repo into an architecture diagram (Mermaid/Graphviz) and enforces architecture rules in CI
Available components
Last scanned (11 hours ago)
Scores higher than 90% of npm servers
Category Developer Tools
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 92 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 781 tokens (~130/item across 6 items; 5 tools + 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 −1
- Stability: pass → 0.93 functional
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 6 Nov 2026 · Analysed npm/repo-cartographer@1.0.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 →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
build_import_graph Build import graph ~132
Extract intra-repo import/require relationships for JavaScript/TypeScript and Python. Nodes are files (auto-collapsed to module/directory level for large repos); edges are directed import relationships. Returns JSON. Use this when you need the raw dependency edges — who imports whom — e.g. to reason about coupling, cycles, layering, or the blast radius of a change. Do NOT use it just to draw a picture: generate_diagram returns a ready-to-render draft, and map_repo does the whole flow in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path to the repository root |
No output schema declared.
No examples provided.
generate_diagram Generate diagram ~171
Combine scan + import facts into a DRAFT diagram string — Mermaid flowchart (default) or Graphviz DOT. level 'high' (default) shows modules/directories; 'detail' shows files grouped by module. This is a draft the calling model is expected to refine. Use this when you want to edit or refine the diagram source before rendering (pair with render_diagram to write the HTML afterwards). If no in-between editing is needed, prefer map_repo — it generates AND renders in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Diagram notation: 'mermaid' (default; renders on GitHub) or 'dot' (Graphviz interop) |
| level | string | – | Diagram granularity (default 'high') |
| path | string | yes | Absolute or relative path to the repository root |
No output schema declared.
No examples provided.
map_repo Map repository (one-shot) ~192
Point at a folder and get a downloadable architecture diagram in one call: runs scan + import-graph + render internally and returns the HTML path, a facts summary, and the draft diagram source inline. By default writes architecture.html plus the raw source (.mermaid or .dot) into the repo; pass outPath to write elsewhere. Use the granular tools (scan_repo, build_import_graph, generate_diagram, render_diagram) only when you need to compose the steps yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Diagram notation: 'mermaid' (default; renders on GitHub) or 'dot' (Graphviz interop) |
| level | string | – | Diagram granularity (default 'high') |
| outPath | string | – | Output base path (default: <repo>/architecture); .html and the raw source are written |
| path | string | yes | Absolute or relative path to the repository root |
No output schema declared.
No examples provided.
render_diagram Render diagram ~161
Write a self-contained, shareable HTML page (renders via CDN: Mermaid, or Viz for Graphviz DOT) plus the raw source file (.mermaid or .dot). Returns the absolute paths written. Use this as the final step after refining a draft from generate_diagram — or to render ANY Mermaid/DOT source, hand-written included. If you have not edited the draft, prefer map_repo, which renders it for you.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Notation of `source` (default 'mermaid') |
| outPath | string | yes | Output path (with or without extension); .html and the raw source siblings are written |
| source | string | yes | Diagram source to render (Mermaid, or DOT when format is 'dot') |
No output schema declared.
No examples provided.
scan_repo Scan repository ~109
Deterministically extract facts from a local repo: programming languages, frameworks/libraries, entry points, top-level modules (with role guesses), and a manifest summary. Returns JSON facts only — no interpretation. Use this when you need repo facts WITHOUT a diagram (e.g. to answer questions about the stack). Prefer map_repo for the one-shot diagram flow; use build_import_graph when you need dependency edges rather than an inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path to the repository root |
No output schema declared.
No examples provided.
How do I install the io.github.builditwithgk/repo-cartographer MCP server?
io.github.builditwithgk/repo-cartographer runs locally as an npm package, launched with npx -y repo-cartographer. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · repo-cartographer
claude mcp add builditwithgk-repo-cartographer -- npx -y repo-cartographer
What is the io.github.builditwithgk/repo-cartographer MCP server?
io.github.builditwithgk/repo-cartographer is an MCP server listed in the public MCP registry as io.github.builditwithgk/repo-cartographer. Maps any repo into an architecture diagram (Mermaid/Graphviz) and enforces architecture rules in CI. This page covers its npm package (repo-cartographer).
Is the io.github.builditwithgk/repo-cartographer MCP server safe to use?
io.github.builditwithgk/repo-cartographer scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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.builditwithgk/repo-cartographer MCP server expose?
io.github.builditwithgk/repo-cartographer exposes 5 tools: map_repo, scan_repo, build_import_graph, generate_diagram, render_diagram. Their descriptions and schemas cost roughly 765 tokens of context every time the server is loaded.
Is the io.github.builditwithgk/repo-cartographer MCP server still maintained?
io.github.builditwithgk/repo-cartographer is still listed as active in the MCP registry. We last reached this channel on 6 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.builditwithgk/repo-cartographer MCP server under?
io.github.builditwithgk/repo-cartographer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.builditwithgk/repo-cartographer MCP server?
VerifyMCP ran 16 checks on io.github.builditwithgk/repo-cartographer, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.