Jev Guard MCP
Related Servers
Alternatives to Jev Guard MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables an LLM to drive a real browser by declaring one outcome at a time, while Jev chooses the element, action, and value and Playwright executes it, returning a clear status such as done, blocked, or needs confirmation. Also exposes tools to open pages, ask yes/no or multiple-choice questions about a page, read question-relevant page text, capture snapshots and screenshots, act on elements directly, and invoke a page's own WebMCP tools.0MIT
- AlicenseNot gradedqualityAmaintenanceEnables LLM-driven browser automation in which the caller states one outcome per step and Jev (Typesafe System One) decides the target element, action, value, and whether the step is done, blocked, erroring, or irreversible, while Playwright performs the action. Also exposes direct tools for navigation, element actions, page reading, screenshots, and invoking WebMCP tools that a page registers.0MIT
- AlicenseAqualityBmaintenanceEnables 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.6Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables an LLM client to drive a real browser by stating one outcome per step, while Jev (Typesafe System One) decides which element, action, and value to use and Playwright performs it. Also exposes tools for direct actions, page reading, screenshots, checks, choices, and calling a page's own WebMCP tools.0MIT
- AlicenseAqualityBmaintenanceEnables 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.1115 npm4MIT
- AlicenseNot gradedqualityAmaintenanceIt enables LLM clients to control a browser by giving goals and candidate values while Jev selects elements, actions, and values, with Playwright executing them. It also exposes tools for opening pages, checking conditions, choosing options, taking snapshots, direct actions, reading content, screenshots, WebMCP tools, and closing sessions.0MIT
TDQS
Scored across 3 tools
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.
All tools share the jev_guard_ prefix and follow the same lowercase verb pattern: preview, execute, cancel. The naming convention is uniform and predictable.
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.
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.