Proving Lab MCP server

What tools does Proving Lab expose? (10)

Read from the live server. Click any tool for its input schema.

• list_measurementsUse 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_dataUse 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.
• get_methodFetch 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.
• extract_citationRead 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 a
• extract_citationsUse 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 e
• recommend_settingsThe 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.
• how_to_captureGet 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 as
• install_extensionInstall 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 r
• adoption_statsHow 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
• open_workList 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.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%not measurable

  No commit history available.

• Adoption20%not measurable

  No usage data available.

• Transparency20%25%

  1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.

• Provenance15%0%

  No source repository to trace the code back to.

• Packaging15%75%

  Remote endpoint; authentication requirements not declared.

Maintain Proving Lab? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![Proving Lab on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/dev-provinglab-browser-citation-capture)](https://mcp-skills-hub.vercel.app/mcps/dev-provinglab-browser-citation-capture)