MCP.Market

doiget MCP server

by QAtlasHub·io.github.QAtlasHub/doiget·v0.9.0·2 stars

OA-first paper fetcher: DOIs/arXiv IDs to local PDFs + metadata via Open Access APIs.

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
New

2 stars

Reviews

Write one

Nobody has reviewed doiget yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

doiget tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How doiget compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,243 servers
GitHub stars
2
more than 75% of 28,706 servers

Release history: 2 versions in the registry since 2026-09-01, latest 2026-10-01, typically one every 30 days.

Install doiget in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the doiget repository's README, as published. We do not edit it. Read it on GitHub

doiget

A single-binary CLI + stdio MCP server that turns DOIs and arXiv ids into local PDFs through official, OA-first APIs.

Designed as the agent-facing companion to BiblioFetch.jl.

Docs: stable = the Zola site (built from main); dev = rustdoc built from next; API = docs.rs (latest published release).

Status: Shipping on crates.io (doiget-core, doiget-cli, doiget-mcp), with sigstore-signed binaries + an SBOM attached to the GitHub Release. Tier 1 + Tier 2 sources, the stdio MCP server, citation-graph expansion, and gated TDM sources are all implemented. Releases are cut by a single signed git tag through the tag-driven pipeline (see ADR-0025); release-plz was retired. See CHANGELOG.md for history and docs/PHASES.md for the phase plan.

Posture

doiget is a general-purpose automation tool for retrieving papers via official publisher APIs. By design, doiget only attempts retrieval through:

  1. Public Open Access sources (default — Crossref, Unpaywall, arXiv).
  2. Credentials the user has personally configured for their own institutional or personal subscriptions (opt-in, compile-time gated).

doiget does not work around any access control mechanism, redistribute papers, host content, operate as a SaaS, or bundle any publisher API keys.

Users are responsible for ensuring they have the right to access the content they request and for compliance with each source's Terms of Service.

See docs/LEGAL.md and docs/SCOPE.md.

Documentation

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

doiget: common questions

Is doiget MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the doiget safety report
Does doiget need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is doiget maintained?
The last commit was 10 days ago (2026-10-26). The latest release is v0.9.0.
How does doiget compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,243 servers); github stars 2 (more than 75% of 28,706 servers). Full comparison.