init_auditLABSCO SUMMARY
The gates are in code, which is what makes the audit worth reading.
Three failure modes of "review my paper" are handled structurally rather than by prompting: a fabricated finding is rejected because its quote does not match the source, a premature rewrite is refused because the state machine has not reached adjudication, and a skipped verdict is impossible because the gate is computed. The limits are stated as plainly: it is not a theorem prover, and catching a semantic error still depends on the model driving it.
What it is
A reproducible audit harness for mathematical LaTeX papers, with a deterministic Python core and two front ends — a CLI and an MCP server. The harness itself never calls a model; the reasoning stays in the agent driving it or in your hands.
What you get
- An MCP server exposing 29 tools by the README's count, eight of them named in its docs, plus the audit prompt pack; the agent walks through them in order:
init_audit,run_scan,propose_segments,submit_issue,adjudicate_issue,run_gate - LaTeX-AST structure extraction — theorems, labels, references, citations, equations, draft markers — into
structure.json - Quote verification at intake: a finding whose quoted text is not in the source is rejected as
REJECTED_SOURCE_TARGET_INVALIDbefore it reaches the ledger - A stage-gated state machine from
INITthroughADJUDICATEDtoGATEDthat refuses out-of-order operations — patches are refused unless the state is adjudicated and the issue accepted - Domain packs generated per paper through
scaffold_domain_packandcreate_domain_pack, with generic packs for stochastic analysis, PDE, numerical analysis, optimization and machine-learning theory - A final gate computed from mechanical signals and accepted blockers, a self-contained HTML report, and a local web UI
Requirements
The PyPI package papercheck, version 0.3.4 — pipx install papercheck or pip install papercheck. Python 3.10+. Register the server with claude mcp add papercheck -- papercheck-mcp; the CLI entry point is papercheck and the server runs over stdio. No API keys: the harness makes no network calls of its own and runs no models.
Setup effort
One command — pipx install papercheck
USE CASES
Auditing a preprint before you post it
Run the full staged pipeline and get a verdict backed by a ledger, not a paragraph of impressions.
Stopping an agent from inventing problems
Every finding must quote text that exists in the source, or it never enters the ledger.
Checking a paper repository on every pull request
Run scan and the mechanical-only gate in CI, with nothing sent to any model provider.
Tailoring the audit to the paper's field
Have the agent draft a domain pack from the scan, then validate and store it.
8 tools
Listed in project docs. Your client may show a different list.
run_scanpropose_segmentssubmit_issueadjudicate_issuerun_gatescaffold_domain_packcreate_domain_packBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
pipx install papercheckMCP Clients
Claude Code
claude mcp add papercheck -- papercheck-mcp