
Reachvuln
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Rank vulnerabilities by whether the vulnerable code path is reachable in your code.
Overview
Reachvuln's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Reachvuln in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
reachvuln
A scanner report with two hundred findings is not a work list. Most of those packages may never be loaded by your code at all, and of the ones that are, the vulnerable export may never be the one you import. reachvuln reorders the report around that question: given the findings, your modules and their imports, and your entry points, which findings can actually be reached?
Reachability is computed over the import graph you supply.
An import whose package equals another module's path
is a local edge; anything else is an external package
import. The reachable modules are the entry points plus
everything reached from them by following local edges —
breadth-first, and safe around cycles, so a circular import
chain neither loops forever nor hides what sits behind it.
A finding is reachable when some reachable module
imports its package and either the finding lists no
vulnerable_exports (any import of the package counts) or
that import's names share at least one entry with
vulnerable_exports. It is imported_unreachable when
some module imports the package but the reachable condition
does not hold — the package is in the tree, yet no reachable
module imports it in a way that touches the vulnerable
exports. It is not_imported when no module imports the
package at all. For a reachable finding, reached_via
lists the sorted distinct paths of the reachable modules
whose imports satisfy the condition; otherwise it is empty.
Ranking is pinned arithmetic, not a heuristic: severity
weighs critical 40, high 30, medium 20, and low 10, and the
weight is multiplied by 3 for reachable findings, by 1 for
imported-but-unreachable ones, and by 0 for not-imported
ones. Findings order by rank score descending, then
severity weight descending, then id ascending, and the
result also carries counts for the three classes.
Validation is strict and names the offending path: a
missing or badly typed vulnerabilities, modules, or
entry_points; a finding with a missing, empty, or
duplicate id, a missing or empty package, a severity
outside its enum, or a badly typed vulnerable_exports; a
module with a missing, empty, or duplicate path, a
missing imports, or an import with a bad package or
names; and an entry point that is not one of the module
paths. Note that entries in an import's names may be
empty strings — they simply never match a vulnerable
export, which is itself required to be non-empty. Unknown
extra fields are ignored, and no partial result is produced
on invalid input. The computation is pure and local: no
network, no configuration, and no repository is read.
CLI
args.json contains the full arguments object:
The result is printed as JSON:
Exit codes: 0 on success, 1 on a runtime error (including
an unreadable or invalid input file, or invalid input), 2
on a usage error.
MCP server
MCP client config:
Tools
-
rank_vulns_by_reach— Rank vulnerability findings by whether the vulnerable package and exports are reachable from your entry points.vulnerabilities(array, required, may be empty) — findings, each{id, package, severity, vulnerable_exports};idis a non-empty unique string,packagea non-empty string,severityone ofcritical,high,medium,low, andvulnerable_exportsan optional array of non-empty strings (default[])modules(array, required, may be empty) — modules, each{path, imports};pathis a non-empty unique string andimportsan array of{package, names}, wherepackageis a non-empty string andnamesa required array of strings (entries may be empty)entry_points(array, required, may be empty) — module paths that are entry points; every entry must equal some module'spath
Returns
{ranked, counts}, where each ranked entry is{id, package, severity, reachability, rank_score, reached_via}in the pinned order andcountsis{reachable, imported_unreachable, not_imported}.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit f659040
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts