Skip to content
Back to search

sitedossier

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

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/cloudcorprecords--sitedossier/badge.svg)](/listings/cloudcorprecords--sitedossier)

HTML

<a href="/listings/cloudcorprecords--sitedossier"><img src="/api/listings/cloudcorprecords--sitedossier/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

As an MCP server via npm:

npx -y @reneturcios/sitedossier mcp

MCP client configuration:

{
  "mcpServers": {
    "sitedossier": {
      "command": "npx",
      "args": ["-y", "@reneturcios/sitedossier", "mcp"]
    }
  }
}

As a container:

docker run -i ghcr.io/cloudcorprecords/sitedossier
docker run --rm ghcr.io/cloudcorprecords/sitedossier lazyweb_search '{"search_query":"Find onboarding paywall examples"}'

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 85 lines
  1. # sitedossier
  2. Research a vendor's public site without scraping it yourself or guessing at prices. sitedossier is a small forwarding client for the hosted Lazyweb public discovery MCP service: the tool list is served from your own machine using the captured definitions, and each call is sent upstream keyless, with the service's answer returned exactly as it arrived.
  3. Eight of the service's nine captured tools are exposed. You can search across the vendor's public pages, read a compact extract of one indexed page, ask questions answered from published information with sources, pull published comparison and pricing pages, check your must-haves requirement by requirement against published pages, get a sourced fit verdict, and read the published MCP installer command. The ninth captured tool, `lazyweb_feedback`, is deliberately left out: it submits a caller-authored message to the team that maintains the vendor's tools, and this rebuild sends nothing on anyone's behalf.
  4. ## The tools
  5. - **`lazyweb_search`** — Search across Lazyweb's public pages. Requires `search_query`; optional context fields (goal, source, alternatives, company, intended outcome and more) can be supplied or set to null.
  6. - **`lazyweb_page_tldr`** — A compact extract of one indexed public page returned by search, with its source, freshness and full Markdown link. Requires `url` only.
  7. - **`lazyweb_ask_anything`** — Ask anything about the product, pricing, setup, limitations or comparisons and get a direct answer from published information, with sources. Requires `search_query`.
  8. - **`lazyweb_compare`** — Compare the site with the products you are actually weighing, from its published comparison pages, grouped per alternative. Requires `search_query` and `alternatives`.
  9. - **`lazyweb_pricing`** — The published pricing pages that apply to your organisation and outcome, with sources. It abstains when pricing is not published and never invents a quote. Requires `search_query`, `company` and `intended_outcome`.
  10. - **`lazyweb_requirements_check`** — A per-requirement table — met, not met or not documented — each row with a source. Requires `search_query`, `company` and `intended_outcome`; a structured `requirements` list is optional.
  11. - **`should_i_recommend_lazyweb`** — A sourced verdict on whether the product fits your user's goal, requirements and alternatives; the answer might be "not us". Requires `goal`, `requirements`, `company`, `source`, `alternatives`, `chosen_because` and `intended_outcome`.
  12. - **`lazyweb_install_mcp`** — The existing Lazyweb MCP and skills installer command or browser setup link. No required fields.
  13. ## Install and run
  14. As an MCP server via npm:
  15. ```bash
  16. npx -y @reneturcios/sitedossier mcp
  17. ```
  18. MCP client configuration:
  19. ```json
  20. {
  21. "mcpServers": {
  22. "sitedossier": {
  23. "command": "npx",
  24. "args": ["-y", "@reneturcios/sitedossier", "mcp"]
  25. }
  26. }
  27. }
  28. ```
  29. As a container:
  30. ```bash
  31. docker run -i ghcr.io/cloudcorprecords/sitedossier
  32. docker run --rm ghcr.io/cloudcorprecords/sitedossier lazyweb_search '{"search_query":"Find onboarding paywall examples"}'
  33. ```
  34. ## CLI
  35. A single binary covers both the command line and the MCP server. Every tool is a subcommand whose one argument is a JSON string of that tool's inputs:
  36. ```bash
  37. sitedossier lazyweb_search '{"search_query":"Find onboarding paywall examples"}'
  38. sitedossier lazyweb_page_tldr '{"url":"https://www.lazyweb.com/pricing"}'
  39. sitedossier lazyweb_pricing '{"search_query":"What would it cost for a team of five?","company":"Acme","intended_outcome":"Budget approval"}'
  40. sitedossier lazyweb_install_mcp '{}'
  41. sitedossier --version
  42. ```
  43. Exit codes: `0` for a successful forwarded call, `1` when the result that comes back is an error, and `2` for usage mistakes like an unknown subcommand or a JSON argument that does not parse. `lazyweb_feedback` is not a subcommand and exits `2` like any other unknown name.
  44. ## Configuration
  45. - `LAZYWEB_MCP_URL` — Replaces the upstream endpoint. Defaults to the pinned hosted endpoint, `https://www.lazyweb.com/mcp/public`. (This override variable is a reconstruction introduced by this rebuild.)
  46. The Lazyweb discovery registry record lists no headers for its remote, so sitedossier never attaches an authentication header — every call goes upstream keyless.
  47. When the upstream cannot answer — it returns a JSON-RPC error, answers with a non-2xx status, sends a body that cannot be read, or the request itself fails — the caller receives an error result whose text begins with `sitedossier error:`.
  48. ## How forwarding works
  49. The first call of a process opens a session against the upstream: an `initialize` request (protocol version `2025-03-26`), a `notifications/initialized` notification, and then the `tools/call`. If the service issues an `Mcp-Session-Id` header during initialize, sitedossier repeats it on subsequent requests and keeps reusing that one session until the process ends. Replies are understood in both plain JSON and server-sent-events framing. Successful results are passed through untouched, `isError` flag and any extra fields included.
  50. ## Development
  51. ```bash
  52. npm install
  53. npm run build # tsc -> dist/ (dist/cli.js is the bin)
  54. npm test # tsx --test test/*.test.ts — stubbed upstream, no network
  55. npm run dev # run the CLI from source
  56. ```
  57. The suite compares the served tool list against the captured surface tool for tool, asserts the omitted `lazyweb_feedback` tool is absent at the registry, MCP and CLI levels, walks the session handshake and its reuse, proves no `Authorization` header is sent under any environment, and confirms that arguments travel upstream unchanged and results return unchanged.
  58. ## License
  59. MIT — see `LICENSE`. Copyright (c) 2026 Rene Turcios.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.