Lets an assistant extract web page citation records, look up capture measurements and methods, and install a capture extension in Firefox or Chrome.
What you can do
Offers tools around browser capture and citation: list and fetch measurement datasets and reproducible methods, extract citation details a page declares about itself for one source or up to 50, returning structured records plus RIS and BibTeX. It also recommends capture settings by purpose, explains how to capture pages the endpoint cannot read, installs or uninstalls a capture extension in Firefox or Chrome, and reports adoption figures and open work.
When to use it
Use it when an assistant needs importable citation records for web sources, a batch bibliography, or capture settings and methods before saving a page. Also suited to checking measured figures on browser tools and capture quality, or finding project work to contribute to.
Requirements
Remote endpoint over streamable HTTP; no local package. No authentication, environment variables or headers are declared. Installing the extension needs a Firefox or Chromium browser with a profile, and some routes require a person to click once.
Before you install
install_extension installs or removes a browser extension in a profile without a window or administrator rights, so review the returned script and target profile before running it. extract_citations accepts up to 50 URLs and contacts external pages. adoption_stats and open_work return project usage figures and GitHub issue details.
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/dev.provinglab%2Fbrowser-citation-capture/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.
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.
Takes no parameters.
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.
Parametersdatasetrequired
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.
Parametersname
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.
Parametersurlrequired
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.
Parametersurlsrequired
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.
Parameterspurpose
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.
Parametersagentbrowser
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.
Parametersactionbrowser
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.
Takes no parameters.
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.
Parameterslabel
Version history
1
v1.24.2LatestSep 16, 2026
Score
83%
83% 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
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.