Skip to main content
Glama
GeoCodeCrafter

frontend-eyes

by GeoCodeCrafter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to frontend-eyes

No user-submitted related servers found.

    Related Servers

    • websight

      h34tsink
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to see, analyze, and visually verify web page changes through pixel-perfect diffing, theme extraction, layout analysis, and interactive element detection.
      19 npm
      MIT

    • browsertrack

      litepacks
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to access local browser diagnostics—runtime errors, console logs, network failures, breadcrumbs, DOM snapshots, and screenshots—and run closed-loop verification to debug and confirm fixes.
      13 npm
      -

    • agnt

      standardbeagle
      A
      license
      Not graded
      quality
      A
      maintenance
      Bridges AI coding agents with the browser to provide visual debugging, real-time error capture, screenshot capabilities, DOM inspection, and interactive wireframing through a reverse proxy with injected developer tools.
      21 npm
      21
      Apache 2.0
    • QualityMax QA MCP by Quality-Max

      QualityMax QA MCPofficial

      Quality-Max
      A
      license
      A
      quality
      A
      maintenance
      Enables coding agents to independently verify web changes by scanning pages, inspecting UI structure, generating Playwright reproductions, and executing tests with structured QA evidence.
      4
      66 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    capture is solely concerned with layout overflow across viewport widths, while diagnose handles console errors, exceptions, and failed requests. Their purposes are clearly separated with no meaningful overlap.

    Naming Consistency4/5

    Both tool names are lowercase imperative verbs and follow the same two-tool pattern, but they are generic single words rather than descriptive verb_noun pairs. This is still internally consistent, though slightly less informative.

    Tool Count4/5

    Two tools is small, but the server appears intentionally scoped to frontend issue detection rather than broad browser automation. The count is slightly thin yet reasonable for the stated purpose.

    Completeness4/5

    The pair covers common frontend failure modes: visual overflow and runtime/network errors. Missing areas like accessibility or performance checks are not obviously required by the server's narrow focus, though the surface is minimal.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources