mcpbeat Sign in

Proving Lab MCP Server

by provinglab Your server? Claim it
answering

Proving Lab is answering right now. Last checked moments ago. It exposes 10 tools.

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

Uptime history 50 days of history · worst day 82%
50 days agonow
90.2%
Uptime 24h
83 of 92 checks
10
Tools
read from the server
98 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 August 2026. No other catalogue keeps this.

31 Aug a tool description was rewritten install_extension
31 Aug a tool changed version
30 Aug a tool changed version3 times that day
and 2 more, back to 30 August 2026

Proving Lab does not always answer

Over the last week it answered 97.7% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

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

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

extract
extract_citation
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.
extract_citations
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.
adoption
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.
how
how_to_capture
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.
install
install_extension
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.
measurement
get_measurement_data
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.
measurements
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.
method
get_method
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.
open
open_work
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.
recommend
recommend_settings
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.

Endpoints

URLTransportStateLatencyChecked
https://provinglab.dev/mcp streamable-http answering 163 ms 0 min ago

Alternatives to Proving Lab

same job, measured the same way
Chrome-Stats
by chrome-stats

Extension and app analytics across Chrome, Edge, Firefox, Google Play, and the Apple App Store.

answering
Crawlio Browser
by crawlio

Bridge a live Chrome browser to your agent: 150 tools for capture, extraction, and observation.

72 installs/wk local only
O
Crx Permission Risk
by zovo

Score the privilege a Chrome MV3 extension takes from its manifest, and diff permission sets.

3 tools answering
Cws
by mikusnuz

MCP server for Chrome Web Store — extension upload, publish, status, and rollout

29 installs/wk local only
Newton Browser
by koala-studios

Local-only Chrome and Edge control for MCP clients through an origin-scoped extension.

28 installs/wk local only
url2image
by url2image

Capture batches of public web pages in a real browser and download the screenshots as a zip.

5 tools answering
Screenshotink
by screenshotink

Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.

31 installs/wk answering
UI Annotator MCP
by mcpware

Annotates any web page with hover labels for AI assistants — zero extensions, any browser

33 installs/wk local only

Proving Lab — questions

Answers built from our own checks of this server.

What can Proving Lab do?
It exposes 10 tools, read directly from the server on our last check. Among them: adoption_stats, extract_citation, extract_citations, get_measurement_data, get_method, how_to_capture and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Proving Lab working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 83 of 92 checks got a reply (90.2%), average response time 98 ms. The bar chart above shows every period we have measured.
How do I connect Proving Lab?
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.
Does Proving Lab need an API key?
No. Proving Lab completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Proving Lab?
It answers our handshake in 98 ms on average, which is faster than 90% 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.