io.github.cyanheads/crossref-mcp-server
Resolve DOIs, search ~155M scholarly works, and fetch references via the Crossref REST API.
The current version, v0.4.2, was published to the official MCP registry on 2026-10-08. It is distributed as @cyanheads/crossref-mcp-server on npm and as a hosted remote over streamable-http, filed under Search by this index, and declares 9 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using io.github.cyanheads/crossref-mcp-server in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“Normal scholarly search capability”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Screen its description →
That verdict was true at screening time (snapshot 2026-10-12).
Contracts can change after screening, with no version bump. The gate pins io.github.cyanheads/crossref-mcp-server’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
4 changes with a version change.
Server-scoped, not a tool: this is text the server supplies for clients to inject into an agent’s context on connect (instructions or prompt metadata). It sits outside every tool contract hash, so this observation is its only drift signal.
Part of a publisher-wide change to server context of the same kind on 2026-09-25, seen on 11 servers from this publisher.
Part of a publisher-wide change of the same kind on 2026-09-25, seen on 19 servers from this publisher.
Observed by mcpindex’s crawler between daily registry snapshots - a contract diff, not a safety verdict, and not an in-path prevention (that is the gate). A “safety-relevant diff” touches a safety-relevant field; it is not a confirmed vulnerability. Shown at the server level; individual tools are not named. Absence is not a clean bill of health: only public-registry servers are crawled.
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for io.github.cyanheads/crossref-mcp-server](https://mcpindex.ai/server/io-github-cyanheads-crossref-mcp-server) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-cyanheads-crossref-mcp-server">Independent trust record for io.github.cyanheads/crossref-mcp-server</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-cyanheads-crossref-mcp-server)<a href="https://mcpindex.ai/server/io-github-cyanheads-crossref-mcp-server"><img src="https://mcpindex.ai/api/v1/badge/io-github-cyanheads-crossref-mcp-server" alt="mcpindex verdict" height="20" /></a>CROSSREF_MAILTOEmail for polite-pool User-Agent header — optional. Without: anonymous pool with stricter rate limits.
CROSSREF_BASE_URLOverride the Crossref API base URL. Defaults to https://api.crossref.org.
CROSSREF_TIMEOUT_MSPer-request timeout in milliseconds.
MCP_LOG_LEVELSets the minimum log level for output (e.g., 'debug', 'info', 'warn').
MCP_TRANSPORT_TYPESelects the HTTP transport.
CROSSREF_MAILTOEmail for polite-pool User-Agent header — optional. Without: anonymous pool with stricter rate limits.
CROSSREF_BASE_URLOverride the Crossref API base URL. Defaults to https://api.crossref.org.
CROSSREF_TIMEOUT_MSPer-request timeout in milliseconds.
MCP_HTTP_HOSTThe hostname for the HTTP server.
MCP_HTTP_PORTThe port to run the HTTP server on.
MCP_HTTP_ENDPOINT_PATHThe endpoint path for the MCP server.
MCP_AUTH_MODEAuthentication mode to use: 'none', 'jwt', or 'oauth'.
MCP_LOG_LEVELSets the minimum log level for output (e.g., 'debug', 'info', 'warn').
Search and update Records and Lists, import and export CSVs, and run enrichment in Connie.
Search and read Edgepedia, a free and growing encyclopedia with citations. No key.
Fleet discovery for the cyanheads MCP ecosystem — semantic search + install snippets.