Replication Radar

Name: Replication Radar
Author: ScienceLiveHub

作者：ScienceLiveHub版本 0.4.8i★ –i在你的电脑上运行

注册名称org.sciencelive4all/replication-radar

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 0 项依据公开信息检查；尚未扫描代码
使用情况i非常新↓ 26/周 · ★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：GITHUB_TOKEN

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 0 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： GITHUB_TOKEN, RADAR_OPENAIRE_BASE, RADAR_NANOPUB_SPARQL, RADAR_HTTP_TIMEOUT

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "replication-radar": {
      "command": "uvx",
      "args": [
        "replication-radar"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value",
        "RADAR_OPENAIRE_BASE": "your-value",
        "RADAR_NANOPUB_SPARQL": "your-value",
        "RADAR_HTTP_TIMEOUT": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add replication-radar --env GITHUB_TOKEN=your-value --env RADAR_OPENAIRE_BASE=your-value --env RADAR_NANOPUB_SPARQL=your-value --env RADAR_HTTP_TIMEOUT=your-value -- uvx replication-radar

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "replication-radar": {
      "command": "uvx",
      "args": [
        "replication-radar"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value",
        "RADAR_OPENAIRE_BASE": "your-value",
        "RADAR_NANOPUB_SPARQL": "your-value",
        "RADAR_HTTP_TIMEOUT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "replication-radar": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "replication-radar"
      ],
      "env": {
        "GITHUB_TOKEN": "your-value",
        "RADAR_OPENAIRE_BASE": "your-value",
        "RADAR_NANOPUB_SPARQL": "your-value",
        "RADAR_HTTP_TIMEOUT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

GITHUB_TOKEN 机密 env
Optional GitHub token for higher API rate limits (RADAR_GITHUB_TOKEN also accepted)
RADAR_OPENAIRE_BASE env
OpenAIRE Graph API base (default: https://api.openaire.eu/graph/v1)
RADAR_NANOPUB_SPARQL env
Nanopub SPARQL endpoint (default: https://query.knowledgepixels.com/repo/full)
RADAR_HTTP_TIMEOUT env
Per-request timeout in seconds (default: 30)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

! 注意
作者与仓库一致
发布者（sciencelive4all.org）不是仓库所有者（ScienceLiveHub）；可能是其他人代为上架的
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18630 个服务器的 0%
发布到注册中心的时间比此分类中其他 18630 个服务器的 74% 更新
基础检查结果等于或优于此分类中其他 18630 个服务器的 16%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Replication Radar 安全吗？

它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：GITHUB_TOKEN

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.4.8）于14天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, CloudGPU MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

CloudGPU MCP

Rent a per-minute GPU from your MCP client, run a job, download results, shut it down.

作者：mrhy7176起步阶段↓ 922/周今天更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Replication Radar

🔗 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

Tool	What 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 `-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

pip install -e .                       # installs the `mcp` runtime

python -m replication_radar.server # stdio MCP server

Add to an MCP client (.mcp.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:

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

Configuration

Env var	Default	Purpose
`RADAR_OPENAIRE_BASE`	`https://api.openaire.eu/graph/v1`	Swap to the Alien AI-Gateway or a mirror — the Radar is endpoint-agnostic
`RADAR_HTTP_TIMEOUT`	`30`	Per-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.

Replication Radar

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

CloudGPU MCP

作者的 README

Replication Radar

🔗 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

Tools

The reproduction-vs-replication distinction, made computable

Run

Configuration

Known limits (v1, honest)