orcid-mcp-server

Get ORCID Researcher Funding

orcid_get_funding

Read-onlyIdempotent

Fetch funding records for an ORCID researcher: grants, contracts, awards, and salary awards. Returns funder names, funder organization identifiers, grant numbers, funding periods, and sources. Funding items come from the researcher or from member organizations such as funders, institutions, and search-and-link tools; sources names who added each. Most researchers have no funding entries even when they hold grants, so absence of funding records does not imply absence of funding. When records exist they are high-value for grant tracking and funder analysis.

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 funding is found — absence of records does not mean absence of funding.
`funding`	No	Funding items associated with this ORCID iD, one per ORCID funding group.
`orcidId`	No	Normalized ORCID iD (bare format).
`orcidUri`	No	Full ORCID URI.
`fundingCount`	No	Number of funding items returned, one per ORCID funding group — versions of one grant added by different sources or deposited twice count once.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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]\\/?$"

changedOutput schema / properties / funding / description

Previous value: -"Funding records associated with this ORCID iD."New value: +"Funding items associated with this ORCID iD, one per ORCID funding group."

changedOutput schema / properties / funding / items / description

Previous value: -"Funding record."New value: +"Funding item: one ORCID funding group, built from its preferred version."

addedOutput schema / properties / funding / items / properties / periods

Added value: +{
+  "description": "Every distinct award period the funding item's versions record, ordered by start date — present only when there are two or more, such as renewals under one grant number. The other fields come from ORCID's preferred version.",
+  "items": {
+    "additionalProperties": false,
+    "description": "Award period one version of this funding item records.",
+    "properties": {
+      "endDate": {
+        "description": "Period end date (YYYY, YYYY-MM, or YYYY-MM-DD).",
+        "type": "string"
+      },
+      "startDate": {
+        "description": "Period start date (YYYY, YYYY-MM, or YYYY-MM-DD).",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / funding / items / properties / sources

Added value: +{
+  "description": "Every party that added this funding item to the ORCID record — the researcher, a funder or institution, or a search-and-link tool — one entry per distinct source in the funding group, the preferred version's first. 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 / funding / items / required

Previous value: -[
-  "grantNumbers"
-]New value: +[
+  "grantNumbers",
+  "sources"
+]

changedOutput schema / properties / fundingCount / description

Previous value: -"Total number of funding records returned."New value: +"Number of funding items returned, one per ORCID funding group — versions of one grant added by different sources or deposited twice count once."

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",
+      "fundingCount",
+      "funding"
+    ]
+  },
+  {
+    "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",
-  "fundingCount",
-  "funding"
-]

First observedMay 29, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing data provenance (researcher or member organizations, with 'sources' naming the contributor) and a critical completeness caveat that absence of records does not imply absence of funding. These are exactly the behavioral traits an agent cannot infer from annotations or schema.

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

Conciseness4/5

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

Four sentences, front-loaded with the core action and return payload, then provenance and caveat. Every sentence carries information, though the final value-proposition sentence is somewhat promotional and could be trimmed.

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?

An output schema exists, so return fields need not be fully specified, yet the description still previews the payload (funder names, identifiers, grant numbers, periods, sources). Combined with the provenance and completeness caveats, 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?

Only one parameter, and schema description coverage is 100% with a detailed pattern and format note for orcid_id. The description adds nothing about the identifier's accepted forms, so the baseline of 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 and resource ('Fetch funding records for an ORCID researcher') and enumerates the record types (grants, contracts, awards, salary awards). This clearly distinguishes it from siblings like orcid_get_works, orcid_get_affiliations, and orcid_get_peer_reviews without needing their schemas.

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

Usage Guidelines3/5

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

The description implies when the data is relevant ('high-value for grant tracking and funder analysis') and warns of a low-yield case, but never names an alternative tool or states when to prefer another sibling. Usage is inferable but no explicit routing or exclusion guidance is given.

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.