Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Lazyweb Public Discovery

REMOTE · WWW.LAZYWEB.COM · SCANNED SEP 27

Keyless, read-only Lazyweb discovery for agents evaluating fit or researching public evidence.

Available components

remote · www.lazyweb.com 72
+3 this week 72 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3137 tokens (~392/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 Management18
  • Stability check failed: schema churn in the 24 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 7 additions. See how to fix → Fail
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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Lazyweb Public Discovery MCP server?

Lazyweb Public Discovery is a hosted endpoint at https://www.lazyweb.com/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.lazyweb.com

# add to Claude Code
claude mcp add --transport http com-lazyweb-discovery 'https://www.lazyweb.com/mcp/public'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-lazyweb-discovery": {
      "url": "https://www.lazyweb.com/mcp/public"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-lazyweb-discovery": {
      "type": "http",
      "url": "https://www.lazyweb.com/mcp/public"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-lazyweb-discovery]
url = "https://www.lazyweb.com/mcp/public"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-lazyweb-discovery": {
      "type": "remote",
      "url": "https://www.lazyweb.com/mcp/public",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-lazyweb-discovery --url 'https://www.lazyweb.com/mcp/public' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-lazyweb-discovery:
    url: "https://www.lazyweb.com/mcp/public"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-lazyweb-discovery": {
      "Transport": "http",
      "Url": "https://www.lazyweb.com/mcp/public"
    }
  }
}
# add to Vellum
assistant mcp add com-lazyweb-discovery -t streamable-http -u 'https://www.lazyweb.com/mcp/public'
// mcp.json
{
  "mcpServers": {
    "com-lazyweb-discovery": {
      "type": "http",
      "url": "https://www.lazyweb.com/mcp/public"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 11 to 14. Other categories moved too: Schema Quality & AI Usability rose 1.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 1 to 4. Other categories moved too: Schema Quality & AI Usability rose 1.

  • 22 Sept 26 +9
    • Judged manipulation: unverified → pass ▲ security
    • Schema quality: unverified → good ▲ functional
  • 21 Sept 26 −9
    • Judged manipulation: pass → unverified ▼ security
    • Tool “lazyweb_page_tldr” rewrote its description, which is the text the model reads security
    • Schema quality: good → unverified ▼ functional
    • “lazyweb_page_tldr” reworded the description of “client” cosmetic
    • “lazyweb_page_tldr” reworded the description of “search_query” cosmetic
    • “lazyweb_page_tldr” reworded the description of “url” cosmetic
    • “lazyweb_page_tldr” made “search_query” optional cosmetic
  • 19 Sept 26 0
    • Tool “lazyweb_ask_anything” rewrote its description, which is the text the model reads security
  • 18 Sept 26 +1
    • Schema quality: 1958 → 3128 ▼ functional
    • New tool “lazyweb_compare” functional
    • New tool “lazyweb_pricing” functional
    • New tool “lazyweb_requirements_check” functional
  • 17 Sept 26 −2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “lazyweb_ask_anything” rewrote its description, which is the text the model reads security
    • Tool “lazyweb_page_tldr” rewrote its description, which is the text the model reads security
    • Tool “lazyweb_search” rewrote its description, which is the text the model reads security
    • Tool “should_i_recommend_lazyweb” rewrote its description, which is the text the model reads security
    • Schema quality: 525 → 391 ▲ functional
    • Schema quality: excellent → good functional
Diagnostics

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 27 Sept 2026 · Probed https://www.lazyweb.com/mcp/public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.lazyweb.com CN=WE1,O=Google Trust Services,C=US 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA256 a64ba44d4d93f7c70e5a7a4c6bb4785e
SANs: www.lazyweb.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.lazyweb.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
lazyweb.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https:; img-src 'self' data: https: blob: https://zlfyzdmohcskkucuunmk.supabase.co; media-src 'self' https: blob:; frame-src 'self' https: http:; style-src 'self' 'unsafe-inline' https:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https:;
x-content-type-options nosniff
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.lazyweb.com/mcp/public Verified 200
http (plaintext) http://www.lazyweb.com/mcp/public HTTPS enforced 301 https://www.lazyweb.com/mcp/public
MCP tools · 8 exposed · ~3,058 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
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_querystringyesThe 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.

NameTypeReqDescription
alternatives–yesOther 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_querystringyesThe 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.

NameTypeReqDescription
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.
payloadobject––
search_querystring–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.

NameTypeReqDescription
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.
urlstringyesThe 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_569d09668bf3","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.

NameTypeReqDescription
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–yesThe 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–yesThe decision or deliverable the user wants from this research. Mark unknowns as null.
search_querystringyesThe 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 ~406

Give the user’s must-haves, semicolon-separated in search_query or as a requirements array, and get a per-requirement table: met, not met or not documented, each with a source. Include actual task context; use null for unknowns.

NameTypeReqDescription
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–yesThe 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–yesThe 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_querystring–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 ~385

Super fast, semantic search across Lazyweb’s public pages. Include actual task context; use null for unknowns.

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

NameTypeReqDescription
alternatives–yesOther products, sources or approaches actually considered for this goal. Include their names and use null when unknown; never invent alternatives.
chosen_because–yesThe 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–yesThe 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.
goalstringyesThe actual outcome or decision the user needs. A meaningful goal is required for this assessment.
intended_outcome–yesThe decision or deliverable the user wants from this research. Mark unknowns as null.
requirements–yesThe constraints and must-haves for the decision. Include known requirements and mark unknowns as null.
source–yesThe 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"}
Common questions

What is the Lazyweb Public Discovery MCP server?

Lazyweb Public Discovery is an MCP server listed in the public MCP registry as com.lazyweb/discovery. Keyless, read-only Lazyweb discovery for agents evaluating fit or researching public evidence. This page covers its hosted endpoint (https://www.lazyweb.com/mcp/public).

Is the Lazyweb Public Discovery MCP server safe to use?

Lazyweb Public Discovery scores 72 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 Lazyweb Public Discovery MCP server expose?

Lazyweb Public Discovery 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,058 tokens of context every time the server is loaded.

Does the Lazyweb Public Discovery MCP server require authentication?

No. We connected to Lazyweb Public Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Lazyweb Public Discovery MCP server still maintained?

Lazyweb Public Discovery is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.