mcpbeat Sign in

Lazyweb Public Discovery MCP Server

answering

Lazyweb Public Discovery is answering right now. Last checked 7 min ago. It exposes 9 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 53 days of history · worst day 90%
53 days agonow
100.0%
Uptime 24h
91 of 91 checks
9
Tools
read from the server
590 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 87

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 September 2026. No other catalogue keeps this.

20 Oct 2 tool descriptions were rewritten lazyweb_requirements_check, lazyweb_search
20 Oct a tool changed the parameters it asks for lazyweb_requirements_check
10 Oct a tool changed the parameters it asks for lazyweb_page_tldr
29 Sep a tool appeared lazyweb_feedback
26 Sep 8 tools changed the parameters they ask for lazyweb_ask_anything, lazyweb_compare, lazyweb_install_mcp and 5 more
25 Sep a tool changed the parameters it asks for lazyweb_install_mcp
22 Sep 2 tools changed the parameters they ask for lazyweb_pricing, lazyweb_requirements_check
21 Sep a tool description was rewritten lazyweb_page_tldr
21 Sep a tool changed the parameters it asks for lazyweb_page_tldr
18 Sep 3 tools appeared lazyweb_compare, lazyweb_pricing, lazyweb_requirements_check
and 66 more, back to 6 September 2026

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add discovery --transport http https://www.lazyweb.com/mcp/public
Settings → Connectors → Add custom connector, then paste this address
https://www.lazyweb.com/mcp/public
~/.codex/config.toml
[mcp_servers.discovery]
url = "https://www.lazyweb.com/mcp/public"
.cursor/mcp.json
{
  "mcpServers": {
    "discovery": {
      "url": "https://www.lazyweb.com/mcp/public"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "discovery": {
      "type": "http",
      "url": "https://www.lazyweb.com/mcp/public"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lazyweb
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 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.
lazyweb_search
Search across Lazyweb’s public pages. Include actual task context; use null for unknowns.
should
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.’

Endpoints

URLTransportStateLatencyChecked
https://www.lazyweb.com/mcp/public streamable-http answering 447 ms 7 min ago

Alternatives to Lazyweb Public Discovery

same job, measured the same way
Machine Realms
by galanai

Machine-native research commons for agent evidence, discovery, rooms, and bounded research quests.

9 tools answering
Jev Filter
by apixly-ai

Read-only semantic filtering, code search, log triage and traceable evidence for AI agents.

10 installs/wk local only
Did It Work?
by diditwork

Charity evidence for AI agents: cited evaluator figures, caveats and an outcome ledger. Read-only.

20 tools answering
VouchSpec Agent Skill Evidence
by mordiaky

Read-only discovery for exact-commit Agent Skill validation, x402 payment, and signed receipts.

answering
DataPulse
by r3dz4r

Read-only discovery for 440 Malaysian public datasets with freshness, licence, and provenance.

19 tools answering
Poisar Public
by poisar

Read-only public metadata server for Poisar discovery.

2 tools answering
WeSupport-AI
by petros-poli

Read-only AICS onboarding, agent discovery, public forum, identity and transparency-log tools.

830 installs/wk local only
Crawdar Business Research
by crawdar

Evidence-backed public business research for agents with compact, pageable output.

10 tools answering

Lazyweb Public Discovery — questions

Answers built from our own checks of this server.

What can Lazyweb Public Discovery do?
It exposes 9 tools, read directly from the server on our last check. Among them: lazyweb_ask_anything, lazyweb_compare, lazyweb_feedback, lazyweb_install_mcp, lazyweb_page_tldr, lazyweb_pricing and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Lazyweb Public Discovery working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 590 ms. The bar chart above shows every period we have measured.
Is Lazyweb Public Discovery still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Lazyweb Public Discovery?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Lazyweb Public Discovery need an API key?
No. Lazyweb Public Discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Lazyweb Public Discovery?
It answers our handshake in 590 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.