dr-mcp

Name: dr-mcp
Author: Inferensys

by Inferensysversion 0.3.0i★ –iRuns on your computer

Registry nameio.github.Inferensys/dr-mcp

Install

Overview

Description from the maker (original English)

Audits MCP configs, scores risk, and creates reversible repair plans.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "dr": {
      "command": "npx",
      "args": [
        "-y",
        "@inferensys/dr-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add dr -- npx -y @inferensys/dr-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "dr": {
      "command": "npx",
      "args": [
        "-y",
        "@inferensys/dr-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "dr": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@inferensys/dr-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Inferensys, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32691 servers in this category
Published to the registry more recently than 9% of the other 32691 servers in this category
Basic checks equal to or better than 100% of the other 32691 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is dr-mcp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 6 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Dialyne

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

Dialyne

by dialyne

Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

dr-mcp

Clean your MCPs.

dr-mcp is a local-first MCP audit and cleanup tool for developers who use agentic coding every day. It scans the Model Context Protocol configs your tools load, finds stale servers, abandoned packages, duplicate entries, context-heavy tools, risky permissions, and major upgrades, then generates reversible patch plans.

If you use Claude Code, OpenAI Codex, Cursor, Windsurf, GitHub Copilot, VS Code, Cline, Roo Code, Continue, or Zed across multiple projects, your MCP setup can grow quietly: old demo servers, duplicate GitHub tools, broad filesystem access, package pins behind npm latest, abandoned repositories, and large tool surfaces your agent has to consider before it writes code.

dr-mcp shows what to clean up without deleting anything during scan.

npx @inferensys/dr-mcp cleanup

That starts a local cleanup scan in the current project. You get a redacted report, a ranked list of context-heavy MCPs, package and repository freshness signals, and patch plans you can apply after review.

For the full cleanup scan with package/repo checks and local install-history tracking:

npx @inferensys/dr-mcp cleanup --registry --track-usage

Inside Claude Code, Codex, Cursor, Windsurf, GitHub Copilot, or any MCP client that exposes server prompts/tools, use dr_mcp_scan or dr_mcp_cleanup. If your client maps MCP prompts into slash commands, use /dr-mcp scan.

Why Clean Your MCPs?

MCP servers are powerful because they put tools directly into an agent's loop. That also means every extra server can add tool-selection noise, context-window pressure, startup failures, stale dependencies, or permissions you no longer intend to grant.

dr-mcp helps with:

MCP audit: one report across global and project MCP configs.
MCP cleanup: review candidates for duplicates, dead entries, abandoned packages, long-lived installs, and heavy tool surfaces.
MCP context hygiene: estimated tool counts and context weight for servers that do not belong in every coding session.
MCP security review: broad filesystem access, inline secrets, secret-looking args, and broken environment references.
MCP upgrade planning: semver drift against npm latest, including major upgrades that deserve review.
MCP repair plans: explicit operations with backups and diffs before writing.

What It Helps You Fix

Reclaim context. See which MCPs add the biggest tool lists to your agent's prompt.
Cut unwanted tool calls. Remove old servers your agent keeps considering even when the project does not need them.
Ditch abandoned MCPs. With --registry, check npm metadata and GitHub activity for archived or stale projects.
See major upgrades. Find MCP packages pinned far behind npm latest and review upgrade plans.
Find leftovers. Turn on --track-usage and build a local ledger of MCPs that keep showing up across scans.
Remove duplicates. Spot the same MCP registered in Claude, Cursor, VS Code, Codex, Windsurf, or project files.
Fix risky configs. Flag broad filesystem access, inline secrets, secret-looking args, missing commands, dead paths, and broken env refs.
Stop floating installs. Catch npx packages using latest or no version.

How The Audit Works

dr-mcp uses practical static analysis and package metadata checks:

Discover config files for Claude Desktop, Claude Code, Codex, Cursor, Windsurf, GitHub Copilot, VS Code, Cline, Roo Code, Continue, Zed, and .mcp.json.
Parse and normalize JSON, TOML, and YAML config shapes into one internal MCP server model.
Score the setup across reliability, security, context hygiene, and maintainability.
Check package freshness with npm metadata, semver classification, dist-tags.latest, and optional official registry matching.
Estimate context weight with tool-cardinality heuristics for high-surface MCPs such as GitHub, browser automation, Slack, Jira, filesystem, and databases.
Review maintenance signals from GitHub archive status and recent push activity when repository metadata is available.
Generate patch plans with JSON Pointer targets, idempotent operations, timestamped backups, and diffs.

Commands

# Local audit in the current project

npx @inferensys/dr-mcp

Deeper cleanup report with package/repo checks and local install history

npx @inferensys/dr-mcp cleanup

Full scan alias for agent workflows

npx @inferensys/dr-mcp scan --deep

Local-only cleanup flow with no network checks or usage ledger writes

npx @inferensys/dr-mcp cleanup --local

JSON for scripts or CI

npx @inferensys/dr-mcp scan --workspace . --json --registry

Shareable cleanup report

npx @inferensys/dr-mcp report --workspace . --format html > dr-mcp-report.html

Preview a repair plan

npx @inferensys/dr-mcp patch --workspace . --plan remove-duplicate-servers npx @inferensys/dr-mcp patch --workspace . --plan upgrade-stale-packages

Apply a reviewed repair plan with backups

npx @inferensys/dr-mcp patch --workspace . --plan remove-duplicate-servers --apply

Run as an MCP server

npx @inferensys/dr-mcp server

Report Sections

Score: reliability, security, context hygiene, maintainability.
Package upgrades: MCP package pins behind npm latest, including major upgrades.
Context weight: MCPs ranked by estimated tool load.
Install history: long-lived servers from the local usage ledger.
Findings: concrete issues with source config paths.
Patch plans: safe edits such as removing duplicates, dead entries, abandoned servers, or context-heavy servers.

Cleanup Plans

dr-mcp separates findings from action. A finding tells you what looks wrong; a patch plan tells you the exact config edit it can make.

remove-duplicate-servers: remove duplicate MCP server entries while keeping the first enabled definition.
remove-dead-servers: remove entries that cannot launch or packages missing from npm.
upgrade-stale-packages: update MCP package refs to npm latest.
remove-abandoned-servers: remove servers from archived or abandoned repositories.
remove-heavy-context-servers: remove servers estimated to load many tools into every session.
remove-long-lived-servers: remove servers that have stayed installed across multiple tracked scans after you confirm they are no longer useful.

Supported Tools

Tool	Configs scanned
Claude Desktop	`claude_desktop_config.json`
Claude Code / `cc`	`~/.claude.json`, `~/.claude/settings.json`, `.claude/settings.json`
OpenAI Codex	`~/.codex/config.toml`, `.codex/config.toml`
Cursor	`~/.cursor/mcp.json`, `.cursor/mcp.json`
Windsurf	`~/.codeium/windsurf/mcp_config.json`, `.windsurf/mcp.json`
GitHub Copilot in VS Code	VS Code user settings, VS Code Insiders settings, `.vscode/mcp.json`, `.vscode/settings.json`
GitHub Copilot CLI	`~/.copilot/mcp-config.json`, `.copilot/mcp-config.json`
Cline	`~/.cline/data/settings/cline_mcp_settings.json`, `.cline/data/settings/cline_mcp_settings.json`
Roo Code	`.roo/mcp.json`, common Roo Code VS Code global storage paths
Continue	`~/.continue/config.yaml`, `.continue/config.yaml`
Zed	Zed user settings, `.zed/settings.json`
Generic MCP	`.mcp.json`

Add dr-mcp To Your Agent

Once added, start from the shortest in-session action:

dr_mcp_scan

For cleanup candidates, upgrades, abandoned servers, and long-lived installs:

dr_mcp_cleanup

Clients that expose MCP prompts as slash commands may show these as dr_mcp_scan, dr_mcp_cleanup, or a prompt such as /dr-mcp scan.

Codex

codex mcp add dr-mcp -- npx -y @inferensys/dr-mcp server

Claude Code

claude mcp add dr-mcp -- npx -y @inferensys/dr-mcp server

JSON config clients

Use this for Claude Desktop, Cursor, Windsurf, Cline, Roo Code, VS Code, and GitHub Copilot in VS Code:

"mcpServers": { "dr-mcp": { "command": "npx", "args": ["-y", "@inferensys/dr-mcp", "server"] } } }

VS Code and GitHub Copilot may use servers:

"servers": { "dr-mcp": { "type": "stdio", "command": "npx", "args": ["-y", "@inferensys/dr-mcp", "server"] } } }

Zed

"context_servers": { "dr-mcp": { "command": "npx", "args": ["-y", "@inferensys/dr-mcp", "server"] } } }

Continue

mcpServers:

dr-mcp: command: npx args:

-y
@inferensys/dr-mcp
server

MCP Tools

When running as a server, dr-mcp exposes:

dr_mcp_scan
dr_mcp_cleanup
scan_mcp_setup
explain_issue
generate_patch_plan
apply_patch_plan
export_report

MCP Prompts

dr_mcp with action=scan or action=cleanup
dr_mcp_scan
dr_mcp_cleanup

Safety

Scans never edit MCP client configs.

Patch plans create timestamped backups before writing. Reports redact secrets, tokens, emails, home paths, and private GitHub repo URLs.

Usage tracking is opt-in. --track-usage writes a local ledger at ~/.dr-mcp/usage-ledger.json. It tracks what remains installed across scans; it does not claim true per-tool usage unless a client exposes that data.

dr-mcp does not auto-install, uninstall, upgrade packages, or run destructive cleanup.

Development

npm install

npm run check node dist/cli.js scan --workspace tests/fixtures/mixed --json

Registry name: io.github.Inferensys/dr-mcp

Package: @inferensys/dr-mcp

dr-mcp

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Dialyne

README from the maker

dr-mcp

Why Clean Your MCPs?

What It Helps You Fix

How The Audit Works

Commands

Deeper cleanup report with package/repo checks and local install history

Full scan alias for agent workflows

Local-only cleanup flow with no network checks or usage ledger writes

JSON for scripts or CI

Shareable cleanup report

Preview a repair plan

Apply a reviewed repair plan with backups

Run as an MCP server

Report Sections

Cleanup Plans

Supported Tools

Add dr-mcp To Your Agent

Codex

Claude Code

JSON config clients

Zed

Continue

MCP Tools

MCP Prompts

Safety

Development