What it may solve
Per-workspace MCP scoping for the DeepSeek Harness — decide which MCP servers a session may see from the directory it was opened in.
Imported third-party catalog description; not a Registry verification conclusion.Per-workspace MCP scoping for the DeepSeek Harness — decide which MCP servers a session may see from the directory it was opened in.
Author: felix-lj-ct · Memory · Catalog snapshot: 2026-09-19Canonical semantic path
Per-workspace MCP scoping for the DeepSeek Harness — decide which MCP servers a session may see from the directory it was opened in.
Imported third-party catalog description; not a Registry verification conclusion.felix-lj-ct/dsh-mcp-workspace-scope
— stars · 0 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository is reachable and not archived. Public data: 2 stars, 5 commits, 0 forks, and 0 watches; latest commit 2026-08-31.
Conclusion: Resolved npm release 0.1.1, published 2026-08-31, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The scan observed 3 code capabilities: may read environment variables, may create or modify files, may access the network. No predefined elevated-risk condition was triggered; this is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-mcp-workspace-scope@0.1.1; SHA-256: 26e9537868a21bffd5fa75497feef27c1594f202908914b0b072d0feef49e32e.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-mcp-workspace-scope. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-mcp-workspace-scopeAnalyzed 0.1.1github:felix-lj-ct/dsh-mcp-workspace-scopeExact version not resolved