# Jet Browser Verifier

> Jet Browser Verifier is an open-source MCP server for browser automation. Verify an isolated WPE WebKit runtime with native input, DOM and screenshot evidence. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** Linux, CLI, self-hosted
- **Website:** https://masaka-ai.vercel.app/jet-browser/
- **Repository:** https://github.com/masakaai/jet-browser/tree/HEAD/integrations/mcp
- **MCP Registry name:** io.github.masakaai/jet-browser
- **Categories:** browser automation, developer tools
- **Listing updated:** 2026-11-15

## About

This server is a narrow verifier, not a general browsing tool. One call launches Jet Browser's WPE WebKit runtime in a separate Docker container with networking disabled, types through native input into a local fixture page, checks the DOM, captures a fresh PNG and cleans up. A pass requires at least 1,000 decoded PNG bytes and exact agreement between page title, typed text and DOM state.

It deliberately exposes no public-web navigation, CDP, personal profiles, credentials or telemetry, and the tool accepts no command, URL, image or path argument. Only one verification can run at a time, and output and runtime are capped.

It needs Node.js 24 or the OCI image, Docker and an x86_64 or ARM64 Linux host. Because the packaged image needs the Docker socket, which grants host-level control, the README advises configuring it only for a trusted client. Jet Browser itself is Apache-2.0 and aimed at running one isolated browser per agent session.

## Features

- **Offline verification:** Browser networking is disabled with Docker's --network=none.
- **Native input check:** Typing goes through the runtime's native input path rather than injected script.
- **DOM and PNG evidence:** Results include title, DOM state and screenshot size.
- **No arguments:** The verify call accepts no URL, command or path, which limits abuse.
- **Bounded runs:** One verification at a time with capped output and runtime.
- **Pinned image:** The runtime image is pinned by digest.

## Good for

- Confirm a Jet Browser build works in CI before using it for agent tasks
- Check that a container host can run the WPE WebKit runtime
- Capture reproducible evidence of startup and cleanup
- Evaluate Jet Browser's boundaries before adopting it

## Install

### Claude Code (Terminal)

```sh
claude mcp add jet-browser -- docker run -i --rm ghcr.io/masakaai/jet-browser-mcp:0.9.0
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "jet-browser": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/masakaai/jet-browser-mcp:0.9.0"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "jet-browser": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/masakaai/jet-browser-mcp:0.9.0"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "jet-browser": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/masakaai/jet-browser-mcp:0.9.0"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "jet-browser": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/masakaai/jet-browser-mcp:0.9.0"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "jet-browser": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/masakaai/jet-browser-mcp:0.9.0"
      ]
    }
  }
}
```

## Tools

- `jet_browser_capabilities`: Returns the pinned image, platform, evidence contract and non-capabilities without starting Docker.
- `jet_browser_verify`: Runs one bounded verification and returns startup, input, DOM, screenshot, network and image evidence.

## FAQ

### Can it browse the web?

No. It runs a local fixture only and exposes no public-web navigation.

### What does it require?

Node.js 24 or the OCI image, Docker, and an x86_64 or ARM64 Linux host.

### Is there a security caveat?

Yes. The OCI package needs the Docker socket, which grants host-level control, so use it only with a trusted MCP client.

### Which licence applies to Jet Browser?

The website describes the runtime as Apache-2.0.

### Is Jet Browser Verifier free?

Yes. Jet Browser Verifier is open source, so you can use and self-host it for free.

### How do I add Jet Browser Verifier to Claude Code?

Run this command in your terminal: claude mcp add jet-browser -- docker run -i --rm ghcr.io/masakaai/jet-browser-mcp:0.9.0

### What are the best alternatives to Jet Browser Verifier?

The closest alternatives to Jet Browser Verifier are REA, Browser Use, Scrapling MCP Server, Codebase Memory and GitHub.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Browser Use](https://ai-powered.com/mcp/browser-use): Browser Use is a freemium MCP server for browser automation.
- [Scrapling MCP Server](https://ai-powered.com/mcp/scrapling-mcp-server): Scrapling MCP Server is an open-source MCP server for web search and scraping.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.
- [Ouroboros](https://ai-powered.com/mcp/ouroboros): Ouroboros is an open-source MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/jet-browser-verifier
