mcpbeat

Browser Proof MCP Server

io.github.shin1219-eng/browser-proof
answering

Browser Proof is answering right now. Last checked 1 min ago. Last commit 8 Apr 2026.

Evidence-backed web verification for agents with deterministic JSON, text evidence, and screenshots.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
184 of 184 checks
—
Tools
hidden behind auth
94 ms
Response time
average over 24h
0
Stars
last commit 8 Apr 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add browser-proof --transport http https://proof.reprompt.jp/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "browser-proof": {
      "url": "https://proof.reprompt.jp/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.browser-proof]
url = "https://proof.reprompt.jp/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "browser-proof": {
      "url": "https://proof.reprompt.jp/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "browser-proof": {
      "url": "https://proof.reprompt.jp/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://proof.reprompt.jp/mcp streamable-http needs key 105 ms 1 min ago
https://proof.reprompt.jp/mcp/sse sse needs key 100 ms 1 min ago

Browser Proof — questions

Answers built from our own checks of this server.

Why is there no tool list for Browser Proof?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Browser Proof working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 184 of 184 checks got a reply (100.0%), average response time 94 ms. The bar chart above shows every period we have measured.
How do I connect Browser Proof?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Browser Proof need an API key?
Yes. Every time we knock, Browser Proof answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Browser Proof?
It answers our handshake in 94 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Browser Proof open source?
Yes — 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.