io.github.CloudCorpRecords/domaintrack
NPM · @RENETURCIOS/DOMAINTRACK · 2 COMPONENTS
Look up domain reputation snapshots and AI crawler policy from Domduck's public store.
Available components
Last scanned (19 hours ago)
Scores higher than 40% of npm servers
Category Security
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
- 30 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 274 tokens (~91/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.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.
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 71
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 4 Nov 2026 · Analysed npm/@reneturcios/domaintrack@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 | 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 →
get_ai_crawler_policy Get AI crawler policy ~110
Which of the eight tracked AI crawlers a domain's robots.txt admits, and whether it publishes an llms.txt. Three states per agent: allowed, disallowed, unspecified. Unspecified is NOT allowed, because a catch-all Disallow blocks an agent the file never names, so read `effective` for what is in force. Reads the last stored reading; it does not fetch the file.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain name. Scheme, www and trailing dots are stripped. |
No output schema declared.
No examples provided.
list_sources List data sources ~59
What Domduck reads and what each source means, including the eight AI crawlers whose robots.txt policy is tracked. A constant. Read it first: it is what lets a model interpret lookup_domain without guessing at field names or at which direction is better.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_domain Look up one domain ~105
Public reputation snapshot for one domain from Domduck's store: Domain Rating, Tranco rank, OpenPageRank, registration date, TLS certificate state and AI crawler policy. Returns hasReading false for a domain nobody has looked up yet, which is a real answer and not an error. One domain per call, and no history: the dated series is what a Domduck account is for.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A domain name. Scheme, www and trailing dots are stripped. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/domaintrack MCP server?
io.github.CloudCorpRecords/domaintrack runs locally as an npm package, launched with npx -y @reneturcios/domaintrack. 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/domaintrack
claude mcp add cloudcorprecords-domaintrack -- npx -y @reneturcios/domaintrack
What is the io.github.CloudCorpRecords/domaintrack MCP server?
io.github.CloudCorpRecords/domaintrack is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/domaintrack. Look up domain reputation snapshots and AI crawler policy from Domduck's public store. This page covers its npm package (@reneturcios/domaintrack).
Is the io.github.CloudCorpRecords/domaintrack MCP server safe to use?
io.github.CloudCorpRecords/domaintrack scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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/domaintrack MCP server expose?
io.github.CloudCorpRecords/domaintrack exposes 3 tools: lookup_domain, get_ai_crawler_policy, list_sources. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/domaintrack MCP server still maintained?
io.github.CloudCorpRecords/domaintrack is still listed as active in the MCP registry. We last reached this channel on 4 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/domaintrack MCP server under?
io.github.CloudCorpRecords/domaintrack declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.