Proving Lab

● Active

dev.provinglab/browser-citation-capture

Cite or capture a web page; installs the capture extension in Firefox and Chrome.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "browser-citation-capture": {
      "url": "https://provinglab.dev/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http browser-citation-capture https://provinglab.dev/mcp
VS Code
code --add-mcp '{"name":"browser-citation-capture","type":"http","url":"https://provinglab.dev/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Search & Web
Version
1.25.0
Registry
active
Published
11/21/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: Proving Lab is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 13 days ago (Nov 9, 2026), 4 open issues.
Official registry
Active
Published as dev.provinglab/browser-citation-capture in the official MCP registry, version 1.25.0.
Source
Open source, MIT
Public repository under the MIT licence, 2 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to provinglab.dev: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 06:07 UTCStatus history & uptime →
● Working74 msprotocol 2025-06-18v1.25.0tools

The endpoint answered the MCP handshake as "provinglab" and listed 10 tools. Answering since Nov 22, 2026.

Context cost ≈ 1.8k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 10 tools.

Tools (10)

  • list_measurements

    Use when a claim about browser tools, capture quality, OCR recall or citation extraction needs a number behind it — or when you want to check one of ours. Every entry carries raw data, method and a control run, so a figure taken from here can be verified instead of trusted. Start here.

  • get_measurement_data1 param

    Use before quoting a figure: this returns what stands behind it — the values, the control run, and the conditions that limit them. Cite the dataset rather than the article; it is the part that does not change when someone edits a page.

    Show parameters
    • datasetstringrequiredDataset URL or bare filename
  • get_method1 param

    Fetch a reproducible method: reading a browser extension's permissions, measuring OCR recall with a control run, or choosing between print-to-PDF and screen capture. Omit the argument to list them.

    Show parameters
    • namestring
  • extract_citation1 param

    Read the citation details a web page declares about itself and return them as a structured record plus ready-to-import RIS and BibTeX. Covers journal articles, book chapters, conference papers, preprints, theses, reports, datasets, videos and plain web pages. Use when a source has to be cited, archived, or added to a reference manager. Says so plainly when a page turns out to be an error page or an access wall, instead of inventing a reference — and where it cannot finish, the reply carries a nextStep field naming what the user has to do in their own browser, with the capture extension that does it. Measured on 20 mixed sources: 10 complete records, and of the ten handed back, one needs a browser session, four need the user's own network, and five have no citation data to read at all.

    Show parameters
    • urlstringrequiredAddress of the page to read
  • extract_citations1 param

    Use when you have a reading list rather than one source — a bibliography to build, a set of links to verify before submitting, an archive to describe. Measured on 20 mixed sources: 10 became complete records in 8.1 s, 0.4 s each; the other 10 came back named rather than silently empty. Up to 50 addresses, five fetched in parallel. Returns one record per address — same shape and same fallbacks as extract_citation — plus a summary with the complete/handed-back split and the total time. Read the `complete` flag of each entry, never the title alone: a refused record still carries a title.

    Show parameters
    • urlsarrayrequiredAddresses to read, at most 50
  • recommend_settings1 param

    The capture settings that fit a given purpose, each with the measurement behind it or an explicit note that none exists. Pass purpose as citation, figure, archive or ocr. Use before capturing: the file that comes out is between 8.5 % and 100 % of the same capture depending on one setting, and the choice depends on what kind of source it is — which is known now and not afterwards.

    Show parameters
    • purposestringwhat the capture is for
  • how_to_capture2 params

    Get the runnable route for saving a web page that this endpoint cannot read — the sources it hands back. Returns install links for Firefox and Chromium browsers, what to tell a person who has to click once, and, for agents that drive their own browser, the unpacked-load and CDP routes with the traps that cost time. Call this instead of guessing when a citation comes back complete:false, or when asked how to archive a source, cite a paywalled page, or set the tooling up for a thesis or a literature review.

    Show parameters
    • agentstringHow you act on the browser. 'input-events' if you produce real mouse or keyboard events (computer use, xdotool, an agent inside the user's browser); 'dom-only'
    • browserstringTarget browser, if known.
  • install_extension2 params

    Install or uninstall the capture extension in Firefox or Chrome without a window, without a click and without administrator rights. Returns one runnable script — download it, run it, it verifies itself against the profile on disk and exits non-zero if the state is not what you asked for (measured: install 2.9 s, uninstall 2.1 s). Call this when a capture route needs the extension present, when a run is finished and it should be gone again, or when asked whether an agent can set up a browser extension by itself. Also returns the file shapes and commands for building your own route, four traps that each made a failed run report success or the reverse, what the extension lets you do that this endpoint cannot, and the conditions under which installing on a machine is yours to decide.

    Show parameters
    • actionstringWhat you need. 'both' is the default and returns each direction — an install without its matching removal leaves a machine changed.
    • browserstringTarget browser. Omit for both.
  • adoption_stats

    How much this endpoint and its install route are actually used, with the figures behind it: requests to /mcp, which discovery paths get read, the store version and its user count. Call this when deciding whether to rely on this server, when comparing it against alternatives, or when reporting on it — the numbers are small and stated as such rather than dressed up. Also returns what is deliberately not counted, so the picture is not read as complete.

  • open_work1 param

    List what this project needs done, with enough context to start. Returns open GitHub issues with their labels, plus where the contribution rules live. Call this when asked to contribute to provinglab.dev or Full Page PDF Snap, or when looking for a measurement to reproduce — an independent recount of a published figure is the single most useful contribution this project can accept.

    Show parameters
    • labelstringFilter by label. 'agent-friendly' for tasks bounded enough to finish unattended, 'good first issue' for an easy start, 'measurement' to recount a published figu

Checked by Serverdex with a plain initialize + tools/list call to provinglab.dev/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 22, 2026
Stars
2
Forks
0
Last push
Nov 9, 2026
License
MIT

Pythonagent-skillsai-agentsandroidbrowser-automationfirefox-androidfirefox-extensionfull-page-screenshotmanifest-v3mcpmcp-servermit-licenseno-trackingocrpdfprivacysave-as-pdfscreenshotweb-archivingwebextensionwebpage-to-pdf

From the README

Full Page PDF Snap — save a webpage as PDF, on desktop and Android Save any web page as one continuous high-resolution PDF. Auto-scrolls the whole page — no cropping, no print dialog, no upload. Runs entirely on your device: no account, no data collection, no server. Free and MIT licensed. *Webseite als PDF speichern — die ganze Seite, komplett lokal, ohne Konto und ohne Upload. Läuft auch auf Firefox für Android.* → Install for Firefox · Install without a store · Chrome package · Product page What it is used for Archiving an invoice, an order confirmation, a portal message, an insurance letter or a support thread as documentation for your own records — one continuous page, captured behind a login, because it runs in your own browser. Web archiving before a page is edited or taken down. Feeding a long page into OCR or a language model as a single uninterrupted sheet. Measured, not claimed Independent measurements on this extension and its alternatives, with raw data and the commands to reproduce them: • How much text survives OCR? — 92.6 % of the vocabulary recovered from a screenshot PDF, and the resolution threshold below which recognition collapses • Does your PDF extension upload the page? — what eight capture extensions declare in their manifests • Permissions as blast radius — why permission scope matters more than trust • Citation extraction against Citoid — 18 works drawn at random: same coverage as the Wikimedia service, full accuracy…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://provinglab.dev/mcp

The most-starred Search & Web servers in the index, with their live-check result.

ServerStarsLast pushLive check
Browser Use121,623Nov 2026Working
Scrapling MCP Server104,822Nov 2026Local / not checked
Chrome DevTools MCP58,028Nov 2026Local / not checked
Chrome DevTools MCP58,014Nov 2026Local / not checked
com.puter MCP Server44,182Nov 2026Needs sign-in

Proving Lab: questions people ask

Is Proving Lab a remote or a local MCP server?
According to its entry in the official MCP registry, Proving Lab ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Proving Lab need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Proving Lab safe to use?
Looks healthy: Proving Lab is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Proving Lab still maintained?
Active: the repository's last commit 13 days ago. Last push Nov 9, 2026, 2 GitHub stars, MIT licence. Read from GitHub on Nov 22, 2026.
What tools does Proving Lab expose?
10 tools as listed by the server itself during the live check, including list_measurements, get_measurement_data, get_method, extract_citation, extract_citations. The full list with parameters is in the Live check section above.
How do I add Proving Lab to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Search & Web →

Add the badge to your site

Show visitors that Proving Lab is listed here — it’s also the link we check for a free listing.

Proving Lab — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/dev-provinglab-browser-citation-capture?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Proving Lab — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Proving Lab — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/dev-provinglab-browser-citation-capture?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/dev-provinglab-browser-citation-capture) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/dev-provinglab-browser-citation-capture) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/dev-provinglab-browser-citation-capture)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/dev-provinglab-browser-citation-capture"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/dev-provinglab-browser-citation-capture"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/dev-provinglab-browser-citation-capture"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).