
Research Chain MCP server
online · 100% uptimeOne call, one paper: everything openly available around it — full text, license, datasets, code…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Research Chain yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Research Chain tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Research Chain compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 66 ms
- faster than 90% of 30,031 servers
Release history: 4 versions in the registry since 2026-09-16, latest 2026-10-29, typically one every 8 days.
Install Research Chain in Claude Code, Cursor or VS Code
claude mcp add --transport http research-chain https://gateway.pipeworx.io/research-chain/mcp
What the publisher says
From the Research Chain repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/research-chain
Everything openly available around one academic paper, in a single call: full text, license, datasets, code, and citations. Given a DOI, PMID, or arXiv id, research_chain walks the join that Crossref, OpenAlex, Unpaywall, DataCite, Zenodo, Hugging Face Papers, PubMed Central, and Semantic Scholar each expose piecemeal — so a caller no longer has to know all six/seven tools to answer "what datasets and code are linked to this paper?" or "find an open copy of this DOI and its license."
Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.
Tools
returns:
- researchchain({doi | pmid | arxivid, maxdatasets?, maxciting?}) —
(URL + which manuscript version each applies to), OpenAlex concepts and citation count.
- paper — title, journal, publisher, authors, Crossref's stated license(s)
with its OWN hosttype, version (publishedVersion | acceptedVersion | submittedVersion), and license — never collapsed. isoa: true only means "a free-to-read copy exists somewhere"; it says nothing about reuse rights, which is why license is null (not guessed) whenever Unpaywall doesn't state one. A PubMed Central copy (if one exists) is added as its own entry with license and version explicitly null, since NCBI's ID Converter confirms the copy exists but doesn't state its terms.
- open_copies[] — every open-access location Unpaywall knows about, each
Converter.
- pmcfulltext — {hasfulltext, pmcid, pmid, url} from NCBI's ID
relatedIdentifiers search (datasets/software that cite the paper's DOI). total is the real upstream count even when results is truncated to max_datasets.
- datasets — {total, returned, results[]} from DataCite's
metadata.relatedidentifiers.identifier. paperswithcode (Hugging Face Papers, the de-facto successor) reports {found: false, results: []} when the upstream search comes back empty — an empty result is notfound, never treated as an answer (a bare [] from this upstream used to be routed to as if it were a real "no code exists" answer).
- code — {zenodo[], paperswithcode}. Zenodo is searched by
paper's total citation count, top is up to max_citing citing papers sorted by their own citation count. note carries an honest partial- failure message (e.g. a rate limit) when one of the two Semantic Scholar calls failed but the other succeeded — it is never silently dropped.
- citing — {count, top[], note} from Semantic Scholar: count is the
paper (title marker, update-to retraction notices, is-retracted-by relation) — no extra API call. retracted: false means "no retraction on record", not proof the paper is clean (coverage depends on the publisher).
- retraction — derived from the SAME Crossref record already fetched for
in parallel; a slow or dead upstream lands in sources_failed with a reason, and every other leg still returns.
- sourcesused / sourcesfailed — every leg fetches independently and
- as_of — ISO timestamp of the call.
Auth
Keyless. Every upstream here is a public, unauthenticated API. Crossref, OpenAlex, and the NCBI ID Converter ask only for a polite-pool contact email, which this pack supplies as its own (hello@pipeworx.io) — the same pattern as the crossref, openalex, and unpaywall packs.
Data sources
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Research Chain: common questions
- Is Research Chain MCP server safe?
- Mostly: it is graded B (77/100). Read the Research Chain safety report
- How do I install Research Chain?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Research Chain need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Research Chain maintained?
- The last commit was 39 days ago (2026-09-26). The latest release is v0.2.0.
- Is Research Chain up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Research Chain compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 66 ms (faster than 90% of 30,031 servers). Full comparison.