4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
Stanford CrossRef MCP Server

Bring Crossref
to Claude Desktop

Learn how to connect Stanford CrossRef to Claude Desktop and start using 16 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get Citations CountGet Funder WorksGet JournalGet Journal WorksGet PublisherGet Reference ListResolve DoiSearch By AffiliationSearch By OrcidSearch FundersSearch JournalsSearch PreprintsSearch PublishersSearch Recent WorksSearch WorksValidate Doi

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Stanford CrossRef

What is the Stanford CrossRef MCP Server?

Connect to the CrossRef API — the authoritative source for DOI metadata and scholarly publishing infrastructure.

What you can do

  • DOI Resolution — Resolve any DOI to complete bibliographic metadata
  • Works Search — Search 150M+ DOI-registered works with advanced filters
  • Journal Registry — Query journals by title or ISSN with coverage metrics
  • Publisher Profiles — Explore academic publishers (Elsevier, Springer, Wiley)
  • Funder Registry — Search funding organizations (NIH, NSF, ERC, Wellcome Trust)
  • ORCID Lookup — Find works by researcher ORCID identifier
  • Affiliation Search — Search works by institutional affiliation
  • Citation Counts — Get citation and reference counts for any DOI
  • Reference Lists — Extract complete bibliographies from published works
  • Preprint Search — Find preprints registered with CrossRef
  • DOI Validation — Verify whether a DOI is valid and registered
  • Recent Works — Monitor the latest DOI registrations

Who is this for?

  • Researchers — DOI resolution and bibliography management
  • Librarians — journal evaluation and publisher analysis
  • Research Administrators — funder tracking and institutional output
  • Bibliometricians — large-scale publication analytics

Built-in capabilities (16)

get_citations_count

The "is-referenced-by-count" is the number of times other works cite this DOI. The "references-count" is how many references this work cites. Quick way to assess a paper's impact. Get citation count for a DOI

get_funder_works

Use the funder ID from search_funders (e.g. "100000002" for NIH). Essential for understanding research funding landscapes and tracking funded output. Get works funded by a specific funding organization

get_journal

Returns title, publisher, subjects, total DOI count, current and backfile counts, metadata coverage percentages, and quality flags. Get journal details by ISSN

get_journal_works

Can be filtered with an optional text query. Useful for browsing a journal's publication history or searching within a specific journal. Get articles published in a specific journal

get_publisher

Returns name, DOI prefix, total/current/backfile DOI counts, metadata coverage scores, and quality flags. Get publisher details with output metrics

get_reference_list

Returns all cited references with their DOIs (when available), authors, titles, journals, and years. Essential for bibliography analysis, finding source material, and understanding a paper's intellectual foundations. Get full reference list (bibliography) for a DOI

resolve_doi

Returns title, authors, journal, publisher, publication date, volume, issue, pages, citation count, reference count, subject areas, and license information. The definitive tool for getting structured metadata from any DOI. Resolve a DOI to full bibliographic metadata

search_by_affiliation

Use institution names like "Stanford University", "MIT", "Harvard Medical School". Can be combined with a topic query. Search works by institutional affiliation

search_by_orcid

ORCID is the universal researcher identifier. Format: "0000-0002-1825-0097". Essential for finding the complete publication record of a researcher across all journals and publishers. Find works by ORCID author identifier

search_funders

Examples: "National Institutes of Health", "National Science Foundation", "European Research Council", "Wellcome Trust". Search funding organizations worldwide

search_journals

Returns journal titles, ISSNs, publishers, subject areas, total DOI counts, and metadata coverage scores. Use this to find journal identifiers and evaluate journal metrics. Search academic journals by title or ISSN

search_preprints

This covers preprints from bioRxiv, medRxiv, SSRN, ChemRxiv, and other preprint servers that register DOIs with CrossRef. Search registered preprints across all servers

search_publishers

Returns publisher names, DOI prefixes, and total DOI counts. Search academic publishers

search_recent_works

Default is last 7 days. Use this to monitor the latest publications across all journals and publishers. Find the most recently registered DOIs

search_works

Supports full-text query, filters, sorting, and pagination. Filter syntax: "from-pub-date:2024-01-01", "type:journal-article", "has-orcid:true", "has-references:true", "is-update:false". Sort options: "relevance", "published", "indexed", "is-referenced-by-count". Search 150M+ DOI-registered academic works

validate_doi

Returns whether the DOI exists in CrossRef, along with basic metadata (title, type, publisher) if valid. Useful for quality-checking reference lists and citation data. Check if a DOI is valid and registered

Why Claude Desktop?

Claude Desktop is the definitive way to connect Stanford CrossRef to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 16 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

  • Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

  • Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

  • Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

  • Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

Stanford CrossRef in Claude Desktop

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Stanford CrossRef and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Stanford CrossRef to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Stanford CrossRef in Claude Desktop

The Stanford CrossRef MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 16 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Stanford CrossRef
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Stanford CrossRef for Claude Desktop

Every tool call from Claude Desktop to the Stanford CrossRef MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Do I need an API key?

No. The CrossRef API is fully public. Including a mailto address gets you into the "polite pool" with higher rate limits, which this server handles automatically.

02

What is a DOI?

A Digital Object Identifier (DOI) is a unique, permanent identifier assigned to academic publications, datasets, and other research outputs. Format: "10.1038/s41586-021-03819-2". CrossRef is the largest DOI registration agency with over 150 million registered DOIs.

03

Can I search by ORCID?

Yes. You can look up all works associated with a researcher's ORCID identifier. ORCID provides a unique, persistent identifier for researchers — similar to what DOI does for publications.

04

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

05

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

06

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

07

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

08

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

09

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

10

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

11

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Explore More MCP Servers

View all →