Jet Browser Verifier

Name: Jet Browser Verifier
Author: masakaai

by masakaaiversion 0.9.0i★ –iRuns on your computer

Registry nameio.github.masakaai/jet-browser

Install

Overview

Description from the maker (original English)

Verify an isolated WPE WebKit runtime with native-input, DOM, PNG, and cleanup evidence.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Web & browsers

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account masakaai, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Web & browsersi

More stars than 0% of the other 1378 servers in this category
Published to the registry more recently than 54% of the other 1378 servers in this category
Basic checks equal to or better than 100% of the other 1378 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Jet Browser Verifier safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.9.0) reached the registry 27 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Browser Use

by browser-use

Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.

Computer or cloud★ 120,087MITUpdated 17 days ago

Install

Chrome DevTools MCP

by ChromeDevTools

Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.

Runs on your computer★ 54,821Apache-2.0Updated 16 days ago

Install

MCP Server Browser

by bytedance

MCP server for browser use access

Runs on your computer★ 39,550Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Jet Browser MCP verifier

This local stdio server gives an MCP client one narrow way to verify Jet Browser. Its multi-platform package selects a native linux/amd64 or linux/arm64 image, disables browser networking, opens the image's local fixture, types through native input, checks the DOM, captures a fresh PNG, and cleans up.

It is a runtime verifier, not a general browsing server. It does not expose public-web navigation, CDP, personal browser profiles, credentials, a hosted service, or telemetry.

Requirements

Node.js 24+
Docker
An x86_64 or ARM64 Linux host

The first verification may pull the public image from GHCR. Browser execution itself uses Docker's --network=none boundary. The image is pinned by digest in server.mjs.

Install from the OCI package

The versioned MCP image starts the stdio server directly. It needs the Docker socket only when jet_browser_verify launches the separately isolated WPE WebKit runtime:

"mcpServers": { "jet-browser": { "command": "docker", "args": [ "run", "--rm", "-i", "--network=none", "--mount", "type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock", "ghcr.io/masakaai/jet-browser-mcp:0.9.0" ] } } }

Docker socket grants host-level control. Configure this local server only for a trusted MCP client. The outer MCP container has networking disabled, and the browser container it launches independently uses --network=none, resource limits, reduced capabilities, and deterministic cleanup.

The package metadata for the official MCP Registry is server.json. The OCI image carries the matching io.modelcontextprotocol.server.name ownership annotation.

Install from source

git clone https://github.com/masakaai/jet-browser.git

cd jet-browser npm ci

Add the server to an MCP client with an absolute checkout path:

"mcpServers": { "jet-browser": { "command": "node", "args": ["/absolute/path/to/jet-browser/integrations/mcp/server.mjs"] } } }

The process speaks MCP on stdout and writes operational errors only to stderr. It exits when the client closes stdin.

Tools

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

Only one verification can run at a time. A client-side cancellation aborts the child process. The server caps child output and total runtime; failures are returned as MCP tool errors rather than protocol failures.

A successful call returns structured content like:

"status": "passed", "network": "disabled", "title": "Jet Browser Ready", "input": "open-source runtime", "screenshotBytes": 2048, "image": "ghcr.io/masakaai/jet-browser@sha256:5884204e128a3e5bb17634078affdf28d1933d2745752cee3bc74235ed316cec" }

The screenshot byte count varies. A pass requires at least 1,000 decoded PNG bytes and exact agreement among the expected page title, native text input, and DOM state.

Verify the integration

The protocol test starts the real stdio server, performs an MCP handshake, lists its tools, and calls the capability tool without requiring Docker:

node --test test/mcp-server.test.mjs

The repository's standalone CI remains the end-to-end runtime proof. To execute that same Docker acceptance locally:

JET_BROWSER_IMAGE=ghcr.io/masakaai/jet-browser@sha256:5884204e128a3e5bb17634078affdf28d1933d2745752cee3bc74235ed316cec \

npm run standalone:smoke

Security boundary

The MCP call accepts no command, URL, image, profile, or path argument.
The child process receives only the Docker connection variables it needs; application secrets are not forwarded.
The container has browser networking disabled, bounded CPU, memory, PIDs, shared memory, and capabilities, and is removed after the check.
The verifier never attaches to a running personal browser.
Treat Docker access as privileged host access. Only configure this server for trusted local MCP clients.

For a broader embedding boundary, use Jet Browser's versioned tool declarations in sdk/tools.mjs and supervise each isolated container from your own harness.

Jet Browser Verifier

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Web & browsersi

Common questions

Alternatives

Browser Use

Chrome DevTools MCP

MCP Server Browser

README from the maker

Jet Browser MCP verifier

Requirements

Install from the OCI package

Install from source

Tools

Verify the integration

Security boundary