io.github.PerryLink/dsh-cert
NPM · DSH-CERT-MCP · SCANNED SEP 20
Read-only MCP server exposing the dsh-plugin-certification registry for DeepSeek Harness plugins.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency71
- 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
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 130 tokens (~43/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.PerryLink/dsh-cert MCP server?
io.github.PerryLink/dsh-cert 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
{
"mcpServers": {
"perrylink-dsh-cert": {
"command": "npx",
"args": [
"-y",
"dsh-cert-mcp"
]
}
}
} {
"servers": {
"perrylink-dsh-cert": {
"command": "npx",
"args": [
"-y",
"dsh-cert-mcp"
]
}
}
} codex mcp add perrylink-dsh-cert -- npx -y dsh-cert-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"perrylink-dsh-cert": {
"type": "local",
"command": [
"npx",
"-y",
"dsh-cert-mcp"
],
"enabled": true
}
}
} openclaw mcp add perrylink-dsh-cert --command npx --arg -y --arg dsh-cert-mcp
mcp_servers:
perrylink-dsh-cert:
command: "npx"
args: ["-y", "dsh-cert-mcp"] {
"McpServers": {
"perrylink-dsh-cert": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"dsh-cert-mcp"
]
}
}
} assistant mcp add perrylink-dsh-cert -t stdio -c npx -a -y dsh-cert-mcp
{
"mcpServers": {
"perrylink-dsh-cert": {
"command": "npx",
"args": [
"-y",
"dsh-cert-mcp"
]
}
}
} 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.
- 19 Sept 26 73
First indexed and scored.
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 20 Sept 2026 · Analysed npm/dsh-cert-mcp@0.2.2
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.2 |
| Rekor log index | 2892519792 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:4de6bb07e8d357a2b75c7c8a659240ee146cb49901f6ae229f0db041a9d041639786dade013b2d13c51d67806659db3f415e098ae6beb047923e7fdbd |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~31
Explain the dsh-plugin-certification spec v1: the five dimensions, the grade scale and the veto rule.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_certification ~70
Return the dsh-plugin-certification record for one DeepSeek Harness plugin repository (grade, snapshot date, five-dimension evidence).
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub owner, e.g. PerryLink |
| repo | string | yes | GitHub repository name, e.g. dsh-auto-review |
No output schema declared.
No examples provided.
list_certified ~29
List every plugin in the public dsh-plugin-certification registry with repo, grade and snapshot date.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.PerryLink/dsh-cert MCP server?
io.github.PerryLink/dsh-cert 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 io.github.PerryLink/dsh-cert MCP server safe to use?
io.github.PerryLink/dsh-cert scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 io.github.PerryLink/dsh-cert MCP server expose?
io.github.PerryLink/dsh-cert exposes 3 tools: get_certification, list_certified, certification_spec. Their descriptions and schemas cost roughly 130 tokens of context every time the server is loaded.
Is the io.github.PerryLink/dsh-cert MCP server still maintained?
io.github.PerryLink/dsh-cert is still listed as active in the MCP registry. We last reached this channel on 20 September 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 io.github.PerryLink/dsh-cert MCP server under?
io.github.PerryLink/dsh-cert 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.