dsh-tool-surface-proof
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@dsh-tool-surface-proofverify the current tool surface against the approved lock"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
dsh-tool-surface-proof
Content-addressed evidence that the actual recorded model-visible tool surface of one DeepSeek Harness deployment still matches an approved lock across agent scopes, permission modes and presentation modes.
DeepSeek Harness already generates an official default Tool Schema Catalog by booting shipped tool plugins. dsh-mcp-lens already compresses large MCP catalogs and offers schema-budget checks. This plugin does neither. It verifies deployment-specific, explicitly recorded envelopes: for example, whether an owner/native surface and a reader/native surface still expose exactly the approved tool identities and schemas after an upgrade.
Evidence contract
Schema version 1 binds an exact deployment revision, evaluation time, freshness policy and one approved surface per surfaceId. Each surface declares agentScope, permissionMode, presentationMode, and ordered {nameHash, schemaHash, position} locks. Each observation records the same public dimensions plus the model-visible tool objects captured by a separate trusted recorder.
The verifier detects missing or unexpected surfaces, scope/permission/presentation mismatch, added or removed tools, schema changes, optional order drift, stale/future observations, duplicate identities and revision mismatch. Reports contain only SHA-256 identities, counts and drift categories. They never return tool names, descriptions, schemas or raw business content.
This plugin does not capture live runtime state, grant or deny permission, execute commands, connect to MCP servers, or prove that a recorder was honest. Use a trusted deployment-specific recorder to create the observation envelope and review the lock before approval.
Related MCP server: mcp-supply-guard
CLI
dsh-tool-surface-proof inspect --manifest surface.json
dsh-tool-surface-proof verify --workspace-root . --manifest surface.json --artifact-dir artifactsVerification reads one workspace-relative regular file, rejects symlinks and traversal, performs no network requests or subprocesses, and writes only one content-addressed JSON report below the explicit artifact directory with exclusive creation and read-back verification.
DSH and MCP
The DSH bundle exposes dsh_tool_surface_inspect and dsh_tool_surface_verify. The independent stdio MCP server exposes inline, filesystem-free equivalents. Both call the same interface-free core.
npm test
npm run check
npm run smoke:plugin
npm run smoke:mcp
python C:/Users/ZhuanZ/.codex/skills/.system/plugin-creator/scripts/validate_plugin.py .MIT licensed. See SECURITY.md.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only verifier for 25 ProofRelay MCP tools and non-confidential evidence bundles.
Pre-flight MCP security. Blocks compromised deps + tool drift. HMAC-signed. Dredd judges.
Statically audits MCP tool surfaces for token cost, schema quality, and design issues.
Run verified read-only code tools: quant diagnostics + agent-ops preflight, no source exposure.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceScans MCP tools for trust drift, composition risks, and runtime policy violations, with optional LLM explanations.-
- AlicenseNot gradedqualityCmaintenanceEnables supply-chain integrity for MCP tools by locking tool-definition hashes after review and detecting added, removed, modified, or risky tool definitions.MIT
- AlicenseNot gradedqualityCmaintenanceLets users inspect and verify content-addressed schema migration evidence offline, checking idempotence, reversible rollback, required invariants, and explicit lossy-field disclosure without executing migrations or accessing data.MIT
- AlicenseNot gradedqualityCmaintenanceEnables verifying that recorded build accesses stay within a declared closure by inspecting and verifying hash-only receipts, without executing builds or making network requests.MIT