DSH Plugin Certification vs ドメイン番人
DSH Plugin Certification is an MCP server published by PerryLink. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). ドメイン番人 is an MCP server published by j-doi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  DSH Plugin Certification |  ドメイン番人 |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.9 Downloads/month (npm): 2 562 Downloads/week (npm): 481 Not marked · First seen |
Listed Version: 0.1.0 No figure published Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.2.9 Downloads/month (npm): 2 562 Downloads/week (npm): 481 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | DSH Plugin Certification | ドメイン番人 |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | On your machine (dsh-cert-mcp) | Remote server (domain-bannin.jp/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/perrylink/dsh-cert-mcp | github.com/j-doi/domain-shield |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
DSH Plugin Certification
Read-only MCP server exposing the dsh-plugin-certification registry for DeepSeek Harness plugins.
ドメイン番人
ドメインの設定を調べる MCP サーバー。SPF / DKIM / DMARC・DNS・SSL 証明書・セキュリティヘッダ・サブドメイン・類似ドメインを、公開情報だけで確認します。登録不要・無料。
How to run each
DSH Plugin Certification As a local MCP server: npm package
claude mcp add --transport stdio dsh-cert -- npx -y dsh-cert-mcpドメイン番人 As a remote MCP server
claude mcp add --transport http domain-bannin https://domain-bannin.jp/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ドメイン番人 has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of DSH Plugin Certification nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: DSH Plugin Certification · What it can do: ドメイン番人 · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.