DeepSeek Harness
CallLint support for DeepSeek Harness by DeepSeek. CallLint does not auto-discover DeepSeek Harness configuration. Its MCP servers are plugin instances in cordis.yml rather than an mcpServers map, so no existing extractor reads that shape. This record exists for discovery routing only: DeepSeek is a model vendor here, not a security-relevant distinction.
Why scan DeepSeek Harness?
DeepSeek Harness carries MCP servers as plugin instances, so authority is granted through a plugin list rather than a server map — the grant is real, the shape is just less obvious.
Usage
CallLint does not yet support native auto-discovery for DeepSeek Harness. No automatic detection yet — this page documents where the config lives.
What CallLint does to DeepSeek Harness
Offline by default. Deterministic. Never executes the server it judges. SAFE means no blockers observed, not a proof of runtime safety.
A No blockers observed verdict means exactly that — no blocker under the evidence CallLint could collect. It is not a guarantee, and Insufficient evidence never becomes it on its own. See Coverage Boundary for what this scan does not look at.
Configuration Paths
CallLint looks for DeepSeek Harness configurations in:
cordis.yml @deepseek-ai/dsh-mcp-client plugin instances
Distribution
CallLint is available for DeepSeek Harness through:
- mcp-stdio (via officialMcpRegistry) — Listing not yet verified
-
dsh-plugin
— Not available here
⚠️ The harness is in vendor-declared developer preview with breaking changes expected. Do not build a plugin against an unstable interface for listing eligibility alone.
Support Status
Guide only — No automatic detection yet — this page documents where the config lives.
CallLint publishes no scan command for DeepSeek Harness yet. That is a statement about CallLint's coverage, not about DeepSeek Harness: see Coverage Boundary for what would have to be built first.
Official Sources
Coverage Boundary
CallLint does not auto-discover DeepSeek Harness configuration. Its MCP servers are plugin instances in cordis.yml rather than an mcpServers map, so no existing extractor reads that shape. This record exists for discovery routing only: DeepSeek is a model vendor here, not a security-relevant distinction.