Skip to main content
Glama
RanielliMontagna

Jev Guard MCP

by RanielliMontagna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Jev Guard MCP

No user-submitted related servers found.

    Related Servers

    • jev-explorer

      lazyoft
      A
      license
      A
      quality
      C
      maintenance
      Enables agents to delegate browser exploration to Jev by providing natural-language objectives, receiving compact evidence and source context, and continuing the same live browser session through supervisor handoffs.
      6
      Apache 2.0

    • ultrabrowse

      narekgevorgyan
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to delegate complex web browsing goals to a real Chrome instance driven by Jev, completing tasks end-to-end in ~300ms per decision and returning only the final result.
      11
      1
      MIT

    • browser-use-mcp

      jimsimoy
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI clients with deterministic Playwright-driven browser control, enabling navigation, interaction, screenshots, and inspection of rendered HTML, computed styles, console diagnostics, and font audits without an embedded LLM or API key.
      MIT

    • browser-mcp-claude

      saGoldberg31
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote browser automation via MCP, allowing models to open pages, read snapshots, click, fill, and select elements using Playwright, with built-in security restrictions against sensitive actions.
      -

    • Playwright MCP

      1000carlospena-prog
      A
      license
      B
      quality
      C
      maintenance
      Enables LLMs to drive a hosted headless Chromium browser over HTTP, performing navigation, clicks, typing, and page reading through accessibility snapshots, protected by bearer-token authentication.
      23
      5,046,799 npm
      Apache 2.0
    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 3 tools

    Disambiguation5/5

    Each tool maps to a distinct state in the preview lifecycle: creating a preview, executing it, or canceling it. The descriptions make it clear that preview never navigates, execute does navigate, and cancel aborts without navigating.

    Naming Consistency5/5

    All tools share the jev_guard_ prefix and follow the same lowercase verb pattern: preview, execute, cancel. The naming convention is uniform and predictable.

    Tool Count5/5

    Three tools is exactly the right scope for this guard workflow: one to create a preview token, one to consume it via navigation, and one to consume it by canceling. There is no redundancy or bloat.

    Completeness5/5

    The preview-to-execute-or-cancel lifecycle is fully covered with no dead ends. Each preview token has a clear path to either execution or cancellation, which satisfies the server's stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources