orcid-mcp-server

Get ORCID Researcher Peer Reviews

orcid_get_peer_reviews

Read-onlyIdempotent

Fetch peer review activity for an ORCID researcher: reviewer role (reviewer, editor, chair, etc.), review type, completion dates, ISSN-keyed group identifiers, and the convening organization as ORCID records it — often the service that imported the review (e.g. Publons, Clarivate). ORCID returns no journal name; groupIssn is the key to the journal, and a review that has one is headed by it. Use to assess editorial activity, journal affiliations, and the scope of a researcher's peer review contributions. Reviews come from the researcher or from member organizations that import them; sources names who added each, and coverage varies by researcher.

Input Schema

Name	Required	Description
`limit`	No	Reviews per page. Default 25; a larger value returns at most 1,000 and says so.
`offset`	No	Zero-based review offset; continue with nextOffset.
`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

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Deprecated-iD disclosure naming the primary iD, requested/effective limit disclosure, past-end guidance, or empty-history guidance.
`offset`	No	Zero-based offset applied to this page.
`orcidId`	No	Normalized ORCID iD (bare format).
`orcidUri`	No	Full ORCID URI.
`truncated`	No	True when more reviews remain after this page.
`nextOffset`	No	First omitted review offset; absent on final, empty, or past-end pages.
`totalCount`	No	Total reviews before pagination.
`peerReviews`	No	Peer review records for this ORCID iD.
`reviewCount`	No	Total number of peer review records returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 28, 2026

changedInput schema / properties / limit / default
```
Previous value: -50New value: +25
```

changedInput schema / properties / limit / description

Previous value: -"Requested page size (default 50, accepted maximum 10,000, effective maximum 1,000). Each surface is bounded to 64,000 bytes, except an indivisible oversized review returned alone with a notice."New value: +"Reviews per page. Default 25; a larger value returns at most 1,000 and says so."

changedOutput schema / properties / notice / description

Previous value: -"Empty-history guidance, requested/effective limit disclosure, or an explicit indivisible-review budget exception."New value: +"Deprecated-iD disclosure naming the primary iD, requested/effective limit disclosure, past-end guidance, or empty-history guidance."

changed

Output schema / properties / peerReviews / items / properties / sources / items / properties / selfAsserted / description

Previous value: -"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."New value: +"True when the asserting party (the assertion origin when recorded, otherwise the source) is the record's ORCID iD (orcidId); false when a member organization or another ORCID user asserted the item."

Changed8 schema fields changedOct 18, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 50,
+  "description": "Requested page size (default 50, accepted maximum 10,000, effective maximum 1,000). Each surface is bounded to 64,000 bytes, except an indivisible oversized review returned alone with a notice.",
+  "maximum": 10000,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / offset

Added value: +{
+  "default": 0,
+  "description": "Zero-based review offset; continue with nextOffset.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / anyOf

Previous value: -[
-  {
-    "not": {
-      "required": [
-        "error"
-      ]
-    },
-    "required": [
-      "orcidId",
-      "orcidUri",
-      "reviewCount",
-      "peerReviews"
-    ]
-  },
-  {
-    "required": [
-      "error"
-    ]
-  }
-]New value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "orcidId",
+      "orcidUri",
+      "reviewCount",
+      "totalCount",
+      "offset",
+      "truncated",
+      "peerReviews"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / nextOffset

Added value: +{
+  "description": "First omitted review offset; absent on final, empty, or past-end pages.",
+  "type": "number"
+}

changedOutput schema / properties / notice / description

Previous value: -"Note when no peer reviews are found — coverage varies by researcher and publisher participation."New value: +"Empty-history guidance, requested/effective limit disclosure, or an explicit indivisible-review budget exception."

addedOutput schema / properties / offset

Added value: +{
+  "description": "Zero-based offset applied to this page.",
+  "type": "number"
+}

addedOutput schema / properties / totalCount

Added value: +{
+  "description": "Total reviews before pagination.",
+  "type": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "True when more reviews remain after this page.",
+  "type": "boolean"
+}

Changed7 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 / peerReviews / items / properties / conveningOrganization / description

Previous value: -"Journal or publisher that convened the review."New value: +"Organization ORCID records as convening the review, often the importing service. Identify the journal by groupIssn."

changedOutput schema / properties / peerReviews / items / properties / conveningOrganization / properties / name / description

Previous value: -"Convening organization name (journal or publisher)."New value: +"Convening organization name as ORCID records it — often the service that imported the review (e.g. Publons)."

changedOutput schema / properties / peerReviews / items / properties / groupIssn / description

Previous value: -"ISSN of the journal group this review belongs to, if available."New value: +"ISSN of the journal group this review belongs to, if available — the key to the journal name, which ORCID does not return."

addedOutput schema / properties / peerReviews / items / properties / sources

Added value: +{
+  "description": "The party that added this review to the ORCID record — the researcher, or a member organization such as a review-import service or publisher. 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"
+}

addedOutput schema / properties / peerReviews / items / required
```
Added value: +[
+  "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",
+      "reviewCount",
+      "peerReviews"
+    ]
+  },
+  {
+    "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",
-  "reviewCount",
-  "peerReviews"
-]

First observedMay 29, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes well beyond the annotations (which already declare readOnly/idempotent/openWorld) by disclosing real data quirks: ORCID returns no journal name, groupIssn is the journal key, sources names who contributed each record, and coverage varies by researcher. That provenance and coverage caveat is exactly the kind of context annotations cannot carry; only the pagination cap behavior is left to the 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?

Three sentences, front-loaded with the payload contents before moving to interpretation guidance and provenance. The groupIssn/journal-name explanation is slightly long-winded but earns its place because that quirk would otherwise mislead an agent.

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

Completeness4/5

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

With an output schema present and 100% param coverage, the description only needs to add interpretive context — and it does, covering data provenance, the ISSN-keyed journal gap, and variable coverage. Nothing critical is missing, though a note on typical result volumes or ordering would round it out.

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 schema already explains limit, offset, and the orcid_id format/pattern in detail. The description adds no parameter-level meaning 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 and resource ('Fetch peer review activity for an ORCID researcher') and enumerates the fields returned (reviewer role, review type, completion dates, groupIssn, convening organization). This makes it trivially distinguishable from siblings like orcid_get_works or orcid_get_funding, which cover different record types.

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?

Explicitly says 'Use to assess editorial activity, journal affiliations, and the scope of a researcher's peer review contributions,' giving clear selection context. It does not, however, name when to prefer a sibling (e.g. orcid_get_works for publications vs. this tool) or state exclusions.

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.