# Lazyweb Public Discovery

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

- name: com.lazyweb/discovery
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 92/100
- quality: 90/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.lazyweb%2Fdiscovery
- tools: https://api.protogrid.dev/v1/servers/com.lazyweb%2Fdiscovery/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "discovery": {
      "type": "http",
      "url": "https://www.lazyweb.com/mcp/public"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 85
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-97% ~updated-47d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 90/100 (strong)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 9 of 9 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 7,787 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 75 (weight 15)

- warn `stability.changes`: 11 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 9, about 7,787 tokens to load them all
- tool set hash: 3003fd8038206acb361d94ac0ff2ec47
- tools last changed: 2026-10-10T06:05:22.986Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.lazyweb/discovery.svg)](https://protogrid.dev/servers/com.lazyweb/discovery)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-10 `lazyweb_page_tldr` changed (inputSchema)
- 2026-09-29 `lazyweb_feedback` added
  - Report a bug, a missing feature, a wrong answer or unclear docs in Lazyweb’s agent tools, right when you hit it. Only kind and message are required. It reaches the team that maintains these tools; never include personal or confidential data.
- 2026-09-26 `lazyweb_install_mcp` changed (inputSchema)
- 2026-09-26 `should_i_recommend_lazyweb` changed (inputSchema)
- 2026-09-26 `lazyweb_requirements_check` changed (inputSchema)
- 2026-09-26 `lazyweb_pricing` changed (inputSchema)
- 2026-09-26 `lazyweb_compare` changed (inputSchema)
- 2026-09-26 `lazyweb_ask_anything` changed (inputSchema)
- 2026-09-26 `lazyweb_page_tldr` changed (inputSchema)
- 2026-09-26 `lazyweb_search` changed (inputSchema)

Full history: https://api.protogrid.dev/v1/servers/com.lazyweb%2Fdiscovery/changes

## Remotes

- https://www.lazyweb.com/mcp/public (streamable-http, auth none, reachable true, uptime30d 0.9741379)

## Packages

_none_

## Tools (9)

- `lazyweb_ask_anything`: 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.
- `lazyweb_compare`: 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.
- `lazyweb_feedback`: Report a bug, a missing feature, a wrong answer or unclear docs in Lazyweb’s agent tools, right when you hit it. Only kind and message are required. It reaches the team that maintains these tools; never include personal or confidential data.
- `lazyweb_install_mcp`: Get the existing Lazyweb MCP and skills installer command or browser setup link.
- `lazyweb_page_tldr`: 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.
- `lazyweb_pricing`: 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.
- `lazyweb_requirements_check`: 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.
- `lazyweb_search`: Super fast, semantic search across Lazyweb’s public pages. Include actual task context; use null for unknowns.
- `should_i_recommend_lazyweb`: 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.’