MCP servers · cloudcorprecords

deadpath: find exports that no module in a set imports

Finds exported names that no module in a supplied set imports, reported per module, as a flat list and as set-wide totals.

This text was machine-translated from the publisher's own information and has not been checked by a human editor. The publisher's original text is the reference.

This resource was imported automatically from the sources listed below and has not been reviewed by the AI Gate team yet. The description is the publisher's own, as published. Check the repository before installing.

What it does

deadpath finds exported names that no module in a supplied set imports. Given each module's path, its exports and its imports, it reports dead export names and counts per module, a sorted flat list of dead {module, name} pairs, and set-wide totals including a dead_ratio rounded to four decimals. An export counts as used when another module in the set imports it by name, and a module importing its own names also counts. Modules marked entry keep all their exports as used, and side-effect imports with an empty names list keep nothing alive.

It suits cleanup of a codebase whose modules have accumulated exports nobody uses, such as helpers left behind after a caller was deleted. The flat list can drive a cleanup list or a CI check. It is also available as an MCP tool, find_dead_exports, which returns the same report.

It runs as a command-line tool that reads an args.json file containing the arguments object, or as an MCP server exposing find_dead_exports. The computation is pure and local, with no network access, configuration, or file reads beyond the input passed in. Exit codes are 0 on success, 1 on runtime errors including invalid input, and 2 on usage errors.

Limitations and requirements

Every import's from must name a module in the supplied set. An import pointing outside the set, a duplicate module path, a malformed exports entry or a non-boolean entry value returns a validation error naming the offending path, and no partial report is produced. The analysis covers only the modules passed in, so exports used outside the set are reported as dead unless their module is marked entry.

Safety

Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.

  • Runs code or changes an assistant's behaviour

Sources

  • Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
    io.github.CloudCorpRecords/deadpath

    Find exported-but-never-used names across a module set, with import-graph proof.

    v0.1.0
    As shown on registry.modelcontextprotocol.io when we last read it
MCP servers
hashicorp

Terraform MCP Server (HashiCorp)

HashiCorp's MCP server that gives an assistant current Terraform Registry information on providers, modules and policies, and can manage HCP Terraform workspaces.

1.6K GitHub starsCloud & DevOpsSoftware development
Updated 17 Nov 2026
MCP servers
neondatabase

Neon MCP Server (Postgres)

Neon's MCP server for managing Neon Postgres in plain language: create projects and branches, run queries and prepare schema migrations from your editor.

663 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
redis

Redis MCP Server

Redis's official MCP server that lets an AI assistant store, read and search data in a Redis database, including streams, JSON documents and vector indexes.

642 GitHub starsData & databasesSoftware development
Updated 17 Nov 2026
MCP servers
supabase-community

Supabase MCP Server

Supabase's MCP server that connects an AI assistant to your Supabase project to design tables, run queries, read configuration and look up documentation.

Data & databasesSoftware development
Updated 17 Nov 2026