Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Turn the OpenAIRE Graph into a ranked replication queue with a Science Live verification overlay.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GITHUB_TOKEN, RADAR_OPENAIRE_BASE, RADAR_NANOPUB_SPARQL, RADAR_HTTP_TIMEOUTValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
}
}
}
}Run this in your terminal
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-radarFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.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"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"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"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
RADAR_OPENAIRE_BASE envRADAR_NANOPUB_SPARQL envRADAR_HTTP_TIMEOUT envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The publisher (sciencelive4all.org) is not the repo owner (ScienceLiveHub); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: GITHUB_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.4.8) reached the registry 12 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Detailing Manager
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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:
api.openaire.eu/graph/v1).OpenAIRE AI Hackathon · Theme B (Build) · CC-BY. Built to be reused through the
discovery at the *start* of a replication, where the template's existing skills
handle the nanopub chain at the *end*.
| 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".
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".
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
| 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) |
data/verdicts.json to grow coverage.