Bring Researcher Search
to CrewAI
Learn how to connect ORCID (Researcher IDs) to CrewAI and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the ORCID (Researcher IDs) MCP Server?
Connect the ORCID registry to your AI agent to seamlessly navigate the global ecosystem of researcher identifiers and scholarly records.
What you can do
- Registry Search — Perform standard or expanded Solr searches to find researchers by name, institution, or keywords using
searchandexpanded_search. - Profile Summaries — Retrieve complete researcher records, including biographical details and activity summaries, via
get_recordandget_activities. - Works & Funding — Inspect specific research outputs and funding history using
get_worksor drill down into specific items withget_section_item. - Trust Markers — Access validated trust markers for records using
get_summary(requires Member API). - Record Management — Add or update items in an ORCID record directly through the agent using
add_itemandupdate_item(requires Member API).
How it works
- Subscribe to this server
- Enter your ORCID Access Token (Public or Member API)
- Start querying researcher data from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Academic Researchers — quickly find collaborators and verify publication records without manual searching
- Librarians & Data Managers — automate the retrieval of institutional research outputs and metadata
- Grant Officers — verify researcher credentials and funding history directly within your workflow
Built-in capabilities (14)
Requires Member API access token with /activities/update or /person/update scope. Add a new item to an ORCID record (Member API only)
Search the ORCID registry and return CSV data
Requires Member API access token. Delete an item from an ORCID record (Member API only)
Search the ORCID registry (Expanded)
Get summary of all activities for an ORCID record
Get biographical section of an ORCID record
Get full summary of an ORCID record
Get full details for a specific item in an ORCID record
Requires Member API access token. Get validated trust markers (Member API only)
Get summary of research works for an ORCID record
Requires /webhook scope. Register a webhook for an ORCID record (Premium Member API only)
Search the ORCID registry (Standard)
Unregister a webhook for an ORCID record (Premium Member API only)
Requires Member API access token. Update an existing item in an ORCID record (Member API only)
Why CrewAI?
When paired with CrewAI, ORCID (Researcher IDs) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ORCID (Researcher IDs) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
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
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
ORCID (Researcher IDs) in CrewAI
ORCID (Researcher IDs) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ORCID (Researcher IDs) to CrewAI 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ORCID (Researcher IDs) in CrewAI
The ORCID (Researcher IDs) 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 14 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI 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.
* 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
How Vinkius secures
ORCID (Researcher IDs) for CrewAI
Every tool call from CrewAI to the ORCID (Researcher IDs) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for researchers by their institution or specific keywords?
Yes! Use the expanded_search tool with a Solr query like affiliation-name:"University of Oxford" to find researchers associated with specific organizations along with their profile details.
How do I retrieve the full list of publications for a specific ORCID iD?
You can use the get_works tool by providing the researcher's ORCID iD. This will return a summary of all research works associated with that record.
Is it possible to add new research items to an ORCID profile using this server?
Yes, if you have a Member API access token with the appropriate scopes, you can use the add_item tool to add works, funding, or other activities to a record.
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.
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.
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.
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.
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.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
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.
Explore More MCP Servers
View all →
Image Router
11 toolsRoute image generation requests to the best AI model automatically based on prompt type, style, and quality requirements.
Donorbox
10 toolsEquip your AI agent to manage donations, track recurring plans, and monitor fundraising campaigns via the Donorbox API.
Mnemonic
12 toolsDeep NFT analytics and Web3 intelligence via Mnemonic — track collections, portfolios, and transfers directly from your AI agent.
Boathouse Connect
10 toolsManage marina operations with boat slip reservations, customer records, and facility maintenance in one connected system.