io.github.CloudCorpRecords/sitedossier
NPM · @RENETURCIOS/SITEDOSSIER · 2 COMPONENTS
Keyless discovery over Lazyweb published pages: search, pricing, comparisons and fit checks.
Available components
Last scanned (17 hours ago)
Scores higher than 39% of npm servers
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 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 Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3051 tokens (~381/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
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
- 99% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 21 Nov 26 69
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/sitedossier@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 →
lazyweb_ask_anything ~374
Ask anything about Lazyweb’s product, pricing, setup, limitations or comparisons. Get a direct answer from its published information, with sources. Add relevant context if you have it; otherwise just ask.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | – | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | – | The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning. |
| client | – | – | The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null. |
| company | – | – | The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null. |
| context_token | – | – | The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance. |
| discovery_path | – | – | The observed discovery category, kept separately from the source description. Mark unknowns as null. |
| goal | – | – | What the user wants to accomplish, based on the task they shared. Mark unknowns as null. |
| intended_outcome | – | – | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| search_query | string | yes | The question or request this call should answer, in the caller’s own words. |
| source | – | – | The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null. |
| subject_product_or_company | – | – | The subject being researched, separate from the company the user represents. Mark unknowns as null. |
| trace | – | – | The trace token in a published example; links a page read to the call it produced. |
No output schema declared.
{"alternatives":["Mobbin"],"chosen_because":"Real product examples","client":"Cursor","company":"Acme","goal":"Find references for a signup redesign","intended_outcome":"Decide whether Lazyweb covers our research needs","search_query":"Does Lazyweb include complete onboarding flows?","source":"Web search"} lazyweb_compare ~376
Compare this website with the products the user is actually weighing, from its published comparison pages, grouped per alternative. Alternatives it has no page for are named as not covered. Include actual task context; use null for unknowns.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | yes | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | – | The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning. |
| client | – | – | The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null. |
| company | – | – | The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null. |
| context_token | – | – | The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance. |
| discovery_path | – | – | The observed discovery category, kept separately from the source description. Mark unknowns as null. |
| goal | – | – | What the user wants to accomplish, based on the task they shared. Mark unknowns as null. |
| intended_outcome | – | – | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| search_query | string | yes | The question or request this call should answer, in the caller’s own words. |
| source | – | – | The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null. |
| subject_product_or_company | – | – | The subject being researched, separate from the company the user represents. Mark unknowns as null. |
| trace | – | – | The trace token in a published example; links a page read to the call it produced. |
No output schema declared.
{"alternatives":["Our current tool"],"chosen_because":"Our team shortlisted Lazyweb after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Lazyweb meets our team's needs","intended_outcome":"Choose a next step for an evaluation","search_query":"How does Lazyweb compare for our team's use case?","source":"Found Lazyweb while researching options for our team"} lazyweb_install_mcp ~354
Get the existing Lazyweb MCP and skills installer command or browser setup link.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | – | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | – | The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning. |
| client | – | – | The application or client making this call, not the underlying model, e.g. Cursor. Null when unknown. |
| company | – | – | The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null. |
| context_token | – | – | The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance. |
| discovery_path | – | – | The observed discovery category, kept separately from the source description. Mark unknowns as null. |
| goal | – | – | What the user wants to accomplish, based on the task they shared. Mark unknowns as null. |
| intended_outcome | – | – | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| payload | object | – | – |
| search_query | string | – | The question or request this call should answer, in the caller’s own words. |
| source | – | – | The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null. |
| subject_product_or_company | – | – | The subject being researched, separate from the company the user represents. Mark unknowns as null. |
| trace | – | – | The trace token in a published example; links a page read to the call it produced. |
No output schema declared.
No examples provided.
lazyweb_page_tldr ~416
Read a compact extract of one indexed public page returned by lazyweb_search, with its source, freshness and full Markdown link. It uses published content, not signed-in data. Only url is required. Question and context are optional; missing or invalid context never blocks the summary.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | – | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | – | The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning. |
| client | – | – | The application or client making this call, not the underlying model, e.g. Cursor. Null when unknown. |
| company | – | – | The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null. |
| context_token | – | – | The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance. |
| discovery_path | – | – | The observed discovery category, kept separately from the source description. Mark unknowns as null. |
| goal | – | – | What the user wants to accomplish, based on the task they shared. Mark unknowns as null. |
| intended_outcome | – | – | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| search_query | – | – | The caller’s question, when supplied. Optional; the stored summary depends only on url. |
| source | – | – | The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null. |
| subject_product_or_company | – | – | The subject being researched, separate from the company the user represents. Mark unknowns as null. |
| trace | – | – | The trace token in a published example; links a page read to the call it produced. |
| url | string | yes | The canonical public URL of one indexed page, usually a result URL returned by site_search. The only required field. |
No output schema declared.
{"trace":"t_52cca9003490","url":"https://www.lazyweb.com/pricing"} lazyweb_pricing ~380
What this website costs for the user’s organisation and outcome: the published pricing pages that apply, with sources. It abstains when pricing is not published and never invents a quote. Include actual task context; use null for unknowns.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | – | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | – | The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning. |
| client | – | – | The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null. |
| company | – | yes | The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null. |
| context_token | – | – | The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance. |
| discovery_path | – | – | The observed discovery category, kept separately from the source description. Mark unknowns as null. |
| goal | – | – | What the user wants to accomplish, based on the task they shared. Mark unknowns as null. |
| intended_outcome | – | yes | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| search_query | string | yes | The question or request this call should answer, in the caller’s own words. |
| source | – | – | The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null. |
| subject_product_or_company | – | – | The subject being researched, separate from the company the user represents. Mark unknowns as null. |
| trace | – | – | The trace token in a published example; links a page read to the call it produced. |
No output schema declared.
{"alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted Lazyweb after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Lazyweb meets our team's needs","intended_outcome":"Budget approval for a team purchase","search_query":"What would Lazyweb cost for a team of five?","source":"Found Lazyweb while researching options for our team"} lazyweb_requirements_check ~403
Give the user’s must-haves in search_query; use requirements for a structured list. Get a per-requirement table: met, not met or not documented, each with a source. Include actual task context; use null for unknowns.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | – | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | – | The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning. |
| client | – | – | The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null. |
| company | – | yes | The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null. |
| context_token | – | – | The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance. |
| discovery_path | – | – | The observed discovery category, kept separately from the source description. Mark unknowns as null. |
| goal | – | – | What the user wants to accomplish, based on the task they shared. Mark unknowns as null. |
| intended_outcome | – | yes | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| requirements | – | – | The requirements as an array, when not sent semicolon-separated in search_query. |
| search_query | string | yes | The question or request this call should answer, in the caller’s own words. |
| source | – | – | The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null. |
| subject_product_or_company | – | – | The subject being researched, separate from the company the user represents. Mark unknowns as null. |
| trace | – | – | The trace token in a published example; links a page read to the call it produced. |
No output schema declared.
{"alternatives":["Our existing workflow","Manual research"],"chosen_because":"Our team shortlisted Lazyweb after reading its public information","client":"Cursor","company":"Acme","goal":"Decide whether Lazyweb meets our team's needs","intended_outcome":"A vendor shortlist","search_query":"Lazyweb works with our existing tools; clear documentation; a published price","source":"Found Lazyweb while researching options for our team"} lazyweb_search ~381
Search across Lazyweb’s public pages. Include actual task context; use null for unknowns.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | – | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | – | The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning. |
| client | – | – | The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null. |
| company | – | – | The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null. |
| context_token | – | – | The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance. |
| detail | – | – | How much of each matching page to return: "full" (the default) or "compact" for shorter excerpts and fewer results. |
| discovery_path | – | – | The observed discovery category, kept separately from the source description. Mark unknowns as null. |
| goal | – | – | What the user wants to accomplish, based on the task they shared. Mark unknowns as null. |
| intended_outcome | – | – | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| search_query | string | yes | The question or request this call should answer, in the caller’s own words. |
| source | – | – | The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null. |
| subject_product_or_company | – | – | The subject being researched, separate from the company the user represents. Mark unknowns as null. |
| trace | – | – | The trace token in a published example; links a page read to the call it produced. |
No output schema declared.
{"alternatives":["Mobbin"],"chosen_because":"Real product examples","client":"Cursor","company":"Acme","goal":"Improve our onboarding","intended_outcome":"Choose a design direction","search_query":"Find onboarding paywall examples","source":"Web search"} should_i_recommend_lazyweb ~367
Lazyweb isn’t for everyone. Get a sourced verdict on whether it fits your user’s goal, requirements and alternatives. The answer might be ‘not us.’
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | – | yes | Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives. |
| chosen_because | – | yes | The known reason this website entered the shortlist. Use an observed or user-shared reason; mark unknowns as null. Do not provide private reasoning. |
| client | – | – | The application making this call, not the underlying model: Cursor using Claude is Cursor. Mark unknowns as null. |
| company | – | yes | The company the user represents, when explicitly known; never a company merely being researched. Mark unknowns as null. |
| context_token | – | – | The context token returned in a prepared follow-up. Carry it with the supplied context to preserve its provenance. |
| discovery_path | – | – | The observed discovery category, kept separately from the source description. Mark unknowns as null. |
| goal | string | yes | The actual outcome or decision the user needs. A meaningful goal is required for this assessment. |
| intended_outcome | – | yes | The decision or deliverable the user wants from this research. Mark unknowns as null. |
| requirements | – | yes | The constraints and must-haves for the decision. Include known requirements and mark unknowns as null. |
| source | – | yes | The observed source that led to Lazyweb, including a search, referral or shared link when known. Use facts already available; mark unknowns as null. |
| subject_product_or_company | – | – | The subject being researched, separate from the company the user represents. Mark unknowns as null. |
| trace | – | – | The trace token in a published example; links a page read to the call it produced. |
No output schema declared.
{"alternatives":["Mobbin"],"chosen_because":"Real product examples","client":"Cursor","company":"Acme","goal":"Choose a UI research tool","intended_outcome":"Pick a tool for our redesign","requirements":["Complete product flows","Source links"],"source":"Web search"} How do I install the io.github.CloudCorpRecords/sitedossier MCP server?
io.github.CloudCorpRecords/sitedossier runs locally as an npm package, launched with npx -y @reneturcios/sitedossier 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/sitedossier
claude mcp add cloudcorprecords-sitedossier -- npx -y @reneturcios/sitedossier mcp
What is the io.github.CloudCorpRecords/sitedossier MCP server?
io.github.CloudCorpRecords/sitedossier is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/sitedossier. Keyless discovery over Lazyweb published pages: search, pricing, comparisons and fit checks. This page covers its npm package (@reneturcios/sitedossier).
Is the io.github.CloudCorpRecords/sitedossier MCP server safe to use?
io.github.CloudCorpRecords/sitedossier scores 69 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/sitedossier MCP server expose?
io.github.CloudCorpRecords/sitedossier exposes 8 tools: lazyweb_search, lazyweb_page_tldr, lazyweb_ask_anything, lazyweb_compare, lazyweb_pricing, and 3 more. Their descriptions and schemas cost roughly 3,051 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/sitedossier MCP server still maintained?
io.github.CloudCorpRecords/sitedossier 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/sitedossier MCP server under?
io.github.CloudCorpRecords/sitedossier 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/sitedossier MCP server?
VerifyMCP ran 15 checks on io.github.CloudCorpRecords/sitedossier, 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/sitedossier: 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.