Skip to main content
Glama
albinchristo14

Render & Verify MCP

by albinchristo14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Render & Verify MCP

No user-submitted related servers found.

    Related Servers

    • agent-eyes

      oljodev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to see, measure, and verify web pages through a real Chrome browser, including screenshots, responsive layout and accessibility audits, pixel diffing against baselines, secure logins, and deployed-fix verification.
      27
      1
      MIT

    • vouch

      hamza-paracha
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to verify application changes by running browser workflows, executing independent state assertions, and producing replayable evidence.
      2 npm
      MIT
    • 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
      59 npm
      3
      MIT

    • web-ui-tester

      hofmeister
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to rapidly drive and inspect real web pages through persistent browser sessions, using accessibility-tree snapshots and DevTools-grade diagnostics to identify and diagnose issues.
      26
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: session lifecycle (open_url, close_session), interaction (click, type_text, set_viewport), evidence retrieval (screenshot, get_console_errors, get_network_failures, get_page_snapshot), and verification (verify_page). The only real overlap is open_url vs navigate, but the descriptions explicitly distinguish creating a new isolated session from navigating an existing one. screenshot vs get_page_snapshot are also reasonably separated as image vs DOM evidence.

    Naming Consistency4/5

    Nearly all tools follow a predictable snake_case verb_noun or get_* pattern (open_url, close_session, set_viewport, verify_page, get_console_errors, get_network_failures). The only deviation is hello_world, which breaks the verb-first convention but is minor and reads as a connectivity probe. Overall the naming is consistent and readable.

    Tool Count5/5

    At 12 tools the set is well-scoped for a browser render-and-verify server, comfortably within the ideal 3-15 range. Each tool maps to a coherent stage of the workflow (open, interact, collect evidence, verify, close) with no obvious filler. No bloat or thinness.

    Completeness4/5

    The surface covers session lifecycle, core interactions, diagnostic collection, and a deterministic verification step, which is solid coverage for the stated domain. Minor gaps exist: no scroll/hover/select or explicit key-press beyond Enter within type_text, and no session listing, but agents can work around these from the current toolset.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources