Replication Radar

org.sciencelive4all由 sciencelive4all.org 发布v0.4.8更新于 Oct 26, 2026

Turn the OpenAIRE Graph into a ranked replication queue with a Science Live verification overlay.

概览

AI 生成的概览

把 OpenAIRE Graph 变成按影响力排序的复现队列,标注论文是待复现机会还是已有验证结论,并找出独立软件。

可以做什么
  • 按研究领域列出高影响力论文作为复现目标,并标注为待复现机会或已验证及其结论
  • 查询某个 DOI 是否已被独立复现、结论是否成立,结论实时取自 nanopub 网络
  • 列出整个已验证主张语料库,含结论与复现次数
  • 查找非原作者团队编写的可复用方法软件,按代码仓库、归档、下载量与星标排序
  • 提供 FORRT 复现模板及建议的脚手架仓库名称,用于启动复现
  • 指引使用 OpenAIRE MCP 查找可引用的数据集 DOI
适用场景
适合在规划或界定复现研究时使用:挑选值得重测的高影响力主张、确认某主张是否已被检验及结果如何、以及寻找独立于原作者的可用工具。
运行要求
以 Python 包形式通过 stdio 在本地运行,需用 pip 安装并启动模块。需要访问 OpenAIRE Graph API、nanopub SPARQL 端点以及 GitHub 与 Software Heritage 的网络。可选 GitHub 令牌可提高 API 速率限制;超时与端点可通过环境变量调整。
安装前请注意
可选 GitHub 令牌属于凭据,只应通过环境变量提供。结果基于启发式:检索受关键词限制,工具与数据集按主题和作者独立性匹配而非图关系,内置结论索引仅覆盖少量成果。该服务器读取公开研究数据,未见写入或删除操作。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Replication Radar,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Replication Radar

[DOI] [PyPI]

🔗 Live demo → https://openaire-hackathon.netlify.app

▶ Watch the 3-min demo → https://youtu.be/hVyLafY3Y3E · reproduce it step by step → https://openaire-hackathon.netlify.app/demo.html

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:

  • OpenAIRE Graph — impact-ranks candidate papers (api.openaire.eu/graph/v1).
  • Software Heritage + repo signals — surfaces reusable method software.
  • Science Live nanopub verdicts — the "already checked → did it hold" overlay.

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.

Tools

ToolWhat it answers
radar(topic)Impact-ranked replication targets in a field — each OPEN (opportunity) or VERIFIED (done, with verdict) + independent tooling + funder context
find_independent_software(doi, topic)Reusable engines not authored by the original team (author-disjoint = replication, not reproduction), ranked by reuse signal — repo · Software Heritage · downloads · GitHub stars — not citations (returns stars + rank_score)
replication_status(doi)Has this DOI been replicated, did it hold? Verdict(s) — live from the nanopub network, any signer — with status, CiTO relation, repo, and signed Outcome/CiTO nanopub links; open if not
verified_claims()The whole verified-knowledge corpus — every claim the network holds a verdict for (author-agnostic)
replication_template(doi, topic, owner)The FORRT replication template (the produce half) — the scaffold repo, the workflow, and a suggested <topic>-replication repo name (checks availability under owner)
find_dataset(topic)Hand-off to the OpenAIRE MCP for datasets — replication-radar doesn't search datasets; this says how to find a citable dataset DOI there

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".

The reproduction-vs-replication distinction, made computable

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".

Run

bash
pip install -e .                       # installs the `mcp` runtimepython -m replication_radar.server     # stdio MCP server

Add to an MCP client (.mcp.json):

json
{ "mcpServers": {  "replication-radar": { "command": "python", "args": ["-m", "replication_radar.server"] }} }

The core (OpenAIRE client + radar logic) is stdlib-only — try it without the MCP runtime:

bash
PYTHONPATH=src python3 demo_sdm.py     # live vertical-slice demo on SDM

Configuration

Env varDefaultPurpose
RADAR_OPENAIRE_BASEhttps://api.openaire.eu/graph/v1Swap to the Alien AI-Gateway or a mirror — the Radar is endpoint-agnostic
RADAR_HTTP_TIMEOUT30Per-request timeout (s)

Known limits (v1, honest)

  • Keyword-bound discovery. OpenAIRE free-text terms are AND-ed; long queries return nothing. Use short topics. The VERIFIED overlay is guaranteed (resolved from the verdict index directly), but OPEN-target recall depends on the query.
  • No graph-relation traversal on the public API (paper→its software/data/grant edges aren't exposed): tooling/data are matched heuristically by topic + author independence, not by a hard relation. Upgrades cleanly if a gateway exposes relations.
  • Funder context is field-level, not per-paper (per-paper funder attribution is not reachable); budgets are frequently reported as 0 in records.
  • The verdict index ships 6 source works / 12 chains (Science Live). Extend data/verdicts.json to grow coverage.

来源:README.md,提交 c91b750

工具

6

radar

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.

输入参数limittopic必填

find_independent_software

Reusable 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).

输入参数doilimittopic

replication_status

Has 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.

输入参数doi必填

verified_claims

List 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.

无需输入参数。

replication_template

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.

输入参数doiownertopicdatasetsoftware

find_dataset

Where 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.

输入参数topic

版本历史

2
  1. v0.4.8最新Oct 26, 2026
  2. v0.4.7Sep 21, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分