4,000+ servers built on vurb.ts
Vinkius

Stanford CrossRef MCP Server for CrewAIGive CrewAI instant access to 16 tools to Get Citations Count, Get Funder Works, Get Journal, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Stanford CrossRef through Vinkius, pass the Edge URL in the `mcps` parameter and every Stanford CrossRef tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Stanford CrossRef MCP Server for CrewAI is a standout in the Education category — giving your AI agent 16 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Stanford CrossRef Specialist",
    goal="Help users interact with Stanford CrossRef effectively",
    backstory=(
        "You are an expert at leveraging Stanford CrossRef tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Stanford CrossRef "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 16 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
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

About Stanford CrossRef MCP Server

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

When paired with CrewAI, Stanford CrossRef becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Stanford CrossRef tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

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

The Stanford CrossRef MCP Server exposes 16 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 16 Stanford CrossRef tools available for CrewAI

When CrewAI connects to Stanford CrossRef through Vinkius, your AI agent gets direct access to every tool listed below — spanning crossref, doi, metadata, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get citations count on Stanford CrossRef

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

Get funder works on Stanford CrossRef

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

Get journal on Stanford CrossRef

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

get

Get journal works on Stanford CrossRef

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

Get publisher on Stanford CrossRef

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

get

Get reference list on Stanford CrossRef

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

Resolve doi on Stanford CrossRef

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

Search by affiliation on Stanford CrossRef

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

search

Search by orcid on Stanford CrossRef

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

Search funders on Stanford CrossRef

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

search

Search journals on Stanford CrossRef

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

Search preprints on Stanford CrossRef

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

search

Search publishers on Stanford CrossRef

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

search

Search recent works on Stanford CrossRef

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

search

Search works on Stanford CrossRef

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

Validate doi on Stanford CrossRef

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

Connect Stanford CrossRef to CrewAI via MCP

Follow these steps to wire Stanford CrossRef into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 16 tools from Stanford CrossRef

Why Use CrewAI with the Stanford CrossRef MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Stanford CrossRef through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Stanford CrossRef + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Stanford CrossRef MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Stanford CrossRef for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Stanford CrossRef, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Stanford CrossRef tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Stanford CrossRef against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Stanford CrossRef in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Stanford CrossRef immediately.

01

"Resolve DOI 10.1038/s41586-021-03819-2"

02

"Find works funded by the National Institutes of Health on gene therapy"

03

"Look up all publications by ORCID 0000-0002-8350-519X"

Troubleshooting Stanford CrossRef MCP Server with CrewAI

Common issues when connecting Stanford CrossRef to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Stanford CrossRef + CrewAI FAQ

Common questions about integrating Stanford CrossRef MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →