Browser Proof

io.github.shin1219-engPublished by GitHub account shin1219-engv1.1.0Updated Oct 25, 2026

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

The publisher's own server: Proof Holdings

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that lets an assistant verify web content and return deterministic JSON, text evidence and screenshots as proof.

What you can do
Verify web content and return evidence-backed results as structured JSON, text evidence and screenshots. Produce deterministic output suitable for checking claims against what a page actually shows. Capture screenshots as visual proof alongside the extracted text.
When to use it
Useful when an assistant needs to confirm what a web page actually says or shows and back that up with reproducible evidence, rather than relying on unverified retrieval.
Requirements
A remote endpoint at proof.reprompt.jp over streamable HTTP. A production API key supplied in the X-API-Key header is required. No local runtime or packages are needed.
Before you install
You must supply a production API key via the X-API-Key header; treat it as a secret and check how the remote service stores or logs the pages it verifies. The service sends the target web content to a third party.

Installation

In SourceWeft

  1. Open Browser Proof in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.shin1219-eng%2Fbrowser-proof/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "browser-proof": {
      "type": "http",
      "url": "https://proof.reprompt.jp/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Proof integrations