# Screenrove

> Real product UI captures (onboarding, pricing, in-app screens) with design guides for coding agents.

- name: com.screenrove/screenrove
- version: 1.1.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 72/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.screenrove%2Fscreenrove
- tools: https://api.protogrid.dev/v1/servers/com.screenrove%2Fscreenrove/tools

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

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "screenrove": {
      "type": "http",
      "url": "https://screenrove.com/mcp"
    }
  }
}
```


## Trust

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

## Quality 72/100 (needs work)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### 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: 93 (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`: 13 of 13 tools declare readOnlyHint or destructiveHint
- warn `tools.directory_hints`: 1 of 13 tools declare all four hints; missing: build_handoff (idempotentHint); compare_screens (idempotentHint); get_flow (idempotentHint); …
- pass `tools.token_cost`: about 3,240 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 25 (weight 15)

- warn `stability.changes`: 13 tool changes in 30 days
- fail `stability.rug_pull`: 6 tools kept their name but changed most of their description in 30 days; review before trusting them

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

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

- tools: 13, about 3,240 tokens to load them all
- tool set hash: 3a669e946bff22f314a415351ca7e614
- tools last changed: 2026-10-01T12:08:21.280Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.screenrove/screenrove.svg)](https://protogrid.dev/servers/com.screenrove/screenrove)
- 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-01 `wait_for_pick` changed (description, outputSchema, annotations)
  - before: Wait for the user to choose on the pick page. Returns as soon as they click, or status pending after the wait; call again if so. Once chosen, returns their reference with its screenshot and a full build prompt, so you can start building from it.
  - after: Wait for the user to choose on the pick page. Long-polls up to 50 seconds—returns as soon as they click, or status "pending" after the wait (call again if so). Once chosen, returns their reference with its screenshot and a full build prompt, so you can start building from it immediately. If they clicked "None of these fit", status is "dismissed" and you should ask what they want instead.
- 2026-10-01 `search_screens` changed (description, inputSchema, outputSchema, annotations) **meaning changed**
  - before: Search every captured screen by keyword across titles, notes, page sections and observed actions. Filter by product or kind. Use this to find references like "pricing page", "empty state" or "date picker".
  - after: Search the UI reference catalog by keyword across titles, notes, page sections, and observed actions. Filter by product or kind (flow/marketing/product). Use this to find design pattern examples like "pricing page", "empty state", "date picker", "onboarding step", "checkout form", "dashboard", "sign-up", "settings", etc. Returns the best matches with screen IDs you can pass to getScreen or getScreenImage.
- 2026-10-01 `pick_reference` changed (description, inputSchema, outputSchema)
  - before: Show the user a few matching references side by side in their browser and let them click the one to build from. Prefer this over sending full-page images whenever the user should decide. Returns a url: open it for them (run `open <url>` on macOS, `xdg-open <url>` on Linux, or show the link), tell them to choose, then call waitForPick with the pickId.
  - after: Show the user several matching UI references side by side in their browser and let them click the one to build from. Returns a URL to open for them. Prefer this over sending full-page images whenever the user should decide which reference to use. The picker shows real screenshots at scroll depth so they can evaluate long pages. After calling this, tell them to choose in the picker, then call waitForPick with the pickId to get their choice and a complete build prompt.
- 2026-10-01 `list_products` changed (description, outputSchema, annotations) **meaning changed**
  - before: List every product in the library with its capture date, tags, coverage notes and screen counts. Start here to see what references exist.
  - after: List every product in the UI reference catalog with its capture date, tags, coverage notes and screen counts. Start here to see what competitor products, design systems, and UI patterns are available. Products include: Linear, Cursor, Vercel, Airbnb, Stripe, Duolingo, Notion, Raycast, Cal.com, Framer, and Supabase. Each has captured onboarding flows, marketing pages, and/or in-app screens.
- 2026-10-01 `list_flows` added
  - List every captured user journey: onboarding flows, signup sequences, checkout processes, booking flows, and marketplace explorations. Shows step counts, flow type, and observed transitions between steps. Use this to find complete user journey references—not just individual screens—so you can see how products guide users through multi-step processes like signup, onboarding, or checkout.
- 2026-10-01 `get_screen_image` changed (description, annotations)
  - before: Get the screenshot itself so you can look at it. For marketing pages taller than 4000px, preview returns only the first screen (above the fold); use size=full for the whole page, which can exceed what vision models accept. getScreen lists the page's sections with their y offsets.
  - after: Get the actual screenshot so you can see the UI. For marketing pages taller than 4000px, preview returns only the first screen (above the fold); use size=full for the whole page, which can exceed what vision models accept. getScreen lists the page's sections with their y offsets so you know what's below the fold.
- 2026-10-01 `get_screen` changed (description, outputSchema, annotations)
  - before: Get everything recorded about one screen: notes, source URL, image URLs and dimensions, observed actions and where they lead, and page sections for long pages.
  - after: Get everything recorded about one screen: notes on what it does and how it's laid out, source URL, image URLs and dimensions, observed actions and where they lead, and page sections for long marketing pages. Use this to understand a specific UI pattern in detail before building something similar.
- 2026-10-01 `get_product` changed (description, outputSchema, annotations) **meaning changed**
  - before: Get a product's coverage notes, design summary and every screen it contains, grouped into the onboarding flow, marketing pages and in-product screens.
  - after: Get a product's full collection: coverage notes, design summary, and every captured screen grouped into onboarding flow, marketing pages, and in-product screens. Use this to explore a competitor's complete UI: their signup flow, pricing page, dashboard, settings, and other screens. Each screen has notes and an image URL.
- 2026-10-01 `get_flow` added
  - Get the complete onboarding flow for a product: every step in order with titles, notes on what happens, observed transitions (button labels and where they lead), and which steps are alternate branches. Includes the handoff reference id to use with buildHandoff. Use this to study how a competitor structures their signup and onboarding, what information they collect at each step, and how they guide users to activation.
- 2026-10-01 `get_design` changed (description, outputSchema, annotations) **meaning changed**
  - before: Get the measured design guide for a product: font, palette, type scale, layout and component notes. Marketing site and product UI are measured separately.
  - after: Get the measured design guide for a product: observed font families, color palette, type scale, layout patterns, spacing values, and component observations. Marketing site and product UI are measured separately. Use this when you want to match a competitor's design system, understand their visual language, or borrow their typography and color choices for your own project.

Full history: https://api.protogrid.dev/v1/servers/com.screenrove%2Fscreenrove/changes

## Remotes

- https://screenrove.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.97590363)

## Packages

_none_

## Tools (13)

- `build_handoff`: Generate a complete build prompt for a coding agent: ordered screens with notes, observed
transitions, full-resolution image URLs, the measured design guide, and an implementation
checklist. This is the same prompt as the "Use in agent" button on the site.

Reference IDs: use `{product}-onboarding` for a product's signup flow, `{product}-collection`
for all their screens, or any single screen id (like `linear-marketing-pricing`).

Use this when you want to build UI that follows a real product's patterns. The prompt includes
everything an agent needs: screenshots to reference, design tokens to match, and implementation
steps to follow.
- `check_my_ui`: Compare the user's UI structure against Screenrove's catalog of real products. Describe what
the user has (screen type, sections, flow steps, plan count) and get a report showing the
closest real-world references with factual comparisons.

Use only the fields the user provides; leave out personal names, pricing, or customer data.
The report includes step counts, section counts, observed actions, and factual comparisons—
not recommendations.

Use this when the user wants to validate their UI against real products, understand if their
flow has more or fewer steps than competitors, or see how similar screens are structured.
- `compare_screens`: Compare two captured screens side by side: layout structure, page sections, observed actions,
dimensions, screen types, and design guide differences. Returns a structured comparison with
similarities, differences, and factual observations.

Use this when the user wants to understand how two products approach the same problem
differently—e.g. comparing Linear's pricing page with Stripe's pricing page, or Vercel's
onboarding with Notion's onboarding.

You can also compare one screen against a target description to see how close a reference
matches what the user is trying to build.
- `get_design`: Get the measured design guide for a product: observed font families, color palette, type scale,
layout patterns, spacing values, and component observations. Marketing site and product UI
are measured separately.

Use this when you want to match a competitor's design system, understand their visual language,
or borrow their typography and color choices for your own project.
- `get_flow`: Get the complete onboarding flow for a product: every step in order with titles, notes on
what happens, observed transitions (button labels and where they lead), and which steps are
alternate branches. Includes the handoff reference id to use with buildHandoff.

Use this to study how a competitor structures their signup and onboarding, what information
they collect at each step, and how they guide users to activation.
- `get_product`: Get a product's full collection: coverage notes, design summary, and every captured screen
grouped into onboarding flow, marketing pages, and in-product screens.

Use this to explore a competitor's complete UI: their signup flow, pricing page, dashboard,
settings, and other screens. Each screen has notes and an image URL.
- `get_screen`: Get everything recorded about one screen: notes on what it does and how it's laid out, source
URL, image URLs and dimensions, observed actions and where they lead, and page sections for
long marketing pages.

Use this to understand a specific UI pattern in detail before building something similar.
- `get_screen_image`: Get the actual screenshot so you can see the UI. For marketing pages taller than 4000px,
preview returns only the first screen (above the fold); use size=full for the whole page,
which can exceed what vision models accept. getScreen lists the page's sections with their
y offsets so you know what's below the fold.
- `list_flows`: List every captured user journey: onboarding flows, signup sequences, checkout processes,
booking flows, and marketplace explorations. Shows step counts, flow type, and observed
transitions between steps.

Use this to find complete user journey references—not just individual screens—so you can
see how products guide users through multi-step processes like signup, onboarding, or checkout.
- `list_products`: List every product in the UI reference catalog with its capture date, tags, coverage notes
and screen counts. Start here to see what competitor products, design systems, and UI
patterns are available.

Products include: Linear, Cursor, Vercel, Airbnb, Stripe, Duolingo, Notion, Raycast, Cal.com,
Framer, and Supabase. Each has captured onboarding flows, marketing pages, and/or in-app screens.
- `pick_reference`: Show the user several matching UI references side by side in their browser and let them click
the one to build from. Returns a URL to open for them.

Prefer this over sending full-page images whenever the user should decide which reference to
use. The picker shows real screenshots at scroll depth so they can evaluate long pages.

After calling this, tell them to choose in the picker, then call waitForPick with the pickId
to get their choice and a complete build prompt.
- `search_screens`: Search the UI reference catalog by keyword across titles, notes, page sections, and observed
actions. Filter by product or kind (flow/marketing/product).

Use this to find design pattern examples like "pricing page", "empty state", "date picker",
"onboarding step", "checkout form", "dashboard", "sign-up", "settings", etc. Returns the
best matches with screen IDs you can pass to getScreen or getScreenImage.
- `wait_for_pick`: Wait for the user to choose on the pick page. Long-polls up to 50 seconds—returns as soon as
they click, or status "pending" after the wait (call again if so).

Once chosen, returns their reference with its screenshot and a full build prompt, so you can
start building from it immediately. If they clicked "None of these fit", status is "dismissed"
and you should ask what they want instead.