CursorIDE

ORCID (Researcher IDs) MCP Server

Bring Researcher Search
to Cursor

Name: ORCID (Researcher IDs) MCP Server
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

Learn how to connect ORCID (Researcher IDs) to Cursor 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 Subscribers

Add ItemCsv SearchDelete ItemExpanded SearchGet ActivitiesGet PersonGet RecordGet Section ItemGet SummaryGet WorksRegister WebhookSearchUnregister WebhookUpdate Item

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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 search and expanded_search.
Profile Summaries — Retrieve complete researcher records, including biographical details and activity summaries, via get_record and get_activities.
Works & Funding — Inspect specific research outputs and funding history using get_works or drill down into specific items with get_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_item and update_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)

add_item

Requires Member API access token with /activities/update or /person/update scope. Add a new item to an ORCID record (Member API only)

csv_search

Search the ORCID registry and return CSV data

delete_item

Requires Member API access token. Delete an item from an ORCID record (Member API only)

expanded_search

Search the ORCID registry (Expanded)

get_activities

Get summary of all activities for an ORCID record

get_person

Get biographical section of an ORCID record

get_record

Get full summary of an ORCID record

get_section_item

Get full details for a specific item in an ORCID record

get_summary

Requires Member API access token. Get validated trust markers (Member API only)

get_works

Get summary of research works for an ORCID record

register_webhook

Requires /webhook scope. Register a webhook for an ORCID record (Premium Member API only)

Search the ORCID registry (Standard)

unregister_webhook

Unregister a webhook for an ORCID record (Premium Member API only)

update_item

Requires Member API access token. Update an existing item in an ORCID record (Member API only)

Why Cursor?

Cursor's Agent mode turns ORCID (Researcher IDs) into an in-editor superpower. Ask Cursor to generate code using live data from ORCID (Researcher IDs) and it fetches, processes, and writes. all in a single agentic loop. 14 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

—
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
—
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
—
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
—
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

See it in action

ORCID (Researcher IDs) in Cursor

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

ORCID (Researcher IDs) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect ORCID (Researcher IDs) to Cursor 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 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

Unlock for AI Agents View step-by-step setup guide for Cursor →

Enterprise Security

Why teams choose Vinkius for ORCID (Researcher IDs) in Cursor

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 Cursor 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.

Unlock for AI Agents View full ORCID (Researcher IDs) details →

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
ORCID (Researcher IDs) for Cursor

Every tool call from Cursor to the ORCID (Researcher IDs) 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

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.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Explore More MCP Servers

View all →

Freshworks

9 tools

Manage unified CRM and support via Freshworks — track sales deals and accounts, handle helpdesk tickets, and manage contacts directly from any AI agent.