[APP] Lazyweb — real product evidence for agents (hosted MCP + OAuth, first-party request)

**Name of app / service**

Lazyweb (https://www.lazyweb.com) — real product evidence for UI and growth decisions: 281k+ real app screens and flows, 20k+ mobile A/B tests with outcomes, growth scores, growth reports, and a growth backlog. This is a first-party request (I'm the cofounder) under your App Partner program — happy to provide everything your integrations team needs.

**Link to developer documentation**

- Hosted MCP server (Streamable HTTP, self-describing tool schemas): `https://www.lazyweb.com/mcp`
- Official MCP Registry entry: https://registry.modelcontextprotocol.io/v0.1/servers?search=lazyweb (`com.lazyweb/lazyweb`)
- OAuth 2.1: RFC 8414 metadata at https://www.lazyweb.com/.well-known/oauth-authorization-server (authorization code + PKCE S256, Dynamic Client Registration at `/mcp-oauth/register`, refresh tokens; RFC 9728 resource metadata at https://www.lazyweb.com/.well-known/oauth-protected-resource/mcp)
- A fully featured, MFA-free test account is ready for your team — credentials shared privately via your support channel on request.

**Is lack of support preventing you from moving forward, or do you have a workaround?**

Workaround exists (users can consume the hosted MCP directly — it's live in the Anthropic and OpenAI directories, both in review), but a native Pipedream integration would put Lazyweb in front of Pipedream Connect products where our users already are.

**Are there specific actions or triggers you'd like to see for this app?**

Suggested actions (map 1:1 to existing authenticated endpoints/tools):
1. **Search App Screens** — query the screenshot corpus (filters: category, company, pattern)
2. **Search Mobile A/B Tests** — real experiments with tested change + outcome
3. **Add Growth Backlog Spec** — append a growth idea to the account's backlog (idempotency-keyed)

Suggested polling triggers:
1. **New Growth Report completed**
2. **Proposal decision recorded** (human approved/rejected a UI-change proposal)
3. **New Growth Backlog spec added**

Contact: ali@lazyweb.com — we can also open a shared channel with your integrations team.

Start by reviewing the Lazyweb hosted MCP and OAuth documentation linked in the issue, then inspect the repository's existing app integration patterns; no specific files or tests are named. Done means a native Pipedream integration covering the three suggested actions and three polling triggers, with the provided test account used for verification.

Written by the indexing model from the issue text.