Proofpage MCP Server

Capture it. Keep the evidence. Check the quote.

Proofpage turns public web pages and your own exported files into traceable evidence for AI. Collect material, inspect the original source, review training examples, and export datasets—or let an existing AI assistant search your evidence through MCP. The goal is a workspace for web evidence across formats, with source context, permissions, revisions, and exportable provenance. See the scraper strategy and format roadmap for what works today and what comes next.

Free to run on your own computer. MIT licensed. No account, subscription, or model API key required for core features. Desktop downloads include Python: no Python installation or terminal is needed. This is an early release. The Mac downloads are Developer ID signed and Apple-notarized; Windows signing is still pending.

New in v0.5.0: Reviewed business context, saved evidence runs, offline replay, Python/Node SDKs, installable skills, and Google Docs connection support. Google Docs requires your own OAuth setup while the shared app remains in testing.

What you can do

Proofpage prepares data; it does not train a model. Collection respects robots rules and does not bypass logins or access controls. Optional model-assisted drafting sends selected content only when you request it and still requires review. See capabilities and limits.

Related MCP server: qsearch

Run from source

With Python 3.11+ installed, clone this repository and run:

python3 -m pip install -e .
python3 -m proofpage --home ~/Proofpage-preview/data serve --open

Back up your workspace before updating. For the easiest setup, use the native downloads below.

Install and run

Download, extract, open

Choose your computer from the v0.5.0 downloads:

Proofpage opens in its own native Tauri window. Keep it open for scheduled collection; closing the window stops the local engine after active captures finish. Settings → App updates checks for releases and offers a matching download. Updating currently uses download-and-replace. Your library stays in your home folder under Proofpage/data.

No terminal. No Python setup. No account. Keep all extracted files together on Windows and Linux. The app chooses an available local port automatically. Linux requires a graphical desktop and system libraries compatible with Ubuntu 22.04 or newer; not every distribution has been tested. On Mac, use About This Mac to find your processor type.

Mac downloads are signed and notarized: both Apple silicon and Intel archives include stapled Apple tickets and pass Gatekeeper assessment. macOS may still show its normal first-download confirmation. Windows remains an unsigned preview and may warn about an unknown publisher or block launch. Do not disable system security protections. Mac verification record.

Your files stay separate from the app

Your user folder / Proofpage/
├── data/       Your private evidence and settings
├── backups/    A place to save database backups
└── exports/    A place to save dataset downloads

Backups and exports are saved where you choose. Updating or replacing the application does not delete this data folder. The desktop app reuses the data/ folder created by the earlier guided installer. CLI workspaces at other paths are separate.

For developers and terminal users, download proofpage-0.5.0-local.zip instead. This source-oriented bundle requires Python 3.11+. Extract it and run:

python3 scripts/install.py

On Windows use py -3 scripts/install.py. It creates an isolated runtime and CLI launchers under ~/Proofpage. If that folder already exists, choose a new location with --directory. Full setup instructions →

Save straight from Chrome

Add to Chrome → — companion 0.3.0 is available from the Chrome Web Store. No Developer mode or ZIP installation is needed.

Open Proofpage → Settings → Connect browser, then enter its port and pairing code in the companion's Connect your desktop app panel. On a page, choose Preview this page, review the content, confirm permission, and choose Save to Proofpage. After pairing, saving goes straight into your local library with no manual import. The companion also saves original images and PDFs with desktop 0.3.0 or later. Passwords and session cookies stay in Chrome. Browser setup and privacy guide →

Your first five minutes

1. Click Add source, enter a public page URL, then click Collect in Sources.

2. Open the record in Library to inspect its text, original evidence, and capture details.

3. Open Verify to check a quoted answer against captured evidence, or use Training to create draft examples, review source permissions, and approve suitable examples.

4. Freeze and export a training bundle. Use Datasets for the separate reviewed text-corpus workflow.

5. Open Agent access to connect an AI assistant to your local evidence.

For archives, choose Import files, create an account-specific profile, preview the file, and select what to keep. Read the full workflow guide →

Connect your AI assistant

Open Agent access → Copy setup prompt and paste it into your assistant. Proofpage fills in the correct executable and data-folder paths. The prompt asks the assistant to preserve existing integrations, configure this local MCP server, and verify it by listing sources. Copy MCP configuration gives you the JSON directly.

Desktop downloads include the MCP helper, so this does not require installing Python. Your assistant must support local MCP and have permission to configure integrations; regular web chats may only be able to provide instructions. Connection guide.

Prefer the terminal?

The optional Python installation includes a CLI. Desktop downloads open a native workspace window. After following the optional CLI setup above, on macOS/Linux:

~/Proofpage/proofpage --help
~/Proofpage/proofpage doctor
~/Proofpage/proofpage collect https://example.com
~/Proofpage/proofpage search "example"
~/Proofpage/proofpage serve --open
~/Proofpage/proofpage backup ~/Proofpage/backups/evidence.sqlite3

On Windows PowerShell, use & "$HOME\Proofpage\proofpage.cmd" followed by the same arguments. Collection and search return JSON for scripts. doctor checks Python and SQLite FTS5 support and shows the workspace path. All CLI workflows →

git clone https://github.com/Mehxeo/Proofpage-OpenSource.git
cd Proofpage-OpenSource
python3 scripts/install.py

For development, create a virtual environment instead:

python3 -m venv .venv
.venv/bin/python -m pip install -e .
.venv/bin/proofpage --home .proofpage serve --open

On Windows, use py -3 and .venv\Scripts\python.exe / .venv\Scripts\proofpage.exe. Installing from source may download build tools. The local release bundle installs its wheel without third-party runtime dependencies. Do not assume an unrelated package on PyPI is this project; use this repository's releases.

Help, upgrades, and your data

• Desktop app: it chooses a free port. If it says Proofpage is already running, use the existing Proofpage window.

• Python or SQLite error: run proofpage doctor. Python must include SQLite FTS5. Install a supported Python distribution if it does not.

• Upgrade desktop: close Proofpage, replace the application with the new download, and reopen it. Keep your Proofpage/data folder. For CLI upgrades and backups, see the installation guide.

• Uninstall desktop: close Proofpage and remove its application files. Your data remains in your user folder. Remove that data folder only if you want to delete the evidence too.

• Questions or bugs: open an issue. For sensitive reports, follow Security.

Open source

MIT license · Contributing · Implementation status · CI checks

The repository also includes an optional self-hosted edition with isolated accounts and billing integration. A managed paid service is not live. Local use remains free and independent of hosted accounts.

Signing and notarization workflows are available for maintainers: secure setup guide. Signing status is stated per release; adding workflows alone does not make existing downloads signed.

Images, PDFs, and OCR

The 0.3 desktop app saves original files and extracts searchable text locally, including scanned PDF pages. Save public image/PDF URLs directly and watch them hourly. Media and automation guide.

Automation and assistant setup (current source)

Open Agent access → Test MCP connection to check the actual local server. Copy the setup prompt to a local MCP-capable assistant, then confirm it can list your sources. Download the bundled Proofpage skill for collection, schedules, research and training-draft workflows. In Sources → Set schedule, choose an interval or pause. Scheduled collection requires the app/server to stay running.

These setup improvements are included in the desktop release. ChatGPT web requires a separate compatible remote connector, not the local stdio configuration.

Native runtime requirements: Windows uses Microsoft Edge WebView2. Linux needs WebKitGTK 4.1 (libwebkit2gtk-4.1-0 on Ubuntu) and a graphical desktop.

Build the native app yourself: Tauri desktop build guide.

Reproducible evidence for developers

Proofpage 0.5.0 includes pinned input manifests, offline replay, exact quote dependencies, drift reports, Python/Node SDKs, and a CI action. The desktop app includes the evidence-run UI and MCP tools; the repository includes the CLI, SDKs and CI action. Developer workflow · Implementation plan.

Agent access now also records retrievals under an output ID, replays saved inputs, checks changes, and exports manifests. Five MCP tools expose the same workflow to local assistants. The Python SDK can import results from existing collectors without a hosted dependency. All of this remains MIT licensed.

Business context

Build a reviewed profile from selected evidence, keep business/customer/reference/ writing material separate, and export portable Markdown/JSON context packs. Bookmark HTML imports preview selected links without silently fetching pages. Local MCP clients can retrieve approved current profiles; approved business facts can become separately reviewed training drafts. Setup and developer API.

Optional connectors

Sync explicitly selected Google Docs with read-only OAuth and credentials stored in the operating system vault. Serve read-only context over OAuth-protected remote MCP, or install the bundled skill into a Codex/Claude project with proofpage install-skill --project /path/to/project --client codex. Setup, permissions and limitations. The desktop includes Google OAuth and secure-vault libraries; client configuration is still required. The remote MCP server and skill installer are available through a source/CLI installation. Remote connections need your own HTTPS host and OAuth provider.