Skip to content

crossref-mcp-server

io.github.cyanheads/crossref-mcp-servercyanheadsstreamable-httpv0.5.4Scanned

Resolve DOIs, search ~188M scholarly works, and fetch references via the Crossref REST API.

7 tools: 7 only read.

Tools: 0 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the crossref-mcp-server can do

The crossref-mcp-server is published by the GitHub account cyanheads. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

4 tools bring in text other people can write (crossref_get_work, crossref_search_works, crossref_search_journals and 1 more).

The fixed checks matched 3 findings (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 5 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 0.5.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Only reads 7Show 7 read-only tools
  • crossref_get_memberResolves a Crossref member ID to its publisher/organization record: primary name, alternate imprint names, owned DOI prefixes, registered DOI counts, a per-work-type breakdown, and…No findings

    Why it is in this group

    • The name "crossref_get_member" says "get": a word for reading.
    Description, as the server wrote it
    Resolves a Crossref member ID to its publisher/organization record: primary name, alternate imprint names, owned DOI prefixes, registered DOI counts, a per-work-type breakdown, and per-category metadata deposit coverage. Members are the organizations that register DOIs with Crossref, so this answers "what does this publisher publish, and how completely do they deposit metadata?" The member that holds a DOI now is the memberId crossref_get_work or crossref_search_works returns for it — pass that ID here. crossref_get_prefix returns the member a DOI prefix record names, the prefix's registrant, which for a transferred title is a former publisher rather than the DOI's current one.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • crossref_get_prefixResolves a DOI prefix — the registrant portion of a DOI, e.g.No findings

    Why it is in this group

    • The name "crossref_get_prefix" says "get": a word for reading.
    Description, as the server wrote it
    Resolves a DOI prefix — the registrant portion of a DOI, e.g. "10.1038" — to the Crossref member its prefix record names: the publisher name and numeric member ID. That member is the prefix's registrant, so for a title transferred to another publisher it is not the member holding the DOI now — crossref_get_work's memberId names that one. The Crossref prefix record carries only these three facts (no counts, coverage, or flags); the returned memberId chains directly into crossref_get_member for the full publisher record.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • crossref_get_referencesReturns the outgoing reference list for a DOI — the works cited by this paper.No findings

    Why it is in this group

    • The name "crossref_get_references" says "get": a word for reading.
    Description, as the server wrote it
    Returns the outgoing reference list for a DOI — the works cited by this paper. Each reference includes the deposited citation string and, where Crossref has resolved it, a DOI you can look up with crossref_get_work. Results are paged: referenceCount is the full deposited total, and when more remain the response carries a nextOffset to pass back as offset. Reference list coverage varies by publisher; many older works and non-participating publishers have no indexed references. Incoming citations — the works that cite this paper — are not available through Crossref; use OpenAlex for that.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • crossref_get_workResolves a DOI to its full Crossref metadata record: title, authors, editors, affiliations, abstract (when deposited), journal or container with the volume, issue, pages, and artic…Reads text others write1 finding

    Why it is in this group

    • The name "crossref_get_work" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "resolve" and "issue": it reads issues, which other people can write.

    Findings

    • Info

      The description is 3,483 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...themselves are not available through Crossref — use OpenAlex for citation graphs."

      What this check looks for
    Description, as the server wrote it
    Resolves a DOI to its full Crossref metadata record: title, authors, editors, affiliations, abstract (when deposited), journal or container with the volume, issue, pages, and article number that locate the work in it, ISSNs and ISBNs, publication date, type, license, full-text links, and funder acknowledgements. Where the record deposits them it also carries the conference event of a proceedings paper (event), the approval date that dissertations and most standards deposit in place of a publication date (approved, never read into published), the institutions a record names (the awarding institution of a thesis, the server of a preprint, the laboratories behind a report) and the degree of a thesis, and the subtype and group title of posted content such as a preprint. The author list is paged: authorCount is the full deposited total, offset and limit select the page (25 authors by default), and when authors remain the response carries a nextOffset to pass back as offset — large-collaboration papers deposit thousands. A grant, which deposits no title or abstract, carries its award number (award), award start, and projects: titles, descriptions, lead and co-lead investigators, investigators, amounts, dates, and funding, each funder with its Funder Registry DOI or ROR. Its investigators are paged by offset and limit the way authors are, across its projects in deposited order, with investigatorCount the full total; lead and co-lead investigators come back whole. A peer review carries review — its stage, type, running number, revision round, recommendation, competing-interest statement, and language, where deposited. Post-publication updates are relayed as Crossref records them: updatedBy names each correction, retraction, expression of concern, or new version issued against this work, with its notice DOI and whether the publisher or Retraction Watch recorded it, and updateTo names the works this record is itself a notice for. An absent updatedBy does not mean the work was never updated — coverage depends on those deposits. relations lists related identifiers, such as a preprint and its published version, grouped by relation type; only the Crossref-registered DOIs among them resolve through crossref_get_work. The record of a preprint can leave out its published version, so on a posted-content record of subtype preprint a second request reads publishedVersions: the works whose own records name it in has-preprint, each with its DOI, type, and title. Every other record takes one request. clinicalTrialNumbers lists the trial registrations the work names, each with its registry where deposited, and assertions the Crossmark entries its publisher attaches — received, revised, and accepted dates, ethics and competing-interest statements, peer-review details — both returned whole in deposited order; an absent clinicalTrialNumbers does not mean the work reports no trial. memberId is the Crossref member that holds the DOI now — pass it to crossref_get_member for the publisher record and its deposit coverage; the prefix of the DOI names the member that registered the prefix, which for a transferred title is a former publisher. Outgoing references are reported as a count in referencesCount; the reference entries themselves come from crossref_get_references. The isReferencedByCount field reports the total incoming citation count from Crossref; the citing works themselves are not available through Crossref — use OpenAlex for citation graphs.

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
  • crossref_search_fundersFinds funders registered in the Crossref Funder Registry by name or funder DOI.Reads text others write1 finding

    Why it is in this group

    • The name "crossref_search_funders" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,206 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...d automatically — re-run with funder_doi set to that ID to get the current entry."

      What this check looks for
    Description, as the server wrote it
    Finds funders registered in the Crossref Funder Registry by name or funder DOI. Provide funder_doi for an exact single-funder lookup — the full DOI ("10.13039/100000001"), the bare registry ID ("100000001"), or either behind a doi: or https://doi.org/ prefix — or query for name-based search. Name-query results page with offset — the nextOffset enrichment carries the value for the following page, up to offset + rows = 100000. Set include_works to true to also return a page of the most recent works funded by the matched funder; that list pages two ways, in two orders. works_offset is the simple one: newest published first, capped ten times lower at works_offset + rows = 10000. works_cursor has no ceiling and reaches the whole funded-works list, newest registered first — ordered by the date each DOI was registered with Crossref, since Crossref does not walk a publication-date sort by cursor: pass works_cursor="*" on the first call, then chain the nextWorksCursor token from each response. The two cannot be combined, and a cursor walk always starts at the most recently registered work — it cannot resume from an offset. This list also counts works funded by the funder's registry descendants, which a crossref_search_works filter on {"funder": "10.13039/<id>"} does not; a funder_doi lookup returns those descendants' registry IDs as descendants, and the funder's own ID OR'd with each of them in the funder filter ({"funder": "<id>,funder:<descendant>,…"}) counts the same scope with date, type, or other filters. Both it and that filter count the grant DOIs a funder registers as funded works. Returns funder name, registry ID, country, and alternate names, plus, on a funder_doi lookup, the Funder Registry's own work count for the ID and the same with its descendants (descendantWorksCount), both less grant records. The Funder Registry supersedes entries, and a deprecated one answers to the same names as its successor while carrying only a fraction of its works: such a record carries replacedBy with the superseding registry ID and the response carries a notice naming it. The replacement is never followed automatically — re-run with funder_doi set to that ID to get the current entry.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • crossref_search_journalsFinds Crossref journal records by ISSN or title query.Reads text others writeNo findings

    Why it is in this group

    • The name "crossref_search_journals" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Finds Crossref journal records by ISSN or title query. Provide issn for an exact single-journal lookup, or query for title-based search returning up to rows results. Title-query results page with offset — the nextOffset enrichment carries the value for the following page, up to offset + rows = 100000. Set include_works to true to also return a page of the matched journal's most recent works — the works deposited under any of its ISSNs, whichever one you passed; that list pages two ways, in two orders. works_offset is the simple one: newest published first, capped ten times lower at works_offset + rows = 10000. works_cursor has no ceiling and reaches the whole works list, newest registered first — ordered by the date each DOI was registered with Crossref, since Crossref does not walk a publication-date sort by cursor: pass works_cursor="*" on the first call, then chain the nextWorksCursor token from each response. The two cannot be combined, and a cursor walk always starts at the most recently registered work — it cannot resume from an offset. Returns journal metadata: title, publisher, ISSNs with their print or electronic form, subject areas, DOI counts (total, current, backfile), and per-category metadata deposit coverage — how completely the journal deposits abstracts, references, ORCIDs, funders, licenses, and similar metadata. An issn lookup also returns DOI counts by issued year.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • crossref_search_worksSearches the Crossref works index (~188M records) by free text and/or structured filters.Reads text others write1 finding

    Why it is in this group

    • The name "crossref_search_works" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,043 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ries a notice saying the list is exhausted. Cursor and offset cannot be combined."

      What this check looks for
    Description, as the server wrote it
    Searches the Crossref works index (~188M records) by free text and/or structured filters. The generic query matches loosely across all fields; scope precisely with the field-specific parameters queryTitle, queryAuthor, and queryContainerTitle, or resolve a known citation to its DOI with queryBibliographic — all combine with each other and with query. Use the filter parameter for structured filtering (object with hyphen-separated Crossref keys). Sort options: relevance, score, is-referenced-by-count, published, deposited, indexed, created. Each work returns at most authorLimit authors (25 by default) with authorCount reporting the full deposited total, since a single page of large-collaboration papers can carry tens of thousands of author entries; crossref_get_work pages the whole author list for any DOI whose list was cut. Funding acknowledgements with their award numbers, license terms, and registered full-text links come back only when fields names funder, license, or link, in the entry shapes crossref_get_work uses; each work then carries at most 25 funders, with funderCount the full deposited total. Post-publication updates ride each work as Crossref records them: updatedBy names each correction, retraction, expression of concern, or new version issued against it, and updateTo the works it is itself a notice for — an absent updatedBy does not mean the work was never updated. Set facets to count the matching works per value of a field — per publication year, publisher, type, funder, affiliation, ORCID, and more — over the whole match set in the same call; rows: 0 returns the counts alone. Offset-based paging is capped at ~10K results; use cursor="*" to start cursor-based deep paging, then pass the nextCursor value from each response to continue. A walk with a query term and no sort runs by relevance, one with filters only in Crossref registration order. The walk ends on the page where nextCursor is absent — that page also carries a notice saying the list is exhausted. Cursor and offset cannot be combined.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

3 info
  • The description is 3,483 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...themselves are not available through Crossref — use OpenAlex for citation graphs."

    What this check looks for
  • The description is 2,043 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ries a notice saying the list is exhausted. Cursor and offset cannot be combined."

    What this check looks for
  • The description is 2,206 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...d automatically — re-run with funder_doi set to that ID to get the current entry."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 changed.~3 changedView diff
  2. Tools5 changed.~5 changedView diff
  3. Tools3 changed.~3 changedView diff
  4. Tools7 changed.~7 changedView diff
  5. Tools5 changed.~5 changedView diff

Install

Pinned to version 0.5.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http crossref https://crossref.caseyjhand.com/mcp
claude mcp add --transport http crossref https://crossref.caseyjhand.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__crossref__crossref_get_work",
      "mcp__crossref__crossref_get_references",
      "mcp__crossref__crossref_search_works",
      "mcp__crossref__crossref_search_journals",
      "mcp__crossref__crossref_search_funders",
      "mcp__crossref__crossref_get_member",
      "mcp__crossref__crossref_get_prefix"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as crossref. Review it before you use it.

Capability tags behind 4 rules
  • mcp__crossref__crossref_get_work untrusted-input
  • mcp__crossref__crossref_search_works untrusted-input
  • mcp__crossref__crossref_search_journals untrusted-input
  • mcp__crossref__crossref_search_funders untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.cyanheads/crossref-mcp-server/verify?hash=b15574faa1d8cb181f3a6e9d5fe15e71bcc94d85313d71173b393f99e7cc9a70" | jq -e '.changed == false'

Pinned hash b15574faa1d8, from Nov 18, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.cyanheads/crossref-mcp-server/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.cyanheads/crossref-mcp-server
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.cyanheads/crossref-mcp-server.svg)](https://radar.anlyon.com/servers/io.github.cyanheads/crossref-mcp-server)

Source: MCP Registry · repository. Synced Nov 18, 2026, 07:17 UTC.

crossref-mcp-server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the crossref-mcp-server safe?

No scan can promise that. What its definitions show: 7 tools, all of which only read, and 3 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the crossref-mcp-server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the crossref-mcp-server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the crossref-mcp-server have?

7 tools: 7 read. crossref_get_work, crossref_get_references, crossref_search_works, crossref_search_journals, crossref_search_funders, crossref_get_member and crossref_get_prefix.

Does the crossref-mcp-server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the crossref-mcp-server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the crossref-mcp-server changed its tools?

Yes, 5 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.