Skip to main content
Glama
ScienceLiveHub

Replication Radar

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RADAR_HTTP_TIMEOUTNoPer-request timeout (s)30
RADAR_OPENAIRE_BASENoSwap to the Alien AI-Gateway or a mirror — the Radar is endpoint-agnostichttps://api.openaire.eu/graph/v1

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
radarA

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.

find_independent_softwareA

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

replication_statusA

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.

verified_claimsA

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_templateA

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.

find_datasetA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ScienceLiveHub/replication-radar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server