io.github.n24q02m/crg
PYPI · BETTER-CODE-REVIEW-GRAPH
Token-efficient code review knowledge graph: semantic search and call-graph resolution.
Available components
Last scanned (16 hours ago)
Scores higher than 65% 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 Security99
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 77 of 78 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 77 of 78 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency23
- 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 (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1238 tokens (~206/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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 22% of tool parameters carry a description.Partial
- 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 0
- Package version: 3.30.0 → 3.31.0 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Package version: 3.30.0 → 3.31.0 functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
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/better-code-review-graph@3.31.0
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 | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 77 packages
| Packages resolved | 77 |
|---|---|
| Stale | 5 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
config Config ~122
Server configuration, status, and model-cell setup. Actions: status (show state), set (key, value -- keys: log_level), cache_clear (wipe embeddings), setup_status (state + configured model cells), setup_start (where the host configures keys), setup_skip (local mode), setup_reset (reset to local), setup_complete (re-resolve from host config). Use `help` tool for full docs.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| force | boolean | – | – |
| key | – | – | – |
| repo_root | – | – | – |
| value | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
graph Graph ~141
Build and manage the code knowledge graph. Actions: build (full_rebuild, base, repo_root), update (base, repo_root), stats (repo_root), embed (repo_root), export (format, output_path, repo_root), import (import_path, repo_root), summarize (max_nodes, repo_root). Use `help` tool for full docs.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| base | string | – | – |
| format | string | – | – |
| full_rebuild | boolean | – | – |
| import_path | – | – | – |
| max_nodes | integer | – | – |
| output_path | – | – | – |
| repo_root | – | – | – |
| roots | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
help Help ~42
Get full documentation for any tool. Topics: graph | query | review | config | security | recipes. Use when compressed descriptions are insufficient.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
query Query ~263
Query the code knowledge graph for relationships, search, and impact analysis. Actions: query (pattern, target), search (search_query), impact (changed_files|base), large_functions (min_lines), spot_check (n -- random callsite snippets from last callers_of/callees_of/inheritors_of/importers_of result), renamed_in_diff (base -- symbols whose callsite line shifted vs base ref), diff (from_sha, to_sha -- nodes added/removed/modified between two commit SHAs). Use `help` tool for full docs.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| as_of | string | – | – |
| base | string | – | – |
| changed_files | – | – | – |
| context_lines | integer | – | – |
| file_path_pattern | – | – | – |
| from_sha | string | – | – |
| kind | – | – | – |
| languages | – | – | – |
| limit | integer | – | – |
| max_depth | integer | – | – |
| max_payload_bytes | integer | – | – |
| max_results | integer | – | – |
| min_lines | integer | – | – |
| n | integer | – | – |
| pattern | – | – | – |
| repo | string | – | – |
| repo_root | – | – | – |
| search_query | – | – | – |
| target | – | – | – |
| to_sha | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
review Review ~492
Generate token-efficient review context for code changes. Actions: context (default — auto-detects changed files from git diff, returns structural summary, impacted nodes, source snippets, and review guidance), delta (from_sha, to_sha — wraps the `query.diff` buckets and, when show_line_shifts=true, surfaces qualified_names whose line_start moved between the two commits for refactor auditing). Context params: changed_files (auto), max_depth=2, include_source=true, max_lines_per_file=200, base='HEAD~1', repo_root (auto). Delta params: from_sha, to_sha, show_line_shifts=false, repo, repo_root. Use `help` tool for full docs.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | ``context`` (default) or ``delta``. |
| base | string | – | ``context`` action — git ref for change detection (default: ``HEAD~1``). |
| changed_files | – | – | ``context`` action — files to review (auto-detected from git if omitted). |
| from_sha | string | – | ``delta`` action — earlier commit SHA. Required. |
| include_source | boolean | – | ``context`` action — include source code snippets (default: true). |
| languages | – | – | ``context`` action — optional list of language names (e.g. ``["python"]``) to scope the ``untested_functions`` list. Excludes functions whose language doesn't match. Fixes false positives on cross-la… |
| max_depth | integer | – | ``context`` action — impact radius depth (default: 2). |
| max_lines_per_file | integer | – | ``context`` action — max source lines per file (default: 200). |
| repo | string | – | Phase 2 Task 10 — when non-empty, scope to nodes whose ``repo_id`` matches (e.g. ``repo='repo_a-aaaaaaaa'``). Default ``""`` includes every federated repo. Both actions. |
| repo_root | – | – | Repository root path (auto-detected). Both actions. |
| show_line_shifts | boolean | – | ``delta`` action — when True, include nodes whose ``line_start`` moved between ``from_sha`` and ``to_sha`` in the response (default False). |
| to_sha | string | – | ``delta`` action — later commit SHA. Required. |
Structured output declared, but exposes no named fields.
No examples provided.
security Security ~116
Security scanning over the code knowledge graph. Actions: scan (engine='heuristic'|'semgrep', repo_root), report (format='json'|'sarif', repo_root), suppress (rule_id, remove=false, repo_root), rule_list (engine='heuristic'|'semgrep'). Use `help` tool for full docs.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| engine | string | – | – |
| format | string | – | – |
| remove | boolean | – | – |
| repo_root | – | – | – |
| rule_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.n24q02m/crg MCP server?
io.github.n24q02m/crg runs locally as a PyPI package, launched with uvx better-code-review-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 · better-code-review-graph
claude mcp add n24q02m-crg -- uvx better-code-review-graph
What is the io.github.n24q02m/crg MCP server?
io.github.n24q02m/crg is an MCP server listed in the public MCP registry as io.github.n24q02m/crg. Token-efficient code review knowledge graph: semantic search and call-graph resolution. This page covers its PyPI package (better-code-review-graph).
Is the io.github.n24q02m/crg MCP server safe to use?
io.github.n24q02m/crg scores 69 out of 100 on VerifyMCP. 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.n24q02m/crg MCP server expose?
io.github.n24q02m/crg exposes 6 tools: graph, query, review, config, help, security. Their descriptions and schemas cost roughly 1,176 tokens of context every time the server is loaded.
Is the io.github.n24q02m/crg MCP server still maintained?
io.github.n24q02m/crg 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.n24q02m/crg MCP server under?
io.github.n24q02m/crg declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.