io.github.CloudCorpRecords/domainledger
NPM · @RENETURCIOS/DOMAINLEDGER · 2 COMPONENTS
Live RDAP domain availability with registration prices, brand scores and resale estimates.
Available components
Last scanned (21 hours ago)
Scores higher than 44% 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 Usability84
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 312 tokens (~156/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 16 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Nov 26 57
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/domainledger@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 ~198
Check whether domain names are actually available to register, using live registry (RDAP) data. Use this when suggesting domain names (verify availability before presenting them, never assume a name is unregistered) or when the user asks whether specific domains are available. Accepts up to 50 fully-qualified domains (e.g. 'brewlog.app'). Returns availability, the registrar for taken domains, a 0-100 brandability score, an estimated resale value, the price in USD (price_usd for term_years, quote it rather than estimating; price_source 'checkout' is the expected charge at buy_url, confirmed before payment), and buy_url, the domhaul checkout page where the user can purchase the domain. If too few names are available, generate more candidates and call again.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Fully-qualified domain names to check, e.g. ['brewlog.app', 'getbrewlog.com']. Max 50. |
No output schema declared.
No examples provided.
get_tld_prices Get TLD Registration Prices ~114
Get registrar retail first-year price estimates in USD for top-level domains (.com, .io, .app, .dev, .ai, …). Use this when the user is comparing TLD options, e.g. 'should I get the .com or the .io?'. For the exact purchase price of a specific domain, use check_domains instead.
| Name | Type | Req | Description |
|---|---|---|---|
| tlds | array | yes | TLDs to price, with or without the leading dot, e.g. ['com', '.io', 'app'] |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/domainledger MCP server?
io.github.CloudCorpRecords/domainledger runs locally as an npm package, launched with npx -y @reneturcios/domainledger 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/domainledger
claude mcp add cloudcorprecords-domainledger -- npx -y @reneturcios/domainledger mcp
What is the io.github.CloudCorpRecords/domainledger MCP server?
io.github.CloudCorpRecords/domainledger is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/domainledger. Live RDAP domain availability with registration prices, brand scores and resale estimates. This page covers its npm package (@reneturcios/domainledger).
Is the io.github.CloudCorpRecords/domainledger MCP server safe to use?
io.github.CloudCorpRecords/domainledger scores 72 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/domainledger MCP server expose?
io.github.CloudCorpRecords/domainledger exposes 2 tools: check_domains, get_tld_prices. Their descriptions and schemas cost roughly 312 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/domainledger MCP server still maintained?
io.github.CloudCorpRecords/domainledger 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/domainledger MCP server under?
io.github.CloudCorpRecords/domainledger 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/domainledger MCP server?
VerifyMCP ran 15 checks on io.github.CloudCorpRecords/domainledger, 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/domainledger: 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.