dsh-cert-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y dsh-cert-mcp@0.2.13
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
list_certified | Returned a result 0.3 s · 785 characters |
During the calls (not necessarily because of them) it first contacted: raw.githubusercontent.com.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
get_certification owner, repo
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.
list_certified
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.
certification_spec
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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | node ^22.19.0 || >=24.9.0 |
| Source | github.com/PerryLink/dsh-cert-mcp |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-UIsYcvWJEpCBUcVwJDdvODDlxpRNPxSbNrA284goHGDA/LrBVmoOk6d3c0N82uDaGlKa6bBs+DSlNRuFcfUF1g== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/dsh-cert-mcp)
New version out? Ask for a fresh report.