Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

doiget

MCPB · DOIGET-0.9.0.MCPB

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

Available components

−3 this week 50 Trust /100

Last scanned (22 hours ago)

Scores higher than 80% of MCPB servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 33 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 7322 tokens (~332/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 2 Nov 26 0
    • Provenance: unverified → fail ▼ security
  • 1 Nov 26 0
    • Provenance: fail → unverified ▼ security
  • 31 Oct 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 30 Oct 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 29 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed mcpb/https://github.com/QAtlasHub/doiget/releases/download/v0.9.0/doiget-0.9.0.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 22 exposed · ~7,158 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
doiget_annotate ~244

WHEN TO USE: Attach or clear a freeform annotation / note on a stored paper for local knowledge-base organisation (#294). INPUTS: ref (DOI or arXiv id); text (string — the annotation; omit or set to null to clear); clear (bool, default false — explicitly clear the annotation). OUTPUTS: { ok: true, ref, annotation } OR { ok: false, error }. COSTS: 0 network requests; one store read + write. SIDE EFFECTS: Overwrites [doiget].annotation in <store>/.metadata/<safekey>.toml. LIMITS: Entry must already exist in the store. Setting text overrides any existing annotation.

NameTypeReqDescription
clearboolean|null–Set to `true` to clear (remove) the annotation instead of setting it.
refstringyesDOI or arXiv id. Validated via `Ref::parse`; failures surface as `INVALID_REF`.
textstring|null–Annotation text. Replaces any existing annotation. Omit or set to null together with `clear: true` to remove the annotation.

No output schema declared.

No examples provided.

doiget_batch_fetch ~383

WHEN TO USE: User wants to fetch many papers in one call (up to 100). INPUTS: refs (array of up to 100 DOIs / arXiv ids), dry_run (optional bool), force (optional bool: ask again even if this session was just answered on the ref; without it such a repeat is replayed as ok:false with replayed:true, #507). OUTPUTS: { ok: true, results: [{ref, ok, ...}] } OR { ok: true, dry_run: true, plans: [{ref, plan, rate_limit_budget}] } OR { ok:false, error }. COSTS: 1-3 s per ref, bounded by the 5/sec global rate cap. SIDE EFFECTS: Writes PDFs / metadata TOMLs to the store (unless dry_run). Appends one provenance row per attempt. LIMITS: Max 100 refs per call (TOO_MANY_REFS otherwise). Per-ref errors are reported in `results` and do NOT fail the whole call.

NameTypeReqDescription
dry_runboolean–When `true`, return one [`FetchPlan`](doiget_core::dry_run::FetchPlan) per ref without touching the network or store.
forceboolean–Ask even if this session was already answered on the ref with something a retry cannot change yet (#507). Without it such a repeat returns `ok:false` with `replayed: true` and the earlier code; with…
refsarrayyesList of DOI / arXiv id refs. Max [`MAX_BATCH_REFS`] entries; the cap is enforced inside the tool handler so a 101st ref surfaces as an `INVALID_REF` envelope (rather than a JSON schema reject).

No output schema declared.

No examples provided.

doiget_batch_from_bibliography ~448

WHEN TO USE: User has a Zotero / Mendeley CSL-JSON export and wants to fetch all OA-resolvable entries. INPUTS: path (absolute path to .bib / .csl / .json), format ("auto" | "csl-json" | "bibtex" | "refs", default "auto"), strict (bool, default false), force (optional bool, as for doiget_batch_fetch). OUTPUTS: { ok: true, summary:{total,ok,failed,parse_errors}, results: [{entry_key, ref, ok, ...}] } OR { ok:false, error }. COSTS: Same as batch_fetch — 1-3 s per entry, bounded by the 5/sec global rate cap. SIDE EFFECTS: Writes PDFs / metadata TOMLs to the store. Appends one provenance row per attempt. LIMITS: bibtex parsing is not yet shipped (re-export as CSL-JSON). Per-entry parse errors are reported in results unless strict=true.

NameTypeReqDescription
forceboolean–Ask even if this session was already answered on the ref with something a retry cannot change yet (#507). Without it such a repeat returns `ok:false` with `replayed: true` and the earlier code; with…
formatstring|null–Optional format override. Accepted tokens (case-insensitive): `auto` (default — extension + content fingerprint), `csl-json`, `bibtex`, `refs`. Anything else surfaces as `INVALID_REF`.
pathstringyesAbsolute path to a bibliography file. CSL-JSON (.json / .csl) is supported in slice 1; BibTeX (.bib) returns a structured "not yet implemented" error pending the biblatex-crate slice.
strictboolean–`true` aborts on the first per-entry parse error (no flushed successes); `false` (default) emits parse errors as `{ok:false, error:{code:INVALID_REF, ...}}` rows next to successful siblings.

No output schema declared.

No examples provided.

doiget_batch_resolve_citations ~296

WHEN TO USE: Resolve multiple free-form bibliographic citation strings in batch. INPUTS: queries (array of query strings), limit (maximum number of candidates per query, default: 5). OUTPUTS: { ok: true, results: [ { query, candidates: [ { doi, title, author, year, score, confidence, matched, source } ] } ] } OR { ok: false, error }. COSTS: 1-2 s round-trip per query. SIDE EFFECTS: none. LIMITS: Returns candidates with similarity score >= 0.5. At most 50 queries per call. BRANCH ON confidence, NOT score: the score is token overlap against your query string and 0.5 is the FLOOR, so the worst candidate this tool can emit still looks like a positive number. confidence is exact (every query token matched), probable (four in five), or weak (cleared the floor and no more) - for a known-item lookup a weak candidate is a near-miss, not a match, so verify it with doiget_resolve_paper before citing. matched lists which of your tokens were found, which is how you see whether the author and the journal were among them.

NameTypeReqDescription
limitinteger–Maximum number of candidates to return per query (default: 5).
queriesarrayyesBibliographic citation query strings.

No output schema declared.

No examples provided.

doiget_bibtex_export ~203

WHEN TO USE: Export already-fetched entries as BibTeX (one or many). INPUTS: refs (array of DOI / arXiv id strings, 1..=200). OUTPUTS: { ok: true, entries: [{ ref, safekey, bibtex }] } — bibtex is null when the entry is not in the store; a per-ref { ref, error } element is emitted for an invalid ref or a store read error. OR { ok:false, error } for a store-open failure. COSTS: <10 ms per entry, local read. SIDE EFFECTS: none. LIMITS: Entry must already have been fetched (bibtex:null otherwise — NOT an error). At most 200 refs per call.

NameTypeReqDescription
refsarrayyesDOIs / arXiv ids to render. 1..=200; each validated via `Ref::parse` with per-ref error reporting.

No output schema declared.

No examples provided.

doiget_capability_profile ~109

WHEN TO USE: Determine which sources the running doiget instance is allowed to use. INPUTS: none. OUTPUTS: { oa_enabled, metadata_sources, tdm_enabled, tdm_elsevier, tdm_aps, tdm_springer, rate_limit_per_sec } (plus additive ok, tier_1, tier_2, tier_3, tdm_ieee). COSTS: <1 ms. SIDE EFFECTS: none. LIMITS: none.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

doiget_csl_export ~214

WHEN TO USE: Export already-fetched entries as CSL JSON 1.0 (one or many). INPUTS: refs (array of DOI / arXiv id strings, 1..=200). OUTPUTS: { ok: true, entries: [{ ref, safekey, csl }] } — csl is a 1-element CSL JSON array, or null when the entry is not in the store; a per-ref { ref, error } element is emitted for an invalid ref or a store read error. OR { ok:false, error } for a store-open failure. COSTS: <10 ms per entry, local read. SIDE EFFECTS: none. LIMITS: Entry must already have been fetched (csl:null otherwise — NOT an error). At most 200 refs per call.

NameTypeReqDescription
refsarrayyesDOIs / arXiv ids to render. 1..=200; each validated via `Ref::parse` with per-ref error reporting.

No output schema declared.

No examples provided.

doiget_expand_citation_graph ~339

WHEN TO USE: Expand a DOI's citation neighborhood via OpenAlex BFS. INPUTS: ref (DOI), depth (optional 1-3, default 3), total (optional 1-100, default 100), per_paper (optional 1-20, default 20). OUTPUTS: { ok: true, ref, seed_work_id, nodes, edges, truncated, total_visited } OR { ok:false, ref, error }. COSTS: O(total) OpenAlex requests; expect 1-30 s for a depth-3 walk. SIDE EFFECTS: Emits one provenance row per consulted Work under Capability::Metadata. NEVER writes to the store. NEVER fetches PDF. LIMITS: ADR-0010 hard caps applied regardless of inputs: depth<=3, total<=100, per_paper<=20. Requires DOIGET_ENABLE_OPENALEX in env. Returns NOT_IMPLEMENTED when this binary was built without the `citation` Cargo feature.

NameTypeReqDescription
depthinteger|null–Max BFS depth (1..=3). Default is the ADR-0010 maximum (3).
per_paperinteger|null–Max children expanded per parent (1..=20). Default is the ADR-0010 maximum (20).
refstringyesDOI seed. arXiv ids are rejected with `INVALID_REF`.
totalinteger|null–Max total nodes (1..=100). Default is the ADR-0010 maximum (100). `truncated: true` is set on the response when this cap is hit.

No output schema declared.

No examples provided.

doiget_fetch_paper ~527

WHEN TO USE: User wants to download a paper PDF given a DOI or arXiv id. INPUTS: ref (DOI or arXiv id), dry_run (optional bool), force (optional bool: ask again even if this session was just answered on the ref; without it such a repeat is replayed as ok:false with replayed:true, #507). OUTPUTS: { ok: true, ref, source, path, license, size_bytes, schema_version, pdf, attempts } OR { ok: true, dry_run: true, ref, plan, rate_limit_budget } OR { ok:false, ref, error }. READ `pdf.status` — `ok: true` does NOT mean a PDF landed. `fetched` = PDF on disk; `no_oa_url` = metadata only, no free copy exists; `blocked` = a free copy EXISTS but was refused. ON `blocked`: do not report the paper as unavailable. `pdf.remediation` lists the config changes that would lift it, narrowest first — `additional_host` entries go under [[network.additional_hosts]] in the config file, a `trust_flag` is a [network] boolean. Show them to the user and let them choose; both widen the trusted download surface. `attempts` says which other sources were consulted and which were never asked (`consulted: false` + `detail` naming the env var to set). Use it before concluding a paper is not indexed anywhere. COSTS: 1-3 s network call (or 0 when dry_run). May fail if not Open Access. SIDE EFFECTS: Writes PDF (or metadata-only TOML) to the store. Appends a row to the provenance log (unless dry_run). LIMITS: Max 5 fetches/sec (global). Use doiget_batch_fetch for >5 refs.

NameTypeReqDescription
dry_runboolean–When `true`, returns a [`FetchPlan`](doiget_core::dry_run::FetchPlan) preview without touching the network or writing anything (ADR-0022). Defaults to `false`.
forceboolean–Ask even if this session was already answered on the ref with something a retry cannot change yet (#507). Without it such a repeat returns `ok:false` with `replayed: true` and the earlier code; with…
refstringyesDOI or arXiv id; validated via `Ref::parse`.

No output schema declared.

No examples provided.

doiget_health ~138

WHEN TO USE: Operational sanity check for the doiget MCP server. INPUTS: none. OUTPUTS: { ok: true, version, schema_version, store_writable, build: { version, channel, binary, method, manifest, manifest_matches, update, check } }. `build` says which binary answered and how to update it; compare `version` with the latest release only if the user asks (`build.check`). COSTS: <1 ms; no network. SIDE EFFECTS: none. LIMITS: store_writable is a best-effort probe of the nearest existing ancestor; it never creates the store.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

doiget_info ~165

WHEN TO USE: Inspect a stored entry's metadata locally; the entry must already have been fetched. INPUTS: ref (DOI or arXiv id). OUTPUTS: { ok: true, ref, safekey, metadata: <object>|null } OR { ok:false, ref, error }. COSTS: <10 ms local read. SIDE EFFECTS: none. LIMITS: A missing entry surfaces as { ok: true, metadata: null } — NOT an error envelope. Check `metadata !== null` to confirm presence; call doiget_fetch_paper first when `metadata` is null.

NameTypeReqDescription
refstringyesDOI or arXiv id. Validated via `Ref::parse`; failures surface as `INVALID_REF`.

No output schema declared.

No examples provided.

doiget_link ~239

WHEN TO USE: Given a published DOI, find whether the same work has a free arXiv preprint (to read it, or to dedup a preprint vs the journal version). INPUTS: ref (a DOI, e.g. "10.1103/PhysRevB.1"). OUTPUTS: { ok: true, doi, arxiv, openalex_id, title } (arxiv is null when no preprint) OR { ok:false, error }. COSTS: 1 OpenAlex request. SIDE EFFECTS: Emits a Metadata provenance row. NEVER writes the store; NEVER fetches a PDF. LIMITS: DOI input only (arXiv → DOI is a follow-up; an arXiv/invalid ref → INVALID_REF). A DOI with no OpenAlex work → NOT_FOUND.

NameTypeReqDescription
refstringyesA **DOI** (e.g. "10.1103/PhysRevB.1"), validated via `Ref::parse`. An arXiv id or unparsable ref returns `INVALID_REF` (arXiv → DOI is a follow-up).

No output schema declared.

No examples provided.

doiget_list_recent ~144

WHEN TO USE: List the most-recently fetched entries in the local store. INPUTS: limit (optional integer, default 50, max 200). OUTPUTS: { ok: true, count, entries: [{ safekey, title, year, fetched_at }] } OR { ok:false, error }. COSTS: <100 ms for a few thousand entries. SIDE EFFECTS: none. LIMITS: Returns at most `limit` entries (capped at 200).

NameTypeReqDescription
limitinteger|null–Maximum number of results to return. `None` means default (50); values >200 are clamped to 200.

No output schema declared.

No examples provided.

doiget_metadata_only ~809

WHEN TO USE: User wants metadata for a DOI / arXiv id without paying for or being noticed by a PDF download. INPUTS: ref (DOI or arXiv id), dry_run (optional bool), include_oa_location (optional bool). OUTPUTS: { ok: true, ref, source, license?, oa_url, oa_status, metadata } OR { ok: true, dry_run: true, ref, plan, rate_limit_budget } OR { ok:false, error }. COSTS: 1-2 s metadata round-trip (or 0 when dry_run; roughly doubled when include_oa_location). SIDE EFFECTS: Appends a 'metadata-only' provenance row (unless dry_run). Writes the metadata TOML to the store. Never fetches PDF. LIMITS: Subject to the same rate cap as fetch_paper (5/sec). The OA URL is reported but never followed. Crossref alone cannot supply an oa_url, because its link[] entries are scoped to a licensed programme (Similarity Check / TDM / syndication) rather than being general-purpose. A null oa_url is therefore NOT evidence that the work is closed. oa_url is null on the default path whenever Crossref answered, which is nearly every DOI. It can be non-null WITHOUT the flag in one case: Crossref failed and Unpaywall answered instead, and then source is unpaywall rather than crossref - so source tells you which happened. With include_oa_location set, oa_status says which answer you got: closed means the lookup completed and found no OA location, null means the lookup did not complete.

NameTypeReqDescription
dry_runboolean–When `true`, returns a [`FetchPlan`](doiget_core::dry_run::FetchPlan) preview without touching the network or writing anything (ADR-0022). Defaults to `false` (the production metadata-only path, curr…
include_oa_locationboolean–Consult Unpaywall for a real OA location, filling `oa_url`, `oa_status` and `license`. Costs one extra metadata round-trip. Defaults to `false`. On the default path `oa_url` is `null` whenever Cross…
refstringyesDOI or arXiv id. Validated via `Ref::parse`; failures surface as `INVALID_REF` per `docs/ERRORS.md`.

No output schema declared.

No examples provided.

doiget_paper_pdf_path ~225

WHEN TO USE: Locate the local PDF file for a stored entry (returns a path, NOT the PDF bytes). INPUTS: ref (DOI or arXiv id). OUTPUTS: { ok: true, ref, safekey, path: string|null, pdf_exists: bool, origin: string|null ("user-supplied" for a PDF added with doiget add; null when doiget fetched it), license: string|null } OR { ok:false, ref, error }. COSTS: <10 ms local read. SIDE EFFECTS: none. NEVER reads or transmits PDF bytes. LIMITS: Both 'no metadata entry' and 'metadata exists but PDF file missing' surface as { ok: true, path: null, pdf_exists: false } — call doiget_info to distinguish the two cases. Returns an ok:false envelope only on invalid ref / store-open failure.

NameTypeReqDescription
refstringyesDOI or arXiv id. Validated via `Ref::parse`; failures surface as `INVALID_REF`.

No output schema declared.

No examples provided.

doiget_paper_search ~624

WHEN TO USE: Discover papers on a topic via external OpenAlex search, abstract-first, before fetching any PDF. INPUTS: query (string); optional limit (1-200, default 25), from_year, to_year, oa_only (bool), min_citations, min_fwci (impact floor), min_percentile (0-100, top-X% in cohort), author, venue, publisher (names — resolved to OpenAlex ids), sort (relevance only — use min_fwci/min_percentile/from_year as filters, #290). OUTPUTS: { ok: true, scope: "external", query, total_results, count, results: [{ doi, openalex_id, arxiv, title, authors, year, venue, abstract, cited_by_count, oa_status, source }] } OR { ok:false, error }. COSTS: 1 OpenAlex request, plus 1 per supplied author/venue/publisher name to resolve. SIDE EFFECTS: Emits Metadata provenance rows. NEVER writes the store. NEVER fetches a PDF. LIMITS: Tier-1, always-on (no DOIGET_ENABLE_OPENALEX gate). An ambiguous author/venue/publisher name → AMBIGUOUS (candidates listed); no match → NOT_FOUND. ZERO RESULTS ARE NOT EVIDENCE OF ABSENCE: OpenAlex free-text matching degrades sharply past roughly 8 terms and returns nothing rather than a partial match. On total_results: 0, retry with 3-5 distinctive terms before concluding the work is not indexed; the envelope carries a `hint` saying so.

NameTypeReqDescription
authorstring|null–Author name (resolved to an OpenAlex author id).
from_yearinteger|null–Inclusive lower publication-year bound.
limitinteger|null–Maximum results (1..=200; default 25). Out-of-range is rejected.
min_citationsinteger|null–Only works cited strictly more than this many times.
min_fwcinumber|null–Minimum field-and-year-normalized impact (FWCI) — a quality filter (#290).
min_percentileinteger|null–Minimum within-cohort citation percentile (0–100): top-X% among same-year works; combine with `from_year` for "recent and standing out" (#290).
oa_onlyboolean|null–Restrict to open-access works.
publisherstring|null–Publisher name (resolved to an OpenAlex publisher id).
querystringyesFree-text topic query (e.g. "tropical tensor networks for spin glasses").
sort––Result ordering: `relevance` only (the default; `cited` / `recent` were removed — see `min_fwci` / `min_percentile` / `from_year`, #290).
to_yearinteger|null–Inclusive upper publication-year bound.
venuestring|null–Venue / journal name (resolved to an OpenAlex source id).

No output schema declared.

No examples provided.

doiget_paper_tex_source ~292

WHEN TO USE: Fetch the raw LaTeX source of an arXiv paper — more reliable than `doiget_paper_text` (ar5iv) for papers not yet processed by LaTeXML. INPUTS: ref (arXiv id, e.g. "arxiv:2401.12345"); optional max_chars (cap; omit for full source). OUTPUTS: { ok: true, arxiv_id, main_file, tex_source, char_count, truncated, retrieved_from } OR { ok:false, error }. COSTS: 1 arXiv source API request (gzip'd tar download); large papers can be sizeable — use max_chars to bound. SIDE EFFECTS: Emits an OA provenance row. NEVER writes the store; NEVER opens a PDF blob. LIMITS: arXiv only (a DOI → NOT_IMPLEMENTED; pass the arXiv id). PDF-only submissions → TEXT_UNAVAILABLE.

NameTypeReqDescription
max_charsinteger|null–Cap the returned LaTeX source to this many characters (truncation is flagged on `truncated`). Omit for the full source.
refstringyesarXiv id (e.g. "arxiv:2401.12345"), validated via `Ref::parse`. A bare DOI returns `NOT_IMPLEMENTED` (pass the arXiv id).

No output schema declared.

No examples provided.

doiget_paper_text ~322

WHEN TO USE: Read a paper's full text (arXiv only) without an external pdf-to-text tool — the 'read' step after discovery/fetch. INPUTS: ref (arXiv id, e.g. "arxiv:2401.12345"); optional max_chars (cap; omit for full text). OUTPUTS: { ok: true, arxiv_id, source: "ar5iv", title, sections: [{ heading, text }], char_count, truncated, retrieved_from } OR { ok:false, error }. COSTS: 1 ar5iv HTTP request (HTML), then parse; large papers can be sizeable — use max_chars to bound. SIDE EFFECTS: Emits an OA provenance row. NEVER opens the PDF blob; NEVER writes the store. LIMITS: arXiv only (a DOI → NOT_IMPLEMENTED; pass the arXiv id). A paper not converted by ar5iv → NOT_FOUND. Best-effort extraction (truncation flagged on `truncated`).

NameTypeReqDescription
max_charsinteger|null–Cap the returned text to this many characters (truncation is flagged on `truncated`). Omit for the full text.
refstringyesarXiv id (e.g. "arxiv:2401.12345"), validated via `Ref::parse`. A bare DOI returns `NOT_IMPLEMENTED` (pass the arXiv id; DOI→arXiv linking is #281 item 5).

No output schema declared.

No examples provided.

doiget_resolve_citation ~301

WHEN TO USE: Resolve a free-form bibliographic citation string (e.g. 'Onsager 1944') to ranked DOI candidates. INPUTS: query (bibliographic citation query string), limit (maximum number of candidates to return, default: 5). OUTPUTS: { ok: true, query, candidates: [ { doi, title, author, year, score, confidence, matched, source } ] } OR { ok: false, error }. COSTS: 1-2 s round-trip. SIDE EFFECTS: none. LIMITS: Returns candidates with similarity score >= 0.5. BRANCH ON confidence, NOT score: the score is token overlap against your query string and 0.5 is the FLOOR, so the worst candidate this tool can emit still looks like a positive number. confidence is exact (every query token matched), probable (four in five), or weak (cleared the floor and no more) - for a known-item lookup a weak candidate is a near-miss, not a match, so verify it with doiget_resolve_paper before citing. matched lists which of your tokens were found, which is how you see whether the author and the journal were among them.

NameTypeReqDescription
limitinteger–Maximum number of candidates to return (default: 5).
querystringyesBibliographic citation query string (e.g. "Onsager 1944").

No output schema declared.

No examples provided.

doiget_resolve_paper ~682

WHEN TO USE: User wants metadata for a DOI / arXiv id with no local persistence (audit log row only). INPUTS: ref (DOI or arXiv id), include_oa_location (optional bool). OUTPUTS: { ok: true, ref, source, resolver_profile, license?, oa_url, oa_status, metadata, schema_version } OR { ok:false, ref, error }. COSTS: 1-2 s metadata round-trip (roughly doubled when include_oa_location). SIDE EFFECTS: Appends one provenance row per consulted resolver. NEVER writes a metadata TOML to the store. NEVER fetches PDF. LIMITS: Subject to the same rate cap as metadata_only (5/sec). The OA URL is reported but never followed. Crossref alone cannot supply an oa_url, because its link[] entries are scoped to a licensed programme (Similarity Check / TDM / syndication) rather than being general-purpose. A null oa_url is therefore NOT evidence that the work is closed. oa_url is null on the default path whenever Crossref answered, which is nearly every DOI. It can be non-null WITHOUT the flag in one case: Crossref failed and Unpaywall answered instead, and then source is unpaywall rather than crossref - so source tells you which happened. With include_oa_location set, oa_status says which answer you got: closed means the lookup completed and found no OA location, null means the lookup did not complete. dry_run is not supported; use metadata_only with dry_run for a preview.

NameTypeReqDescription
include_oa_locationboolean–Consult Unpaywall for a real OA location, filling `oa_url`, `oa_status` and `license`. Costs one extra metadata round-trip. Defaults to `false`. On the default path `oa_url` is `null` whenever Cross…
refstringyesDOI or arXiv id. Validated via `Ref::parse`; failures surface as `INVALID_REF` per `docs/ERRORS.md`.

No output schema declared.

No examples provided.

doiget_search_local ~190

WHEN TO USE: Find stored entries whose title / authors / venue / publisher contain a query substring (case-insensitive). INPUTS: query (string), limit (optional integer, default 50, max 200). OUTPUTS: { ok: true, scope: "local", query, count, results: [{ safekey, title, year, fetched_at }] } OR { ok:false, error }. COSTS: O(N) over the local store; <100 ms for a few thousand entries. SIDE EFFECTS: none. LIMITS: Returns at most `limit` entries (capped at 200).

NameTypeReqDescription
limitinteger|null–Maximum number of results to return. `None` means default (50); values >200 are clamped to 200.
querystringyesCase-insensitive substring matched against title / authors / venue / publisher.

No output schema declared.

No examples provided.

doiget_tag ~264

WHEN TO USE: Add or remove tags / collections on a stored paper entry for local knowledge-base organisation (#294). INPUTS: ref (DOI or arXiv id); add (array of tags to add, optional); remove (array of tags to remove, optional); collection_add (array of collections to join, optional); collection_remove (array of collections to leave, optional). OUTPUTS: { ok: true, ref, tags, collections } OR { ok: false, error }. COSTS: 0 network requests; one store read + write. SIDE EFFECTS: Overwrites [doiget].tags / [doiget].collections in <store>/.metadata/<safekey>.toml. LIMITS: Entry must already exist in the store. Tags are case-sensitive; idempotent add/remove.

NameTypeReqDescription
addarray–Tags to add (idempotent, case-sensitive).
collection_addarray–Collections to join (idempotent, case-sensitive).
collection_removearray–Collections to leave.
refstringyesDOI or arXiv id. Validated via `Ref::parse`; failures surface as `INVALID_REF`.
removearray–Tags to remove.

No output schema declared.

No examples provided.

Install

How do I install the doiget MCP server?

doiget ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 199a7d8829003a49512ea2cbd59f7a384f6d4f3313a7282f0edd7001c93f4f8e; the commands to do that are on this page. If it does not match, do not open it.

mcpb · doiget-0.9.0.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

199a7d8829003a49512ea2cbd59f7a384f6d4f3313a7282f0edd7001c93f4f8e

macOS / Linux

echo "199a7d8829003a49512ea2cbd59f7a384f6d4f3313a7282f0edd7001c93f4f8e  doiget-0.9.0.mcpb" | shasum -a 256 -c

Windows (PowerShell)

(Get-FileHash -Algorithm SHA256 .\doiget-0.9.0.mcpb).Hash -eq "199a7d8829003a49512ea2cbd59f7a384f6d4f3313a7282f0edd7001c93f4f8e"

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

Common questions

What is the doiget MCP server?

doiget is an MCP server listed in the public MCP registry as io.github.QAtlasHub/doiget. OA-first paper fetcher: DOIs/arXiv IDs to local PDFs + metadata via Open Access APIs. This page covers its MCPB bundle (https://github.com/QAtlasHub/doiget/releases/download/v0.9.0/doiget-0.9.0.mcpb).

Is the doiget MCP server safe to use?

doiget scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the doiget MCP server expose?

doiget exposes 22 tools: doiget_annotate, doiget_batch_fetch, doiget_batch_from_bibliography, doiget_batch_resolve_citations, doiget_bibtex_export, and 17 more. Their descriptions and schemas cost roughly 7,158 tokens of context every time the server is loaded.

What licence is the doiget MCP server under?

doiget declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.