DropPerch domain expiry
NPM · DROPPERCH-MCP
Live domain expiry, lifecycle stage, drop date and SSL checks from the registry over RDAP.
Available components
Last scanned (6 hours ago)
Scores higher than 48% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to webvoguetech/dropperch-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 233 tokens (~58/item across 4 items; 4 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "domain_drop_date" implies "drop" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
- 4 Nov 26 +20
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: unverified → fail ▼ security
- Malware scan: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 3 Nov 26 54
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 5 Nov 2026 · Analysed npm/dropperch-mcp@1.0.1
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 | webvoguetech/dropperch-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/webvoguetech/dropperch-mcp/.github/workflows/publish.yml@refs/tags/v1.0.1 |
| Rekor log index | 3664575879 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2d7abbd4db730e6793824a740576f92ca06513e3e82eb95980cfb8773d104a5b15ee4cfa186296988e758e0cb4cd224db15935ef9e9b9c115fe2bff6c |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
check_domain Check a domain ~71
Expiry date, days left, lifecycle stage (active, grace, redemption, pending delete), registrar, nameservers, registry status codes, registration date and likely drop date for one domain, read live from its registry over RDAP.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain name, e.g. example.com |
No output schema declared.
No examples provided.
check_domains Check many domains ~50
The same live registry check for up to 50 domains at once, with the soonest expiry called out. Use it to audit a portfolio or a client list.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Domain names |
No output schema declared.
No examples provided.
domain_drop_date When will a domain drop? ~63
Estimate when an expiring or expired domain will be deleted and become registrable, from its current registry status and ICANN timelines (redemption 30 days, pending delete about 5).
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain name, e.g. example.com |
No output schema declared.
No examples provided.
ssl_certificate Check an SSL certificate ~49
Read the HTTPS certificate on a domain (or www): issuer, expiry date, days left, and whether browsers trust it.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain name, e.g. example.com |
No output schema declared.
No examples provided.
How do I install the DropPerch domain expiry MCP server?
DropPerch domain expiry runs locally as an npm package, launched with npx -y dropperch-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 · dropperch-mcp
claude mcp add webvoguetech-dropperch-mcp -- npx -y dropperch-mcp
What is the DropPerch domain expiry MCP server?
DropPerch domain expiry is an MCP server listed in the public MCP registry as io.github.webvoguetech/dropperch-mcp. Live domain expiry, lifecycle stage, drop date and SSL checks from the registry over RDAP. This page covers its npm package (dropperch-mcp).
Is the DropPerch domain expiry MCP server safe to use?
DropPerch domain expiry scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 DropPerch domain expiry MCP server expose?
DropPerch domain expiry exposes 4 tools: check_domain, check_domains, domain_drop_date, ssl_certificate. Their descriptions and schemas cost roughly 233 tokens of context every time the server is loaded.
Is the DropPerch domain expiry MCP server still maintained?
DropPerch domain expiry 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 DropPerch domain expiry MCP server under?
DropPerch domain expiry declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.