Servidor MCP de Screenrove

• Nombre en el registrocom.screenrove/screenroveverificado en el registro MCP

El nombre en el registro está bajo screenrove.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-25
• Herramientas22
• El servidor se llamascreenrove
• Versión del servidor1.5.0
• Versión del protocolo2025-06-18

El 2026-10-25 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 2051 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta3250 ms
• Espacio en el contexto del agente≈ 6782 tokenslas definiciones de todas sus herramientas (22), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados21 de 22 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Todas las herramientas pasan las seis comprobaciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• build_handoff

  Generate a complete build prompt for a coding agent: ordered screens with notes, observed transitions, links to up to 10 agent-sized images (1x copies and page-section crops, never taller than 8000px, each with its pixel size), the…

• build_recipe

  Combine specific screens from different products, plus one visual style, into a single build brief. Each screen contributes one thing (say what with "id: what to take"); structure comes from the screens and every visual token comes from…

• 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…

• 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…

• find_related_screens

  Find screens from other products that solve the same design problem as this one: same primary pattern first, then shared tasks, states and components (rarer tags count more). At most two per product. Each result says why it matched. Use…

• 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…

• 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…

• get_motion

  Get one motion entry as a build prompt: what moves and how (every property, duration, easing curve or spring, delay and trigger), why it feels good, what a rebuild must keep, Screenrove's working vanilla HTML/CSS/JS implementation, and…

• get_motion_guidelines

  Get house rules for UI motion (durations, which easing for enter and exit, springs, what to animate, reduced motion) with citations, plus ready-to-use duration and easing tokens, the motion library's sources and its category and trigger…

• 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…

• 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…

• 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…

• 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…

• 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…

• list_tags

  List the tag vocabulary for searching by design problem: four facets (task, pattern, component, state), each tag with its definition, aliases and how many screens carry it. Use the ids with searchScreens or pickReference, e.g…

• name_patterns

  Summarise how real products are named: each naming pattern with its share and examples, the commonest TLDs, domain styles, length and syllable distributions, and a per-category table (top TLD, share on .ai, share on the exact .com, top…

• 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…

• search_logos

  Search the logos of the products in Screenrove's library, as references for designing a logo or app icon. Each logo is the product's own mark as its site serves it (SVG icon, apple-touch-icon or large favicon; never redrawn), linked to…

• search_motion

  Search the motion library: polished UI animations and micro-interactions (button presses, toggles, toasts, number tickers, thinking states, hover effects, interaction sounds) curated from open-source component libraries and designers'…

• search_names

  Search about 700 real product names - Screenrove's library plus a curated list of products on Mobbin and Refero - each with its domain and TLD, category and derived traits: naming pattern (real-word, compound, blend, altered, suffix…

• search_screens

  Search the UI reference catalog by design problem and keyword. Every screen is tagged on four facets: task (what the person is doing), pattern (screen archetype), component (building blocks) and state (empty, filtered, error...). Filter…

• 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…