Read-only lookup of OpenRepro's re-run reports on whether published computational research reproduces, with claims, outcomes and evidence.
What you can do
Look up a paper by arXiv ID, DOI, URL, title or common name and get its re-run outcome, qualifiers, assurance level and claim counts
Search published re-runs by title, author, venue or field, or list the whole ledger
Read the full public record for one paper: claims checked, published and re-run values, tolerances, verdicts, attempt history and evidence links
Get the log's final hash, the evidence bundle, the report's SHA-256 and the command that verifies the bundle
Generate a ready-to-send email link to request a re-run for a paper not yet in the ledger
When to use it
Useful when a user asks whether a paper's results replicate, reproduce or hold up, or wants the claim-by-claim evidence behind such a verdict. Also handy for checking the integrity of a published report before relying on it.
Requirements
Remote streamable HTTP endpoint; no package, account, API key or environment variable is declared. A client that can reach the OpenRepro endpoint is enough.
Before you install
Outcomes come from AI-agent re-runs in a sandbox, not independent domain-expert review, and controls and gates are agent-designated and unreviewed; qualified outcomes should not be shortened to a bare yes. The verifier checks log and artifact integrity, not the report's contents. request_rerun only produces an email link; nothing is sent or stored by the tool.
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/io.github.openrepro%2Fledger/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.
Look up one paper in the OpenRepro ledger and return its re-run outcome with its qualifiers (such as a broad bound or a check that missed), how many agent-designated controls were excluded and how many gates the test had (when it has any), how many headline claims held, the assurance level, and links to the report and evidence. Matches arXiv IDs, DOIs, URLs, titles, short names and aliases. With no exact match it returns close matches when there are any, and says the paper is not in the ledger only when there are none.
Parameterspaperrequired
search_reports
Search the OpenRepro ledger
Search published re-runs by words in the title, authors, venue or field, optionally filtered by outcome or field. With no query, lists the whole ledger.
Parametersfieldlimitqueryoutcome
get_report
Get a full re-run report
The full public record for one paper: outcome and qualifiers, summary, assurance, the attempt history (released and superseded versions with reasons), every claim checked with the published value, the re-run value, the registered tolerance, the check kind and the verdict, plus evidence links.
Parameterspaperrequired
how_to_verify
How to verify a report's evidence
The log's final hash, the downloadable evidence bundle, the report's SHA-256 from the release manifest, and the one command that checks the bundle with only Python. The verifier checks log and artifact integrity and that the report names the log's head hash; it does not check the report's contents against the log.
Parameterspaperrequired
request_rerun
Request a re-run of a paper
For a paper not yet in the ledger: returns a ready-to-send email link to OpenRepro with the request filled in. Nothing is sent or stored by this tool; the user sends the email if they want to.
Parameterswhypaperrequired
Version history
1
v0.2.0LatestNov 11, 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.