Other · Remote MCP server
Browser Proof
Evidence-backed web verification for agents with deterministic JSON, text evidence, and screenshots.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.shin1219-eng/browser-proof- Version
- 1.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-04-08
- Updated
- 2026-04-08
- Publisher
- shin1219-eng (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/shin1219-eng) · how
- Listed under
- Browser automation MCP servers
- Repository
- github.com/shin1219-eng/browser-proof
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://proof.reprompt.jp/mcp | X-API-Key (required, secret) |
| SSE (HTTP + Server-Sent Events) | https://proof.reprompt.jp/mcp/sse | X-API-Key (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://proof.reprompt.jp/mcp(HTTP)- Reachable
- No - could not connect (DNS or connection failure)
- Handshake
- -
- Checked on
- 2026-10-05
- Endpoint
https://proof.reprompt.jp/mcp/sse(SSE)- Reachable
- No - could not connect (DNS or connection failure)
- SSE stream
- could not connect (DNS or connection failure)
- Checked on
- 2026-10-05
How to connect Browser Proof
Browser Proof is a remote MCP server: there is nothing to install. Its endpoint is https://proof.reprompt.jp/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://proof.reprompt.jp/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: X-API-Key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Browser GatewayAI browser tools with Chrome CDP. Navigate, screenshot, interact. Multi-provider failover. | Local · stdio |
| Browser MCPControl a local headless Chrome browser: open pages, read titles, and take screenshots. | Local · stdio |
| Browser MCPHosted real Google Chrome MCP with per-user persistent state. Navigate, click, type, screenshot. | Remote · HTTPLive check: ✓ handshake |
| Browser MCP CdpLocal Chrome via CDP with profile-snapshot isolation and shared-broker multi-client support. | Local · stdio |
| Browser URL CheckCheck whether a URL can be opened. No browser is launched. | Remote · HTTPLive check: ✓ handshake |
| BrowserTap MCPMCP server that drives the real Chrome you already use, through an extension and CDP. | Local · stdio |
| Brreg NoBrønnøysund Register Centre (BRREG) MCP - Norway's official business register. | Remote · HTTPLive check: ✓ handshake |
| Bruno MCP StudioAuthor, edit and run Bruno collections as files: HTTP, WebSocket, gRPC, per-request pass/fail. | Local · stdio |