DSH Plugin Certification
NPM · DSH-CERT-MCP
Read-only MCP server exposing the dsh-plugin-certification registry for DeepSeek Harness plugins.
Available components
Last scanned (3 hours ago)
Scores higher than 53% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security63
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- No install/post-install scripts declared.Pass
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency74
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to PerryLink/dsh-cert-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 636 tokens (~212/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −1
- Known CVEs: pass → unverified ▼ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: PerryLink/dsh-cert-mcp security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 0.2.12 → 0.2.13 functional
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- Security disclosure: fail → pass ▲ functional
- 1 Nov 26 +4
- Provenance: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- The attested source repository moved: PerryLink/dsh-cert-mcp security
- Stability: pass → 0.97 functional
- Package version: 0.2.11 → 0.2.12 functional
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.10 → 0.2.11 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 25 Oct 26 −1
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.97 functional
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Package version: 0.2.9 → 0.2.10 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/dsh-cert-mcp@0.2.13
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | PerryLink/dsh-cert-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/PerryLink/dsh-cert-mcp/.github/workflows/release.yml@refs/tags/v0.2.13 |
| Rekor log index | 3692641609 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:508b1872f58912908151c57024376f3830e5c6944d3f149b36b036f388281c60c0fcbac1566a0e93a77773437cdae0da1a529ae9b06cf834a5351b857 |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
certification_spec Explain the certification spec ~130
Return the dsh-plugin-certification specification document, version 1: the five graded dimensions, the grade scale from A to F, and the veto rule that can override a grade. Use this to interpret a grade you have already read - for example to learn why a record was vetoed, or what a dimension actually measures. Use list_certified or get_certification instead when you want a specific plugin's data rather than the rules behind it. Read-only: the document is compiled into the server, takes no parameters, performs no writes and needs no credentials. The same document is returned on every call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_certification Get one plugin certification record ~291
Return the certification record for ONE DeepSeek Harness plugin repository, identified by its GitHub owner and repository name: the letter grade, the snapshot date the grade was measured, and the five-dimension evidence behind it. Use this when you already know which plugin you are asking about and need its grade, or the reasoning that produced it. Use list_certified instead to enumerate every certified plugin, and certification_spec instead to learn what the five dimensions, the grade scale and the veto rule mean. Read-only: it reads a registry snapshot bundled with this server. When the public registry is reachable the snapshot may be refreshed opportunistically; otherwise the embedded snapshot is used. It performs no writes, contacts no service other than that optional refresh, and requires no credentials. Two calls with the same arguments return the same record. If the registry holds no entry for that owner/repo, the result is a plain not-found sentence naming the key it looked up and the snapshot date - it never invents, interpolates or approximates a grade.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub owner (user or organisation) of the plugin repository, for example "PerryLink". Matched case-insensitively. |
| repo | string | yes | GitHub repository name of the plugin, for example "dsh-auto-review". This is the repository name, not the npm package name. Matched case-insensitively. |
No output schema declared.
No examples provided.
list_certified List every certified plugin ~215
List every plugin in the public dsh-plugin-certification registry, each with its repository, letter grade and snapshot date, plus the registry spec version, its generation timestamp and the total count. The returned `coverage` object states what that count is and is not: the registry is an opt-in subset of the ecosystem (a plugin appears only after it was evaluated), so a short list — the bundled snapshot holds one entry — is not evidence that the ecosystem is uncertified, and a single-entry list supports no comparison across plugins. Read `coverage` before drawing any conclusion from `count`. Use this to discover what is in the registry, or to compare grades across plugins. Use get_certification instead when you already know the plugin and want its full five-dimension evidence; this tool returns the summary row only. Read-only: it reads the embedded registry snapshot (optionally refreshed from the public registry when reachable), takes no parameters, performs no writes and needs no credentials. Repeated calls are identical until the snapshot is refreshed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the DSH Plugin Certification MCP server?
DSH Plugin Certification runs locally as an npm package, launched with npx -y dsh-cert-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dsh-cert-mcp
claude mcp add perrylink-dsh-cert -- npx -y dsh-cert-mcp
What is the DSH Plugin Certification MCP server?
DSH Plugin Certification is an MCP server listed in the public MCP registry as io.github.PerryLink/dsh-cert. Read-only MCP server exposing the dsh-plugin-certification registry for DeepSeek Harness plugins. This page covers its npm package (dsh-cert-mcp).
Is the DSH Plugin Certification MCP server safe to use?
DSH Plugin Certification scores 76 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DSH Plugin Certification MCP server expose?
DSH Plugin Certification exposes 3 tools: get_certification, list_certified, certification_spec. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.
Is the DSH Plugin Certification MCP server still maintained?
DSH Plugin Certification is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the DSH Plugin Certification MCP server under?
DSH Plugin Certification declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.