
Deadpath
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Find exported-but-never-used names across a module set, with import-graph proof.
Overview
Deadpath'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 Deadpath 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
deadpath
Codebases accumulate exports nobody uses: a helper written for a caller that was later deleted, a constant kept "just in case", a whole module that still ships because something once imported a name from it. deadpath settles the question from evidence. You hand it a module set — each module's path, the names it exports, and the imports it makes — and it works out which exported names are never imported anywhere in the set:
- Per-module summaries — for every module, its dead export names, its total (de-duplicated) export count, and how many of its exports are used.
- A flat dead list — every dead export as a
{module, name}pair, sorted so it can drive a cleanup list or a CI check directly. - Set-wide totals — the total export count, the total
dead count, and
dead_ratio: the share of the set's exported surface that is dead, rounded to four decimals.
The proof rule is simple. An export is used when some
module in the set imports that name from its module — a
module importing its own names from itself counts, just
like any other import. Entry modules are the one exception:
mark a module entry: true and all of its exports count
as used, because an entry point's exports are public
surface consumed from outside the set. An import with an
empty names list is a side-effect import: it runs the
target module but uses none of its named exports, so it
keeps nothing alive.
Imports form a closed world: every import's from must
name one of the supplied modules. That is what makes a
dead verdict meaningful — the graph is complete by
construction, and an import pointing outside the set is a
validation error naming the offending path (for example
modules[0].imports[1].from must name a supplied module),
not a silent gap in the proof. Malformed input of any kind
— a duplicate module path, a bad exports entry, a
non-boolean entry — fails the same path-naming way, and
no partial report is produced. The computation is pure and
local: no network, no configuration, no files read beyond
the input you pass in.
CLI
args.json contains the full arguments object:
exports and imports default to [] per module, names
defaults to [] per import, and entry defaults to
false. Here legacy is exported by src/util.ts but
imported by nobody, so the report is:
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
-
find_dead_exports— Find exported names that no module imports.modules(array, required, at least one) — modules as{path, exports?, imports?, entry?}objects;pathis unique across the set, each import is a{from, names?}object whosefromnames a supplied module, andentry: truemarks a module whose exports all count as used
Returns
{modules, dead_exports, total_exports, total_dead, dead_ratio}.
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit 689ccdf
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