dr-mcp

Name: dr-mcp
Author: Inferensys

作者：Inferensys版本 0.3.0i★ –i在你的电脑上运行

注册名称io.github.Inferensys/dr-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 Inferensys 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32696 个服务器的 0%
发布到注册中心的时间比此分类中其他 32696 个服务器的 9% 更新
基础检查结果等于或优于此分类中其他 32696 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

dr-mcp 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.3.0）于6个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, LexPact UK Contracts

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211前天更新

安装

LexPact UK Contracts

作者：Idadabhai

Generate UK-law contracts: NDA, service, freelance, recruiter terms of business, IR35.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

LexPact UK Contracts

作者的 README

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