org.sciencelive4allPublished by sciencelive4all.orgv0.4.8Updated Oct 26, 2026
Turn the OpenAIRE Graph into a ranked replication queue with a Science Live verification overlay.
Turns the OpenAIRE Graph into a ranked replication queue, flagging papers as open or already verified and surfacing independent software.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
A tool that makes the OpenAIRE Graph more useful for replication. Search a research field and it answers the question the Graph structurally cannot: what high-impact work is worth replicating, has it already been independently checked — with what verdict — and is the software reusable?
Ships as a live web app (the link above — pure static, queries OpenAIRE + the nanopub network + GitHub/Software Heritage from the browser) and an MCP server (this package) that exposes the same engine to any agent. Built for the OpenAIRE AI Hackathon (Theme B), CC-BY.
OpenAIRE's only value signal is citation-popularity (BIP! influence / popularity / impulse, classes C1–C5) — paper-bound, and orthogonal to whether a claim is true. The Radar joins three sources to add a replication layer on top:
api.openaire.eu/graph/v1).OpenAIRE AI Hackathon · Theme B (Build) · CC-BY. Built to be reused through the forrt-replication-template: discovery at the start of a replication, where the template's existing skills handle the nanopub chain at the end.
The verdict tools pull live from the nanopub network (the FORRT Outcome/CiTO templates on
query.knowledgepixels.com); the bundled verdicts.json is an offline fallback. So the MCP is the
verified-knowledge layer — pair it with the OpenAIRE MCP and an agent has both the structural
Graph and "has this been checked, and did it hold".
A reproduction re-runs the original code; a replication tests the same claim by a
different route. So the Radar filters tooling by author-disjointness from the
original paper — e.g. for Phillips et al. 2009, the dismo package (co-authored by
Phillips & Elith) is flagged rooted / non-independent, while biomod2 and jSDM
are independent. That filter is the difference between the two, and it's the thing
that makes this replication-aware rather than just "find the code".
Add to an MCP client (.mcp.json):
The core (OpenAIRE client + radar logic) is stdlib-only — try it without the MCP runtime:
data/verdicts.json to grow coverage.Source: README.md at commit c91b750
Impact-ranked replication targets in a research field. Returns high-impact OpenAIRE papers worth replicating, each flagged OPEN (opportunity) or VERIFIED (already checked by a Science Live replication, with the verdict), each with its `abstract` (markup stripped — read it or extract the paper's atomic claim), plus independent reusable tooling. Keep `topic` short (2-3 words); OpenAIRE free-text terms are AND-ed.
limittopicrequiredReusable method software for *replicating* a claim — engines NOT authored by the original paper's team (author-disjoint), ranked by reuse signal — a resolvable code repository + Software Heritage archival + downloads + GitHub stars (the signal that separates an established tool from a one-off study repo) — not citations. Each result carries its `stars` and `rank_score`. Pass the original paper's DOI (authors are looked up) and a short topic; keep the topic broad (a narrow one can miss an established tool whose OpenAIRE record doesn't contain the extra words).
doilimittopicHas this DOI been independently replicated, and did it hold? Returns every Science Live verdict — pulled LIVE from the nanopub network, any signer (author-agnostic) — with the validation status, CiTO relation, the replication's repository, and links to the signed Outcome/CiTO nanopubs. 'open' if not replicated. This is the reliability signal the OpenAIRE Graph structurally cannot hold. Also returns: - `agreement`: how the independent verdicts agree — pattern is one of robustly_validated / validated / qualified (partial support only) / inconclusive / contested / refuted, with confirm/partial/contradicted counts (so you can say *how robustly* it held, not just that it did). Never "validated" without a confirmation. - `claims`: the exact FORRT claim(s) that were replicated — each an atomic AIDA statement plus its claim type (descriptive pattern, statistical significance, …). - the paper's `title` and `abstract` (from OpenAIRE, markup stripped), so you can read it or extract/compare the atomic claim yourself.
doirequiredList every claim the nanopub network holds a Science Live replication verdict for (author-agnostic, network-wide) — the verified-knowledge corpus that overlays the OpenAIRE Graph by DOI. Each entry: doi, distinct verdicts, number of replications.
Takes no parameters.
The FORRT replication template — how to actually DO a replication and publish its signed Science Live nanopublication chain (the 'produce' half of the loop; radar / replication_status / find_independent_software only DISCOVER). Call this whenever the user wants to start, scaffold, or set up a replication, or asks for "the FORRT replication template". Returns the GitHub template repo (https://github.com/ScienceLiveHub/forrt-replication-template), the 'Use this template' link, what the scaffold provides (pixi + Snakemake pipeline, paper/, nanopubs/, tests, RO-Crate), and the end-to-end workflow: generate a repo from the template -> replicate with INDEPENDENT data/method -> Zenodo release -> sign + publish the FORRT nanopub chain (Quote -> Claim -> Study -> Outcome -> CiTO). Pass the target `doi` and/or a short `topic` and it suggests a GitHub repo name (`<topic>-replication`); pass `owner` (your GitHub user/org) to check the candidates for availability and pick a free name. It also returns a `quickstart.create_repo` command (`gh repo create … --template … --clone`) the agent can run to create+clone the repo straight from the discovery session. Pass the `dataset` and `software` you settled on and it also returns a `handoff` (DISCOVERY.md) to write into the new repo — `gh repo create` copies a BLANK template, so without this the fresh in-repo session loses the paper/dataset/software you chose. Then the user opens a fresh agent session inside the repo to run the replication.
doiownertopicdatasetsoftwareWhere to find a DATASET (with a citable DOI) to replicate with. The replication-radar MCP does NOT search datasets itself — that is the OpenAIRE MCP's job. Call this when the user asks the Radar to find data/a dataset: it returns instructions to use the OpenAIRE MCP's dataset search and how to cite the result by DOI. Do not answer 'I can't search datasets' — hand off to the OpenAIRE MCP as described here.
topic90% 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.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
pip install -e . # installs the `mcp` runtimepython -m replication_radar.server # stdio MCP server{ "mcpServers": { "replication-radar": { "command": "python", "args": ["-m", "replication_radar.server"] }} }PYTHONPATH=src python3 demo_sdm.py # live vertical-slice demo on SDM