dsh-mcp-audit: Auditing MCP Configuration Risks for DeepSeek Harness
feely0208/dsh-mcp-audit
A security plugin for DeepSeek Harness that audits MCP configs for unpinned npx -y packages, plaintext http endpoints and local executables, cutting supply-chain poisoning risk.
dsh-mcp-audit is an MCP configuration security audit plugin for DeepSeek Harness that focuses on easily overlooked configuration patterns. MCP services typically read and write files, execute tools, and reach accounts, giving them far broader permissions than ordinary plugins, while their configs often sit unversioned on personal machines and have never been reviewed. The plugin lists unpinned remote packages, plaintext endpoints, and executable local services across high, medium, and low tiers, and supports rule rationale inspection plus HTML report export so every finding can be traced.
How to Install
dsh plugin --profile web add @deepwhale-cn/dsh-mcp-audit- Category
- Development & Operations
- Platform
- DSH Plugin
- Author
- feely0208
- Distribution
- Plugin
dsh-mcp-audit Key Features
dsh-mcp-audit Repo Summary
What Does It Do?
MCP Audit is a DSH plugin for DeepSeek Harness that audits MCP service configurations for unpinned remote packages, plaintext endpoints, and executable local services. It addresses a specific risk: MCP services usually hold far broader permissions than ordinary plugins—file access, tool execution, account access—while their configs often sit unversioned on personal machines and have never been reviewed. The plugin grades findings as high, medium, or low so risky entries stand out immediately. It is maintained by feely0208 under the MIT license and written in Shell.
Core Features
- High-severity detection: flags unpinned
npx -ystyle entries that pull the latest version on every start, plus plaintext http:// endpoints, warning that a poisoned upstream release leaves no version to roll back to. - Medium-severity detection: marks MCP services that point at local executables or scripts.
- Low-severity notice: reports when no MCP configuration can be found in the repository.
- Rule inspection: lists every audit rule together with the rationale behind it, so each finding can be traced.
- Report export: produces an HTML audit report for archiving or sharing.
- Demo mode: runs a demonstration so you can see detection results without a real config.
How to Use This Plugin?
After enabling it in DSH, run the audit against a target repository to get a severity-grouped list of MCP configuration issues. Use demo mode first if you just want to see what detection looks like, list the rules and their rationale to understand why something was flagged, and export an HTML report when you need a record. It only audits configuration, not the services themselves—what the service code does or whether it exfiltrates data is out of scope. Pinning a version is not the same as being safe: it guards against silent upstream changes, not against a package that was malicious from the start. It complements dependency-audit plugins: those check npm dependencies, this one checks MCP configuration.
This page is an independent rewrite of the plugin's official README — for authoritative documentation and the latest changes, refer to the source: feely0208/dsh-mcp-audit. The plugin is third-party code that runs on your machine once installed; inclusion does not imply endorsement — please review the source before installing.