io.github.CloudCorpRecords/sweepdot
NPM · @RENETURCIOS/SWEEPDOT · 2 COMPONENTS
Domain availability, WHOIS records and TLD pricing straight from the registries.
Available components
Last scanned (22 hours ago)
Scores higher than 39% of npm servers
Category E-commerce
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 Security98
- 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
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1016 tokens (~338/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 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
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.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 26 53
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 21 Nov 2026 · Analysed npm/@reneturcios/sweepdot@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| 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_domains Check domain availability and price ~651
Checks whether domain names are available, with registration and renewal prices. Answers come from the registry itself: DNS delegation first, then RDAP, with a WHOIS fallback for the registries that publish no RDAP service. A registry that is throttled, timed out or unreachable is reported as unconfirmed, never as available — a raw whois query reports one as available, which is the one wrong answer that costs money. Covers .dev and .app, whose operators run no port-43 whois server at all, and resolves the right registry per extension without being told which. Accepts bare names (expanded across the given extensions) and exact domains (checked as-is). Returns availability, confidence, price, minimum registration term, any eligibility restriction, and where to buy. When a buy link has paid:true, show the response's top-level disclosure sentence alongside it — a commission is earned on that link and the reader is entitled to know before clicking. Each row in prices[] names the registrar it belongs to in vendor — quote the number with that registrar, and link the same one. buy[].url is the link to give; never present check_at[] (estimates only) as a buy link, only as "check availability at"; never compose a registrar URL yourself. Show the link for an available name in the same message as the verdict rather than waiting to be asked, and say so when renewal costs more than the first year or min_term_years makes the first bill a multiple of the price shown. confidence:estimated is not availability — it means no registry answered, usually because one was throttled, so present it as unconfirmed and never as a free name. A result carrying policy.closed is an extension that sells to nobody: it has no price and no buy link, and calling it available offers a name that cannot be bought at any price. When policy carries eligibility, say so before the price — a rule that turns the buyer away at checkout matters more than what they would have paid. Every quoted price is a floor: p…
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Brand names or exact domains. A name without a dot is checked across every extension in tlds; a name with a dot is checked exactly as given. |
| tlds | array | – | Extensions to check bare names against, without leading dots. Choose ones that fit the business: a bakery and an ML startup should not get the same list, and the person asking usually cannot name the… |
No output schema declared.
No examples provided.
list_tlds List checkable extensions with prices ~190
Every extension this server can check, with registration and renewal price, minimum registration term, and any eligibility restriction on who may register it. Use before check_domains when the extensions to check are not already decided: the catalogue is wider than the handful most people can name, prices vary by more than an order of magnitude, and min_term_years means the first bill can be a multiple of the price shown. An entry carrying vendor is priced by a registrar other than the one quoted by default, because that one does not sell the extension — the number is still real, it just belongs to the named registrar. An entry with no price at all means no registrar here sells it, which is a fact about this catalogue and not about the extension: several are sold perfectly well by registrars we hold no feed for, so an absent price leaves availability an open question rather than settling it. All prices are USD.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whois Look up a domain's registry record ~175
Registry record for one domain: registrar, registration and expiry dates, nameservers, status codes, and whether it appears to be for sale. Resolves the correct registry host for the extension itself, and reads RDAP for .dev, .app and other extensions whose operators publish no port-43 whois service. Use when asked who owns a domain, when it expires, or where it is hosted. It forces a registry lookup, so it is also the only call that fills offer — a taken domain that appears to be parked or listed for sale. An offer is an inference from nameservers and a listing page, never a quote: the asking price lives on the listing and not in the registry, so link the listing rather than naming a figure.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A full domain, e.g. example.com |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/sweepdot MCP server?
io.github.CloudCorpRecords/sweepdot runs locally as an npm package, launched with npx -y @reneturcios/sweepdot 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 · @reneturcios/sweepdot
claude mcp add cloudcorprecords-sweepdot -- npx -y @reneturcios/sweepdot mcp
What is the io.github.CloudCorpRecords/sweepdot MCP server?
io.github.CloudCorpRecords/sweepdot is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/sweepdot. Domain availability, WHOIS records and TLD pricing straight from the registries. This page covers its npm package (@reneturcios/sweepdot).
Is the io.github.CloudCorpRecords/sweepdot MCP server safe to use?
io.github.CloudCorpRecords/sweepdot scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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.CloudCorpRecords/sweepdot MCP server expose?
io.github.CloudCorpRecords/sweepdot exposes 3 tools: check_domains, whois, list_tlds. Their descriptions and schemas cost roughly 1,016 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/sweepdot MCP server still maintained?
io.github.CloudCorpRecords/sweepdot is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.CloudCorpRecords/sweepdot MCP server under?
io.github.CloudCorpRecords/sweepdot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/sweepdot MCP server?
VerifyMCP ran 15 checks on io.github.CloudCorpRecords/sweepdot, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/sweepdot: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.