Bring Researcher Search
to VS Code Copilot
Learn how to connect ORCID (Researcher IDs) to VS Code Copilot and start using 14 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
Compatible with every major AI agent and IDE
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 VS Code Copilot?
GitHub Copilot Agent mode brings ORCID (Researcher IDs) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 14 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
ORCID (Researcher IDs) in VS Code Copilot
ORCID (Researcher IDs) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect ORCID (Researcher IDs) to VS Code Copilot 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 VS Code Copilot
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 VS Code Copilot 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 VS Code Copilot
Every tool call from VS Code Copilot 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.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.
Explore More MCP Servers
View all →
X (Twitter)
3 toolsAutomate social intelligence workflows via X (Twitter) — search recent tweets, retrieve user profiles, and analyze tweet engagement directly from any AI agent.

LearningSuite
10 toolsCreate and deliver corporate training programs with course authoring, quizzes, and progress tracking for distributed teams.

Shodan
10 toolsSearch for internet-connected devices, analyze open ports, discover vulnerabilities and explore the IoT landscape.

U.S. EIA Energy Data
10 toolsEquip your AI agent to access official U.S. energy statistics, track electricity generation, and monitor fuel prices via the EIA API.
