When was npm:@inferensys/dr-mcp last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

npm:@inferensys/dr-mcp

Item: npm:@inferensys/dr-mcp
Rating: 93
Author: wmcp.sh

https://www.npmjs.com/package/@inferensys/dr-mcp

93/100 · MCP Trust Grade · checked 1mo ago · MCP 0.3.0

Is the npm:@inferensys/dr-mcp MCP server safe to use?

Independent trust grade A (93/100). Static analysis of npm package @inferensys/dr-mcp@0.3.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured. wmcp.sh continuously watches npm:@inferensys/dr-mcp for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 7 tools · Developer Tools

dr_mcp_scan

One-step MCP cleanup scan for agent sessions. Checks context weight, stale packages, abandoned repos, duplicates, and safe patch plans.

dr_mcp_cleanup

Scan and return the highest-value MCP cleanup candidates. Does not apply patches.

scan_mcp_setup

Scan local MCP configuration files and return a redacted diagnostic report.

explain_issue

Explain a diagnostic from the current MCP setup scan.

generate_patch_plan

Generate a reversible patch plan for a scan finding.

apply_patch_plan

Apply a patch plan after explicit confirmation. Creates backups before writing.

export_report

Export a redacted dr-mcp report as Markdown, HTML, or JSON.

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 7 tool(s) detected in source

Security (OWASP MCP)30%90

no high-risk patterns in sampled source
scanned 6 source files

Maintenance / popularity20%92

published within 90 days
1 published version

Tool hygiene15%95

✓ ships TypeScript types
4 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
15 weekly downloads

Findings

INFO Static analysis of npm package @inferensys/dr-mcp@0.3.0 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:@inferensys/dr-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@inferensys/dr-mcp grade A

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3A%40inferensys%2Fdr-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade A](https://wmcp.sh/mcp/grade/npm%3A%40inferensys%2Fdr-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40inferensys%2Fdr-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3A%40inferensys%2Fdr-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3A%40inferensys%2Fdr-mcp/badge.svg" alt="MCP Trust Grade A · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.