MCP.Market

Replication Radar MCP server

by sciencelive4all.org·org.sciencelive4all/replication-radar·v0.4.8

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

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

0 stars171 downloads/wk

Reviews

Write one

Nobody has reviewed Replication Radar yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Replication Radar tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • 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 describ

  • 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 D

  • radar

    Impact-ranked replication targets in a research field.

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

  • 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://githu

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

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

no findings
  • Code scan20 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 6 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Replication Radar compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
171
more than 73% of 12,191 servers with a package

What its tools let an agent do: 6 read

Release history: 2 versions in the registry since 2026-09-21, latest 2026-10-25, typically one every 35 days.

Install Replication Radar in Claude Code, Cursor or VS Code

claude mcp add replication-radar -- uvx replication-radar
Add to Cursor

What the publisher says

From the Replication Radar repository's README, as published. We do not edit it. Read it on GitHub

Replication Radar

<!-- mcp-name: org.sciencelive4all/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

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Replication Radar: common questions

Is Replication Radar MCP server safe?
Mostly: it is graded B (80/100). Read the Replication Radar safety report
How do I install Replication Radar?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Replication Radar need an API key?
Yes. The registry entry asks for GITHUB_TOKEN.
Is Replication Radar maintained?
The last commit was 9 days ago (2026-10-25). The latest release is v0.4.8.
How does Replication Radar compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.