# Replication Radar (pypi · replication-radar)

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

- Trust score: 50/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `replication-radar`: 50/100 (this document), [markdown](https://verifymcp.io/servers/org-sciencelive4all-replication-radar/replication-radar.md), [page](https://verifymcp.io/servers/org-sciencelive4all-replication-radar/replication-radar)

## Channel facts

- Registry: `pypi`
- Package: `replication-radar`
- Version: `0.4.7`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1091 tokens (~181/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Replication Radar MCP server?

Replication Radar runs locally as a PyPI package, launched with uvx replication-radar. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add org-sciencelive4all-replication-radar -- uvx replication-radar
```

### Cursor

```json
{
  "mcpServers": {
    "org-sciencelive4all-replication-radar": {
      "command": "uvx",
      "args": [
        "replication-radar"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-sciencelive4all-replication-radar": {
      "command": "uvx",
      "args": [
        "replication-radar"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add org-sciencelive4all-replication-radar -- uvx replication-radar
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-sciencelive4all-replication-radar": {
      "type": "local",
      "command": [
        "uvx",
        "replication-radar"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-sciencelive4all-replication-radar --command uvx --arg replication-radar
```

### Hermes

```yaml
mcp_servers:
  org-sciencelive4all-replication-radar:
    command: "uvx"
    args: ["replication-radar"]
```

### Netclaw

```json
{
  "McpServers": {
    "org-sciencelive4all-replication-radar": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "replication-radar"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-sciencelive4all-replication-radar -t stdio -c uvx -a replication-radar
```

### Other

```json
{
  "mcpServers": {
    "org-sciencelive4all-replication-radar": {
      "command": "uvx",
      "args": [
        "replication-radar"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 50)

First indexed and scored.

## MCP tools (6)

### `radar` (~112 tokens)

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.

Input parameters:

- `limit` (integer)
- `topic` (string, required)

### `find_independent_software` (~159 tokens)

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

Input parameters:

- `doi` (string)
- `limit` (integer)
- `topic` (string)

### `replication_status` (~236 tokens)

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 / contested / refuted, with confirm/partial/
    contradicted counts (so you can say *how robustly* it held, not just that it did).
  \- `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.

Input parameters:

- `doi` (string, required)

### `verified_claims` (~64 tokens)

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` (~403 tokens)

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.

Input parameters:

- `dataset` (string)
- `doi` (string)
- `owner` (string)
- `software` (string)
- `topic` (string)

### `find_dataset` (~117 tokens)

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.

Input parameters:

- `topic` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/org-sciencelive4all-replication-radar/replication-radar#diagnostics

## Score history

- 2026-09-21: 50

## Common questions

### What is the Replication Radar MCP server?

Replication Radar is an MCP server listed in the public MCP registry as org.sciencelive4all/replication-radar. Turn the OpenAIRE Graph into a ranked replication queue with a Science Live verification overlay. This page covers its PyPI package (replication-radar).

### Is the Replication Radar MCP server safe to use?

Replication Radar scores 50 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Replication Radar MCP server expose?

Replication Radar exposes 6 tools: radar, find_independent_software, replication_status, verified_claims, replication_template, find_dataset. Their descriptions and schemas cost roughly 1,091 tokens of context every time the server is loaded.

### Is the Replication Radar MCP server still maintained?

Replication Radar is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Replication Radar MCP server under?

Replication Radar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/replication-radar/
- Socket report: https://socket.dev/pypi/package/replication-radar
- Repository: https://github.com/ScienceLiveHub/replication-radar
- Website: https://openaire-hackathon.netlify.app/
- Changelog RSS feed: https://verifymcp.io/servers/org-sciencelive4all-replication-radar/replication-radar.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-sciencelive4all-replication-radar/replication-radar.json
- HTML version of this page: https://verifymcp.io/servers/org-sciencelive4all-replication-radar/replication-radar