4,000+ servers built on vurb.ts
Vinkius
Claude DesktopIDE
ORCID (Researcher IDs) MCP Server

Bring Researcher Search
to Claude Desktop

Learn how to connect ORCID (Researcher IDs) to Claude Desktop and start using 14 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
Add ItemCsv SearchDelete ItemExpanded SearchGet ActivitiesGet PersonGet RecordGet Section ItemGet SummaryGet WorksRegister WebhookSearchUnregister WebhookUpdate Item

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
ORCID (Researcher IDs)

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

  1. Subscribe to this server
  2. Enter your ORCID Access Token (Public or Member API)
  3. 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

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 Claude Desktop?

Claude Desktop is the definitive way to connect ORCID (Researcher IDs) to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 14 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

ORCID (Researcher IDs) in Claude Desktop

AI AgentVinkius
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 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 ORCID (Researcher IDs) in Claude Desktop

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

ORCID (Researcher IDs)
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 Claude Desktop

Every tool call from Claude Desktop 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

01

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.

02

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.

03

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.

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 →