Doiget vs Research Chain
A side-by-side look at the Doiget and Research Chain MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Doiget for research work as a local process; choose Research Chain for research as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Doiget when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
Choose Research Chain when
- You need dedicated capabilities in the Research domain.
- You prefer a local stdio subprocess transport.
- You want tools like
paper, pmc_full_text, datasets.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Research | Research |
| Quality signal | 44/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View Doiget | View Research Chain |
Tools & capabilities
Doiget tools
No tool names declared yet. Check the project README from the listing page.
Research Chain tools 7
papertitle, journal, publisher, authors, Crossref's stated license(s)pmc_full_text`{has_full_text, pmcid, pmid, url}` from NCBI's IDdatasets`{total, returned, results[]}` from DataCite'scode`{zenodo[], paperswithcode}`. Zenodo is searched byciting`{count, top[], note}` from Semantic Scholar: `count` is theretractionderived from the SAME Crossref record already fetched foras_ofISO timestamp of the call.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Doiget
{
"mcpServers": {
"doiget-2": {
"command": "npx",
"args": [
"-y",
"doiget-cli"
]
}
}
}
Research Chain
{
"mcpServers": {
"research-chain": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-research-chain"
]
}
}
}
Frequently asked questions
Doiget is categorized under Research and uses a local stdio subprocess. Research Chain belongs to Research and uses a local stdio subprocess. Pick Doiget for research work and Research Chain for research.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Doiget has no declared pricing — check the project's own site. Research Chain has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add doiget-2 and research-chain as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Doiget has a quality signal of 44/100 (Fair) with 1 views, 0 installs and 2 GitHub stars. Research Chain has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.