# io.github.CloudCorpRecords/sitedossier (oci · ghcr.io/cloudcorprecords/sitedossier)

Keyless discovery over Lazyweb published pages: search, pricing, comparisons and fit checks.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/sitedossier`: 69/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-sitedossier/reneturcios-sitedossier.md), [page](https://verifymcp.io/servers/cloudcorprecords-sitedossier/reneturcios-sitedossier)
- oci · `ghcr.io/cloudcorprecords/sitedossier`: 39/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-sitedossier/ghcr-io-cloudcorprecords-sitedossier.md), [page](https://verifymcp.io/servers/cloudcorprecords-sitedossier/ghcr-io-cloudcorprecords-sitedossier)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/sitedossier`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - 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.
  - Tools include usage examples.
- **Stability & Change Management**: 0/100
  - Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 99% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: 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.

## Install

### How do I install the io.github.CloudCorpRecords/sitedossier MCP server?

io.github.CloudCorpRecords/sitedossier runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/sitedossier:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-sitedossier -- docker run --rm -i ghcr.io/cloudcorprecords/sitedossier:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-sitedossier": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/sitedossier:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-sitedossier": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/sitedossier:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-sitedossier -- docker run --rm -i ghcr.io/cloudcorprecords/sitedossier:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-sitedossier": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/sitedossier:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-sitedossier:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/sitedossier:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-sitedossier": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/sitedossier:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-sitedossier": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/sitedossier:0.1.0",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 39)

First indexed and scored.

## MCP tools (8)

### `lazyweb_search` (~381 tokens)

Search across Lazyweb’s public pages. Include actual task context; use null for unknowns.

Input parameters:

- `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, required): 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.

### `lazyweb_page_tldr` (~416 tokens)

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.

Input parameters:

- `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, required): The canonical public URL of one indexed page, usually a result URL returned by site_search. The only required field.

### `lazyweb_ask_anything` (~374 tokens)

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.

Input parameters:

- `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, required): 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.

### `lazyweb_compare` (~376 tokens)

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.

Input parameters:

- `alternatives` (required): 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, required): 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.

### `lazyweb_pricing` (~380 tokens)

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.

Input parameters:

- `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` (required): 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` (required): The decision or deliverable the user wants from this research. Mark unknowns as null.
- `search_query` (string, required): 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.

### `lazyweb_requirements_check` (~403 tokens)

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.

Input parameters:

- `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` (required): 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` (required): 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, required): 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.

### `should_i_recommend_lazyweb` (~367 tokens)

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.’

Input parameters:

- `alternatives` (required): Other products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
- `chosen_because` (required): 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` (required): 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, required): The actual outcome or decision the user needs. A meaningful goal is required for this assessment.
- `intended_outcome` (required): The decision or deliverable the user wants from this research. Mark unknowns as null.
- `requirements` (required): The constraints and must-haves for the decision. Include known requirements and mark unknowns as null.
- `source` (required): 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.

### `lazyweb_install_mcp` (~354 tokens)

Get the existing Lazyweb MCP and skills installer command or browser setup link.

Input parameters:

- `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.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-sitedossier/ghcr-io-cloudcorprecords-sitedossier#diagnostics

## Score history

- 2026-11-21: 39

## Common questions

### 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 container image (ghcr.io/cloudcorprecords/sitedossier).

### Is the io.github.CloudCorpRecords/sitedossier MCP server safe to use?

io.github.CloudCorpRecords/sitedossier scores 39 out of 100 on VerifyMCP. 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 11 checks on io.github.CloudCorpRecords/sitedossier, covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/sitedossier: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/sitedossier
- Repository: https://github.com/CloudCorpRecords/sitedossier
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-sitedossier/ghcr-io-cloudcorprecords-sitedossier.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-sitedossier/ghcr-io-cloudcorprecords-sitedossier/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-sitedossier/ghcr-io-cloudcorprecords-sitedossier.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-sitedossier/ghcr-io-cloudcorprecords-sitedossier
