Developer · Remote MCP server
Lazyweb
Real product evidence: 281k+ real app screens and flows, 20k+ mobile A/B tests, growth reports.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.lazyweb/lazyweb- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-28
- Updated
- 2026-08-28
- Publisher
- com.lazyweb · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain lazyweb.com · how
- Website
- www.lazyweb.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://www.lazyweb.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Lazyweb
Lazyweb is a remote MCP server: there is nothing to install. Its endpoint is https://www.lazyweb.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.lazyweb
| Server | Runs |
|---|---|
| Lazyweb Public DiscoveryKeyless, read-only Lazyweb discovery for agents evaluating fit or researching public evidence. | Remote · HTTPLive check: ✓ handshake |
More developer servers
| Server | Runs |
|---|---|
| LaunchFlagFeature flags and kill switches. Turn a shipped feature off in production without a deploy. | Remote & Local · HTTP, stdioLive check: sign-in required |
| LaunchTrustCompliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure. | Remote · HTTPLive check: ✓ handshake |
| Lawang OnboardPermission-aware onboarding MCP server: answers about a codebase, filtered by the caller's role. | Remote & Local · HTTP, stdioLive check: sign-in required |
| LayeroDeploy and operate sites on Layero - hosting with build servers in Russia: domains, env, Data API. | Remote · HTTPLive check: ✓ handshake |
| LBrainLocal-first agent memory. Source, date, bind/abstain. Permanent name: lbrain.ai/claim.html. | Local · stdio |
| LDAP Assistant MCPMCP server for 389 Directory Server health diagnostics, log analysis, and SOS-report investigation. | Local · stdio |
| LeakRank GuardScans code changes for leaked secrets and insecure config, with actionable fixes for AI agents. | Local · stdio |
| Lean ReaderToken-minimized URL-to-clean-text reader for LLMs, with a token-savings receipt. | Local · stdio |