Skip to main content
Glama
brunoboto96

SceneScout

by brunoboto96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to SceneScout

No user-submitted related servers found.

    Related Servers

    • uisight

      Kenneth67298
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables AI agents to measure live web and responsive UIs — contrast ratios, touch targets, overflow, and theme drift — returning precise, selector-attached findings as text. It also lets a human and agent share the same live mobile and desktop session, with pinned notes and screenshots readable by the agent.
      98 npm
      MIT

    • uisight

      sololabstr
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that provides AI coding agents with real-time visual access to web apps, enabling them to see screens, run accessibility and layout inspections, and interact with pages through a shared live panel.
      98 npm
      130
      MIT

    • Charlotte

      RebeccaLacroix45928
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI agents token-efficient, structured access to web pages, returning compact page orientations and targeted element queries instead of full accessibility-tree dumps, plus browser interaction, monitoring, and session management tools.
      4 npm
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.6/5.0

    Scored across 48 tools

    Disambiguation3/5

    Core interaction tools (click, type, select, press, hover, scroll, navigate, back) are cleanly separated, and the finding-lifecycle tools (finding, cards, feedback, resolve, verify) are distinguishable. But the planning surface — scout_intake, scout_guided_plan, scout_guided_confirm, scout_recheck_plan, scout_saved_checks, scout_lane_brief/report — and the four reporting tools (report, team_report, recap, cards) overlap heavily in intent; only very long descriptions keep them apart. scout_run_plan vs. the single-action tools is another soft overlap an agent could misselect on.

    Naming Consistency4/5

    Every tool uses the scout_ prefix and snake_case, with a predictable verb_noun or resource_noun shape. Minor deviations (noun-only names like scout_playbook, scout_journey, scout_recap, scout_coverage) break the verb pattern but remain readable and unambiguous within the prefix scheme.

    Tool Count2/5

    48 tools is well past the 'heavy' band and sits in the too-many range for a single server. Much of the bulk comes from peripheral surfaces (guided plans, saved checks, lanes, ticket filing/status, three report formats) that could be consolidated or split into separate servers.

    Completeness4/5

    The surface is unusually thorough for browser-based QA: interaction, network, design audit, journeys, coverage, findings with dedup/verification, guided plans, and reporting are all present with lifecycle coverage. Gaps are minor — no explicit console-log retrieval, viewport/device emulation, or waiting/synchronization primitive — which agents can mostly work around.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources