orcid-mcp-server

Get ORCID Research Resources

orcid_get_research_resources

Read-onlyIdempotent

List research resources associated with an ORCID researcher — compute allocations, equipment access, lab facilities, data resources, and clinical study registrations. This is a newer ORCID section; most researchers have no entries. Returns the resource title, hosting organization, external identifiers (often a URI to the allocation portal), access period, and the source that added each entry. Most entries are deposited by resource-allocation systems (e.g. ACCESS, XSEDE) rather than researchers themselves.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`orcid_id`	Yes	ORCID iD — bare (0000-0001-2345-6789) or as an orcid.org URI (https://orcid.org/0000-0001-2345-6789). The check digit may be X or x.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Note when no research resources are found — this section is sparsely populated across ORCID profiles.
`orcidId`	No	Normalized ORCID iD (bare format).
`orcidUri`	No	Full ORCID URI.
`resources`	No	Research resources associated with this ORCID iD.
`resourceCount`	No	Total number of research resources returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 3, 2026

changedInput schema / properties / orcid_id / description

Previous value: -"ORCID iD — bare format (0000-0001-2345-6789) or full URI (https://orcid.org/0000-0001-2345-6789)."New value: +"ORCID iD — bare (0000-0001-2345-6789) or as an orcid.org URI (https://orcid.org/0000-0001-2345-6789). The check digit may be X or x."

changedInput schema / properties / orcid_id / pattern

Previous value: -"^(https?:\\/\\/orcid\\.org\\/)?\\d{4}-\\d{4}-\\d{4}-\\d{3}[\\dX]$"New value: +"^(?:(?:https?:\\/\\/)?(?:www\\.)?orcid\\.org\\/)?\\d{4}-\\d{4}-\\d{4}-\\d{3}[\\dXx]\\/?$"

addedOutput schema / properties / resources / items / properties / sources

Added value: +{
+  "description": "The party that added this resource to the ORCID record — usually the allocation system that granted it. Empty when ORCID records no source.",
+  "items": {
+    "additionalProperties": false,
+    "description": "A party that asserted this item on the ORCID record.",
+    "properties": {
+      "assertionOriginName": {
+        "description": "Party the source added the item on behalf of, when ORCID records one — usually the researcher, for an item added through a search-and-link tool.",
+        "type": "string"
+      },
+      "name": {
+        "description": "Name of the person or member organization system that added the item (e.g. a university research information system, Crossref, Scopus - Elsevier). Absent when ORCID records no name.",
+        "type": "string"
+      },
+      "selfAsserted": {
+        "description": "True when the asserting party (the assertion origin when recorded, otherwise the source) is the requested ORCID iD; false when a member organization or another ORCID user asserted the item.",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "selfAsserted"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / resources / items / required

Previous value: -[
-  "putCode",
-  "externalIds"
-]New value: +[
+  "putCode",
+  "externalIds",
+  "sources"
+]

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "orcidId",
+      "orcidUri",
+      "resourceCount",
+      "resources"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `profile_not_found`: The ORCID iD does not correspond to a registered researcher. Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "profile_not_found"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "orcidId",
-  "orcidUri",
-  "resourceCount",
-  "resources"
-]

AddedMay 31, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: expected sparsity of entries and the fact that most records are deposited by allocation systems (ACCESS, XSEDE) rather than the researchers themselves, which shapes how results should be interpreted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all front-loaded with the core action first and interpretive context after. Every sentence earns its place: what it lists, how sparse it is, and who deposits the data.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't enumerate return values, yet it still summarizes the key fields and their provenance. Combined with the emptiness caveat and safety annotations, an agent has everything needed to call and interpret this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single orcid_id parameter is fully documented in the schema, including accepted bare and URI formats and the X check digit. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (List) and resource (research resources associated with an ORCID researcher), then enumerates the concrete subtypes (compute allocations, equipment access, lab facilities, data resources, clinical study registrations). This clearly separates it from siblings like orcid_get_affiliations, orcid_get_funding, and orcid_get_works.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives useful selection context: 'This is a newer ORCID section; most researchers have no entries,' which tells the agent not to expect results and implicitly when this call is worth making. However, it never explicitly routes between this and the other orcid_get_* siblings or states when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All orcid-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.