@cyanheads/orcid-mcp-server 0.1.1

package/README.md

@@ -0,0 +1,321 @@
+<div align="center">
+  <h1>@cyanheads/orcid-mcp-server</h1>
+  <p><b>Search and retrieve researcher profiles, works, affiliations, funding, and peer review records from the ORCID registry via MCP. STDIO or Streamable HTTP.</b>
+  <div>7 Tools • 2 Resources</div>
+  </p>
+</div>
+
+<div align="center">
+
+[![Version](https://img.shields.io/badge/Version-0.1.1-blue.svg?style=flat-square)](./CHANGELOG.md) [![License](https://img.shields.io/badge/License-Apache%202.0-orange.svg?style=flat-square)](./LICENSE) [![MCP SDK](https://img.shields.io/badge/MCP%20SDK-^1.29.0-green.svg?style=flat-square)](https://modelcontextprotocol.io/) [![TypeScript](https://img.shields.io/badge/TypeScript-^6.0.3-3178C6.svg?style=flat-square)](https://www.typescriptlang.org/) [![Bun](https://img.shields.io/badge/Bun-v1.3.2-blueviolet.svg?style=flat-square)](https://bun.sh/)
+
+</div>
+
+<div align="center">
+
+[![Framework](https://img.shields.io/badge/Built%20on-@cyanheads/mcp--ts--core-67E8F9?style=flat-square)](https://www.npmjs.com/package/@cyanheads/mcp-ts-core)
+
+</div>
+
+---
+
+## Tools
+
+Seven tools organized around three workflows — author disambiguation, researcher profiling, and cross-server identifier chaining:
+
+| Tool | Description |
+|:-----|:------------|
+| `orcid_search_researchers` | Search the ORCID registry using structured field params (name, affiliation, keyword, ROR ID, DOI, PMID). All params are ANDed into a Solr query against the expanded-search endpoint, returning ORCID iDs with inline name and institution data. |
+| `orcid_get_profile` | Fetch a researcher's public profile: name, biography, keywords, researcher URLs, and external identifiers (Scopus Author ID, ResearcherID, Loop, etc.). |
+| `orcid_get_works` | Retrieve works (publications, datasets, software, preprints) for a researcher. Returns titles, types, publication dates, journal names, and all external identifiers — DOIs, PMIDs, arXiv IDs — ready for chaining to Crossref, PubMed, or arXiv servers. |
+| `orcid_get_affiliations` | Fetch affiliation records for a researcher. Accepts a `types` list to filter which sections to return: `employment`, `education`, `invited-positions`, `distinctions`, `memberships`, `qualifications`, `services`, or `all`. |
+| `orcid_get_funding` | Fetch funding records: grants, contracts, awards, and salary awards, with funder names, grant numbers, and funding periods. |
+| `orcid_get_peer_reviews` | Fetch peer review activity: convening organizations, reviewer role, review type, completion dates, and ISSN-keyed group identifiers. |
+| `orcid_resolve_researcher` | Disambiguate an ambiguous author name to a verified ORCID iD. Returns a ranked list of up to 5 candidates with transparent signals: name match type, institution overlap, and whether a DOI or PMID anchor was used. |
+
+### `orcid_search_researchers`
+
+Search the ORCID registry with structured field parameters mapped to Solr field queries.
+
+- Structured params — `given_name`, `family_name`, `affiliation`, `keyword`, `ror_id`, `doi`, `pmid` — are ANDed into a Solr query automatically
+- `doi` and `pmid` translate to `doi-self` and `pmid-self` field queries: "who has linked this work to their ORCID record?"
+- `query` appends raw Solr to the generated clause for advanced use
+- `ror_id` values (full URLs like `https://ror.org/00f54p054`) are quoted internally to handle Solr's colon parsing
+- Returns expanded-search results with inline name and institution data — no follow-up profile fetch needed for basic discovery
+- Use this for precise field-anchored lookups; use `orcid_resolve_researcher` for ambiguous names needing ranked disambiguation
+
+---
+
+### `orcid_get_profile`
+
+Fetch a researcher's public person section by ORCID iD.
+
+- Accepts bare ORCID iD (`0000-0001-2345-6789`) or full URI form
+- Returns name, biography, keywords, researcher URLs, addresses, and external identifiers (Scopus Author ID, ResearcherID, Loop, etc.)
+- External identifiers are embedded in the person response — no separate round-trip
+- Entry point for building a researcher dossier before fetching works or affiliations
+
+---
+
+### `orcid_get_works`
+
+Retrieve the works list for a researcher.
+
+- Returns work summaries: title, type, publication date, journal name, and all external identifiers (DOI, PMID, arXiv ID, ISBN, etc.)
+- External IDs are returned in formats consumable by downstream servers (Crossref, PubMed, arXiv)
+- Works list is summaries only — chain to the relevant server for full metadata or abstracts
+
+---
+
+### `orcid_get_affiliations`
+
+Fetch affiliation records by type, using a single `/activities` call filtered client-side.
+
+- `types` controls which sections to include: `employment`, `education`, `invited-positions`, `distinctions`, `memberships`, `qualifications`, `services`, or `all`
+- Default is `['employment', 'education']` (the 90% case)
+- Returns organization names, disambiguated org IDs (ROR/GRID/Ringgold), departments, roles, and date ranges
+- One upstream call regardless of how many types are requested — the `/activities` endpoint returns all sections at once
+
+---
+
+### `orcid_get_funding`
+
+Fetch funding records for a researcher.
+
+- Returns grants, contracts, awards, and salary awards with funder names, grant numbers, and funding periods
+- Funding data is self-reported and often sparse — absence does not mean no funding
+- Useful when it exists; high-value (grant numbers, funder IDs) but a thin single-endpoint wrapper
+
+---
+
+### `orcid_get_peer_reviews`
+
+Fetch peer review activity for a researcher.
+
+- Returns convening organizations (journals/publishers), reviewer role (`reviewer`, `editor`, `chair`, etc.), review type, completion dates, and ISSN-keyed group identifiers
+- Useful for assessing editorial activity and journal affiliations
+
+---
+
+### `orcid_resolve_researcher`
+
+Disambiguate an author name to a verified ORCID iD.
+
+- Returns up to 5 ranked candidates with transparent disambiguation signals: name match type (`exact`/`partial`/`other-name`), institution overlap flag, and anchor type (`doi`/`pmid`/`none`)
+- When `doi` or `pmid` is provided, uses `doi-self` or `pmid-self` as an anchor — researchers who have linked that work to their ORCID record are near-deterministic matches
+- Falls back to a relaxed query (dropping affiliation) if the initial candidate set is empty
+- No synthetic scores — raw signal fields only, so callers can apply their own ranking logic
+
+## Resources
+
+| Type | Name | Description |
+|:-----|:-----|:------------|
+| Resource | `orcid://researcher/{orcid_id}/profile` | Researcher profile (person section: name, bio, keywords, external IDs). Prefer the tool when the response needs to flow into conditional logic. |
+| Resource | `orcid://researcher/{orcid_id}/works` | Works list for a researcher. DOIs and PMIDs in the response are ready for Crossref/PubMed chaining. |
+
+All resource data is also reachable via tools. Use resources when injecting stable researcher context into a prompt; use tools when filtering or processing results is needed.
+
+## Features
+
+Built on [`@cyanheads/mcp-ts-core`](https://www.npmjs.com/package/@cyanheads/mcp-ts-core):
+
+- Declarative tool and resource definitions — single file per primitive, framework handles registration and validation
+- Unified error handling — handlers throw, framework catches, classifies, and formats
+- Pluggable auth: `none`, `jwt`, `oauth`
+- Swappable storage backends: `in-memory`, `filesystem`, `Supabase`, `Cloudflare KV/R2/D1`
+- Structured logging with optional OpenTelemetry tracing
+- STDIO and Streamable HTTP transports
+
+ORCID-specific:
+
+- ORCID Public API v3.0 (`https://pub.orcid.org/v3.0/`) — no API key required for public read endpoints
+- `expanded-search` as the primary search backend — returns ORCID iD, name, and institution data inline, eliminating N+1 profile fetches
+- Single `/activities` call for affiliation queries, filtered client-side — eliminates up to 7 parallel upstream calls vs. per-section fetching
+- External identifiers (DOIs, PMIDs, arXiv IDs) surfaced in works responses in formats ready for cross-server chaining
+
+Agent-friendly output:
+
+- Transparent disambiguation signals in `orcid_resolve_researcher` — name match type, institution overlap, and anchor type are returned as raw fields, not a synthetic score, so agents can reason about match confidence
+- Known-limitation annotations — works list surfaces `num_found` so agents know when the 10,000-result public API cap was hit; funding and profile tools note when sections are empty due to researcher-controlled visibility
+- External identifier pass-through — DOIs, PMIDs, arXiv IDs, Scopus Author IDs are normalized to formats consumable by downstream servers without parsing
+
+## Getting started
+
+Add the following to your MCP client configuration file. No API key is required — the ORCID Public API is open for public read access.
+
+```json
+{
+  "mcpServers": {
+    "orcid": {
+      "type": "stdio",
+      "command": "bunx",
+      "args": ["@cyanheads/orcid-mcp-server@latest"],
+      "env": {
+        "MCP_TRANSPORT_TYPE": "stdio",
+        "MCP_LOG_LEVEL": "info"
+      }
+    }
+  }
+}
+```
+
+Or with npx (no Bun required):
+
+```json
+{
+  "mcpServers": {
+    "orcid": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "@cyanheads/orcid-mcp-server@latest"],
+      "env": {
+        "MCP_TRANSPORT_TYPE": "stdio",
+        "MCP_LOG_LEVEL": "info"
+      }
+    }
+  }
+}
+```
+
+Or with Docker:
+
+```json
+{
+  "mcpServers": {
+    "orcid": {
+      "type": "stdio",
+      "command": "docker",
+      "args": [
+        "run", "-i", "--rm",
+        "-e", "MCP_TRANSPORT_TYPE=stdio",
+        "ghcr.io/cyanheads/orcid-mcp-server:latest"
+      ]
+    }
+  }
+}
+```
+
+For Streamable HTTP, set the transport and start the server:
+
+```sh
+MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
+# Server listens at http://localhost:3010/mcp
+```
+
+### Prerequisites
+
+- [Bun v1.3.2](https://bun.sh/) or higher (or Node.js v24+).
+- No API key required. The ORCID Public API is open for public read access. Non-commercial use only under [ORCID Public API ToS §2](https://info.orcid.org/public-client-terms-of-service/).
+
+### Installation
+
+1. **Clone the repository:**
+
+```sh
+git clone https://github.com/cyanheads/orcid-mcp-server.git
+```
+
+2. **Navigate into the directory:**
+
+```sh
+cd orcid-mcp-server
+```
+
+3. **Install dependencies:**
+
+```sh
+bun install
+```
+
+4. **Configure environment:**
+
+```sh
+cp .env.example .env
+# edit .env if needed — no required vars
+```
+
+## Configuration
+
+All configuration is validated at startup via Zod schemas in `src/config/server-config.ts`. Key environment variables:
+
+| Variable | Description | Default |
+|:---------|:------------|:--------|
+| `ORCID_API_BASE_URL` | Override the ORCID API base URL. Useful for pointing at the sandbox (`https://pub.sandbox.orcid.org/v3.0/`). | `https://pub.orcid.org/v3.0/` |
+| `MCP_TRANSPORT_TYPE` | Transport: `stdio` or `http` | `stdio` |
+| `MCP_HTTP_PORT` | HTTP server port | `3010` |
+| `MCP_HTTP_ENDPOINT_PATH` | HTTP endpoint path | `/mcp` |
+| `MCP_PUBLIC_URL` | Public origin for TLS-terminating reverse-proxy deployments | none |
+| `MCP_AUTH_MODE` | Authentication: `none`, `jwt`, or `oauth` | `none` |
+| `MCP_LOG_LEVEL` | Log level (`debug`, `info`, `warning`, `error`, etc.) | `info` |
+| `MCP_GC_PRESSURE_INTERVAL_MS` | Opt-in Bun-only forced-GC pressure loop (ms). Try `60000` if heap growth is observed under sustained HTTP load. | `0` (disabled) |
+| `LOGS_DIR` | Directory for log files (Node.js only) | `<project-root>/logs` |
+| `STORAGE_PROVIDER_TYPE` | Storage backend: `in-memory`, `filesystem`, `supabase`, `cloudflare-kv/r2/d1` | `in-memory` |
+| `OTEL_ENABLED` | Enable OpenTelemetry | `false` |
+
+See [`.env.example`](./.env.example) for the full list of optional overrides.
+
+## Running the server
+
+### Local development
+
+- **Build and run:**
+
+  ```sh
+  # One-time build
+  bun run rebuild
+
+  # Run the built server
+  bun run start:stdio
+  # or
+  bun run start:http
+  ```
+
+- **Run checks and tests:**
+
+  ```sh
+  bun run devcheck   # Lint, format, typecheck, security
+  bun run test       # Vitest test suite
+  bun run lint:mcp   # Validate MCP definitions against spec
+  ```
+
+### Docker
+
+```sh
+docker build -t orcid-mcp-server .
+docker run --rm -p 3010:3010 orcid-mcp-server
+```
+
+The Dockerfile defaults to HTTP transport, stateless session mode, and logs to `/var/log/orcid-mcp-server`. OpenTelemetry peer dependencies are installed by default — build with `--build-arg OTEL_ENABLED=false` to omit them.
+
+## Project structure
+
+| Directory | Purpose |
+|:----------|:--------|
+| `src/index.ts` | `createApp()` entry point — registers tools and resources, inits services. |
+| `src/config` | Server-specific environment variable parsing and validation with Zod. |
+| `src/mcp-server/tools` | Tool definitions (`*.tool.ts`). Seven tools across search, profile, works, affiliations, funding, peer reviews, and disambiguation. |
+| `src/mcp-server/resources` | Resource definitions (`*.resource.ts`). Profile and works resources. |
+| `src/services/orcid` | ORCID Public API v3.0 service layer — search, record section fetchers, retry/backoff. |
+| `tests/` | Unit and integration tests mirroring `src/`. |
+
+## Development guide
+
+See [`CLAUDE.md`](./CLAUDE.md) for development guidelines and architectural rules. The short version:
+
+- Handlers throw, framework catches — no `try/catch` in tool logic
+- Use `ctx.log` for request-scoped logging, `ctx.state` for tenant-scoped storage
+- Register new tools and resources in the `createApp()` arrays
+- Wrap ORCID API calls: validate raw response → normalize to domain type → return output schema; never fabricate missing fields
+
+## Contributing
+
+Issues and pull requests are welcome. Run checks and tests before submitting:
+
+```sh
+bun run devcheck
+bun run test
+```
+
+## License
+
+Apache-2.0 — see [LICENSE](./LICENSE) for details.

package/changelog/0.1.x/0.1.0.md

@@ -0,0 +1,20 @@
+---
+summary: "Initial release — 7 tools and 2 resources for the ORCID Public API v3.0"
+breaking: false
+security: false
+---
+
+# 0.1.0 — 2026-05-25
+
+## Added
+
+- **`orcid_search_researchers`** — search the ORCID registry with structured field params (`given_name`, `family_name`, `affiliation`, `keyword`, `ror_id`, `doi`, `pmid`) mapped to Solr queries via `expanded-search`
+- **`orcid_get_profile`** — fetch the person section of a public ORCID record: name, biography, keywords, researcher URLs, and external identifiers (Scopus, ResearcherID, Loop, etc.)
+- **`orcid_get_works`** — retrieve work summaries with all external identifiers (DOI, PMID, arXiv ID) in formats ready for cross-server chaining
+- **`orcid_get_affiliations`** — fetch affiliation records filtered by type (`employment`, `education`, `invited-positions`, `distinctions`, `memberships`, `qualifications`, `services`, `all`) via a single `/activities` call
+- **`orcid_get_funding`** — fetch funding records (grants, contracts, awards) with funder names and grant numbers
+- **`orcid_get_peer_reviews`** — fetch peer review activity with convening organizations, reviewer role, review type, and ISSN-keyed group identifiers
+- **`orcid_resolve_researcher`** — disambiguate an author name to a verified ORCID iD; returns ranked candidates with transparent signals (name match type, institution overlap, anchor type)
+- **`orcid://researcher/{orcid_id}/profile`** resource — researcher person section as stable inline context
+- **`orcid://researcher/{orcid_id}/works`** resource — researcher works list with external IDs as stable inline context
+- Scaffolded on `@cyanheads/mcp-ts-core ^0.9.9`

package/changelog/0.1.x/0.1.1.md

@@ -0,0 +1,13 @@
+---
+summary: "ORCID iD format validation, 404 error contract fix, description cleanup"
+breaking: false
+security: false
+---
+
+# 0.1.1 — 2026-05-25
+
+## Fixed
+
+- **ORCID iD format validation** — all tools and resources now reject malformed iDs at input parse time via a regex (`^\d{4}-\d{4}-\d{4}-\d{3}[\dX]$` or full URI form) instead of letting bad input reach the API
+- **Error contract not firing** — `orcid_get_profile`, `orcid_get_works`, `orcid_get_affiliations`, `orcid_get_funding`, `orcid_get_peer_reviews` now route ORCID 404s through `ctx.fail('profile_not_found', …)` so `data.reason` is present and correlated with the declared error contract
+- **Tool description noise** — `orcid_search_researchers` and `orcid_get_affiliations` descriptions trimmed of internal Solr field names and implementation notes not relevant to callers

package/changelog/template.md

@@ -0,0 +1,119 @@
+---
+# FORMAT REFERENCE — do not edit. Copy this file to
+# `changelog/<major.minor>.x/<version>.md` (e.g. `changelog/0.8.x/0.8.6.md`)
+# to author a new release. Set that file's H1 to `# <version> — YYYY-MM-DD`
+# with a concrete date.
+
+# Required. One-line GitHub Release-style headline. 350 character cap.
+# Default short and scannable. Don't pad, don't stitch unrelated changes with
+# semicolons — pick the headline. Quotes required: unquoted YAML treats `: `
+# inside the value as a key separator and fails GitHub's strict parser.
+summary: ""
+
+# Set `true` when consumers must change code to upgrade: API removals,
+# signature changes, config renames, behavior changes that break existing
+# usage. Flagged as `Breaking` in the rollup.
+breaking: false
+
+# Set `true` if this release contains any security fix. Pairs with the
+# `## Security` section below. Flagged as `Security` in the rollup so
+# users can triage upgrade urgency at a glance.
+security: false
+---
+
+# <version> — YYYY-MM-DD
+
+<!--
+  AUTHORING GUIDE — applies to the new per-version file you create from this
+  template.
+
+  Audience: someone scanning release notes to decide what affects them. Lead
+  each bullet with the symbol or concept name in **bold** so they can skip
+  what's irrelevant and zoom in on what's not.
+
+  Tone: terse, fact-dense, not verbose. Default to one sentence per bullet —
+  name the symbol, state what changed, stop. Use a second sentence only when
+  it carries weight. If a bullet feels long, it is.
+
+  Cut: mechanism walkthroughs (those belong in JSDoc, AGENTS.md, or the
+  relevant skill), ceremonial framings ("This release introduces…",
+  backwards-compat paragraphs), file-by-file test enumerations, internal
+  implementation notes. Prefer code/symbol names over English re-explanations.
+
+  Narrative intro: skip by default. Add one short sentence only when the
+  release theme genuinely needs framing the bullets can't carry.
+
+  Sections: Keep a Changelog order — Added, Changed, Deprecated, Removed,
+  Fixed, Security. Include only sections with entries; delete the rest
+  (including the commented-out scaffolding below). Don't ship empty headers.
+
+  Include: every distinct fact a reader needs to adopt or audit the release —
+  new exports, signatures, lint rule IDs, env vars, breaking changes, version
+  bumps on shipped skills. Nothing more.
+
+  Links: link issues, PRs, docs, or skills where they help a reader jump to
+  context. Once per item per entry — don't re-link the same issue in summary,
+  narrative, and bullet. Skip links for inline symbol names; code spans speak
+  for themselves.
+
+  Issue/PR URLs: use full URLs. GitHub's bare `#NN` auto-link only resolves
+  inside its own UI, not in npm reads or local editors.
+
+      [#38](https://github.com/cyanheads/mcp-ts-core/issues/38)   ← issue
+      [#42](https://github.com/cyanheads/mcp-ts-core/pull/42)     ← PR
+
+  Verify numbers exist before linking (`gh issue view NN`, `gh pr view NN`).
+  Never speculate on a future number — `#42` for an upcoming PR silently
+  resolves to whatever real item already owns 42, and timeline previews pull
+  in that unrelated item's metadata.
+
+  TAG ANNOTATIONS — the annotated tag body renders as the GitHub Release body
+  via `gh release create --notes-from-tag`. The tag is a derivative of this
+  changelog entry — a condensed, scannable version, not a copy. Format:
+
+    <theme — omit version number, GitHub prepends it>
+                                                          ← blank line
+    <1-2 sentence context: what this release does>
+                                                          ← blank line
+    Dependency bumps:                                     ← section header
+                                                          ← blank line
+    - `@cyanheads/mcp-ts-core` ^0.9.1 → ^0.9.6          ← bullet
+                                                          ← blank line
+    Changed:                                              ← only sections with entries
+                                                          ← blank line
+    - `format()` output includes `query` in text mode
+                                                          ← blank line
+    Added:
+                                                          ← blank line
+    - `manifest.json` scaffolded for MCPB bundle support
+    - Install badges (Claude Desktop, Cursor, VS Code)
+                                                          ← blank line
+    <N> tests pass; `bun run devcheck` clean.             ← footer
+
+  Never a flat comma-separated string. Always structured markdown with
+  sections. The tag must scan well as a rendered GitHub Release page.
+-->
+
+## Added
+
+-
+
+## Changed
+
+-
+
+<!-- ## Deprecated
+
+- -->
+
+<!-- ## Removed
+
+- -->
+
+## Fixed
+
+-
+
+<!-- ## Security
+
+- -->

package/dist/config/server-config.d.ts

@@ -0,0 +1,12 @@
+/**
+ * @fileoverview Server-specific environment variable configuration for orcid-mcp-server.
+ * @module config/server-config
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+declare const ServerConfigSchema: z.ZodObject<{
+    orcidApiBaseUrl: z.ZodDefault<z.ZodString>;
+}, z.core.$strip>;
+/** Returns the parsed server configuration, lazily initialized on first call. */
+export declare function getServerConfig(): z.infer<typeof ServerConfigSchema>;
+export {};
+//# sourceMappingURL=server-config.d.ts.map

package/dist/config/server-config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"server-config.d.ts","sourceRoot":"","sources":["../../src/config/server-config.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,wBAAwB,CAAC;AAG3C,QAAA,MAAM,kBAAkB;;iBAMtB,CAAC;AAIH,iFAAiF;AACjF,wBAAgB,eAAe,IAAI,CAAC,CAAC,KAAK,CAAC,OAAO,kBAAkB,CAAC,CAKpE"}

package/dist/config/server-config.js

@@ -0,0 +1,22 @@
+/**
+ * @fileoverview Server-specific environment variable configuration for orcid-mcp-server.
+ * @module config/server-config
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+import { parseEnvConfig } from '@cyanheads/mcp-ts-core/config';
+const ServerConfigSchema = z.object({
+    orcidApiBaseUrl: z
+        .string()
+        .url()
+        .default('https://pub.orcid.org/v3.0')
+        .describe('ORCID Public API base URL (default: https://pub.orcid.org/v3.0)'),
+});
+let _config;
+/** Returns the parsed server configuration, lazily initialized on first call. */
+export function getServerConfig() {
+    _config ??= parseEnvConfig(ServerConfigSchema, {
+        orcidApiBaseUrl: 'ORCID_API_BASE_URL',
+    });
+    return _config;
+}
+//# sourceMappingURL=server-config.js.map

package/dist/config/server-config.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"server-config.js","sourceRoot":"","sources":["../../src/config/server-config.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,CAAC,EAAE,MAAM,wBAAwB,CAAC;AAC3C,OAAO,EAAE,cAAc,EAAE,MAAM,+BAA+B,CAAC;AAE/D,MAAM,kBAAkB,GAAG,CAAC,CAAC,MAAM,CAAC;IAClC,eAAe,EAAE,CAAC;SACf,MAAM,EAAE;SACR,GAAG,EAAE;SACL,OAAO,CAAC,4BAA4B,CAAC;SACrC,QAAQ,CAAC,iEAAiE,CAAC;CAC/E,CAAC,CAAC;AAEH,IAAI,OAAuD,CAAC;AAE5D,iFAAiF;AACjF,MAAM,UAAU,eAAe;IAC7B,OAAO,KAAK,cAAc,CAAC,kBAAkB,EAAE;QAC7C,eAAe,EAAE,oBAAoB;KACtC,CAAC,CAAC;IACH,OAAO,OAAO,CAAC;AACjB,CAAC"}

package/dist/index.d.ts

@@ -0,0 +1,8 @@
+#!/usr/bin/env node
+/**
+ * @fileoverview orcid-mcp-server MCP server entry point. Provides access to the
+ * ORCID researcher registry: search, profiles, works, affiliations, funding, and peer reviews.
+ * @module index
+ */
+export {};
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;;GAIG"}

package/dist/index.js

@@ -0,0 +1,35 @@
+#!/usr/bin/env node
+/**
+ * @fileoverview orcid-mcp-server MCP server entry point. Provides access to the
+ * ORCID researcher registry: search, profiles, works, affiliations, funding, and peer reviews.
+ * @module index
+ */
+import { createApp } from '@cyanheads/mcp-ts-core';
+import { researcherProfileResource } from './mcp-server/resources/definitions/researcher-profile.resource.js';
+import { researcherWorksResource } from './mcp-server/resources/definitions/researcher-works.resource.js';
+import { orcidGetAffiliations } from './mcp-server/tools/definitions/get-affiliations.tool.js';
+import { orcidGetFunding } from './mcp-server/tools/definitions/get-funding.tool.js';
+import { orcidGetPeerReviews } from './mcp-server/tools/definitions/get-peer-reviews.tool.js';
+import { orcidGetProfile } from './mcp-server/tools/definitions/get-profile.tool.js';
+import { orcidGetWorks } from './mcp-server/tools/definitions/get-works.tool.js';
+import { orcidResolveResearcher } from './mcp-server/tools/definitions/resolve-researcher.tool.js';
+import { orcidSearchResearchers } from './mcp-server/tools/definitions/search-researchers.tool.js';
+import { initOrcidService } from './services/orcid/orcid-service.js';
+await createApp({
+    tools: [
+        orcidGetProfile,
+        orcidSearchResearchers,
+        orcidGetWorks,
+        orcidGetAffiliations,
+        orcidGetFunding,
+        orcidGetPeerReviews,
+        orcidResolveResearcher,
+    ],
+    resources: [researcherProfileResource, researcherWorksResource],
+    prompts: [],
+    setup(core) {
+        initOrcidService(core.config, core.storage);
+    },
+    instructions: 'ORCID researcher registry server. Use orcid_search_researchers for exact field lookups (name + institution + DOI/PMID). Use orcid_resolve_researcher when the input is an ambiguous author name needing ranked disambiguation. Use orcid_get_profile → orcid_get_works → orcid_get_affiliations to build a researcher dossier. DOIs and PMIDs from orcid_get_works are ready for chaining to Crossref or PubMed servers.',
+});
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":";AACA;;;;GAIG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,wBAAwB,CAAC;AACnD,OAAO,EAAE,yBAAyB,EAAE,MAAM,mEAAmE,CAAC;AAC9G,OAAO,EAAE,uBAAuB,EAAE,MAAM,iEAAiE,CAAC;AAC1G,OAAO,EAAE,oBAAoB,EAAE,MAAM,yDAAyD,CAAC;AAC/F,OAAO,EAAE,eAAe,EAAE,MAAM,oDAAoD,CAAC;AACrF,OAAO,EAAE,mBAAmB,EAAE,MAAM,yDAAyD,CAAC;AAC9F,OAAO,EAAE,eAAe,EAAE,MAAM,oDAAoD,CAAC;AACrF,OAAO,EAAE,aAAa,EAAE,MAAM,kDAAkD,CAAC;AACjF,OAAO,EAAE,sBAAsB,EAAE,MAAM,2DAA2D,CAAC;AACnG,OAAO,EAAE,sBAAsB,EAAE,MAAM,2DAA2D,CAAC;AACnG,OAAO,EAAE,gBAAgB,EAAE,MAAM,mCAAmC,CAAC;AAErE,MAAM,SAAS,CAAC;IACd,KAAK,EAAE;QACL,eAAe;QACf,sBAAsB;QACtB,aAAa;QACb,oBAAoB;QACpB,eAAe;QACf,mBAAmB;QACnB,sBAAsB;KACvB;IACD,SAAS,EAAE,CAAC,yBAAyB,EAAE,uBAAuB,CAAC;IAC/D,OAAO,EAAE,EAAE;IACX,KAAK,CAAC,IAAI;QACR,gBAAgB,CAAC,IAAI,CAAC,MAAM,EAAE,IAAI,CAAC,OAAO,CAAC,CAAC;IAC9C,CAAC;IACD,YAAY,EACV,0ZAA0Z;CAC7Z,CAAC,CAAC"}

package/dist/mcp-server/resources/definitions/researcher-profile.resource.d.ts

@@ -0,0 +1,24 @@
+/**
+ * @fileoverview Resource for injecting a researcher's ORCID profile (person section)
+ * as stable inline context into prompts. Use when the agent needs a researcher's
+ * identity data without conditional logic over the result.
+ * @module mcp-server/resources/definitions/researcher-profile.resource
+ */
+import { z } from '@cyanheads/mcp-ts-core';
+export declare const researcherProfileResource: import("@cyanheads/mcp-ts-core").ResourceDefinition<z.ZodObject<{
+    orcid_id: z.ZodString;
+}, z.core.$strip>, z.ZodObject<{
+    orcidId: z.ZodString;
+    orcidUri: z.ZodString;
+    givenNames: z.ZodOptional<z.ZodString>;
+    familyName: z.ZodOptional<z.ZodString>;
+    creditName: z.ZodOptional<z.ZodString>;
+    biography: z.ZodOptional<z.ZodString>;
+    keywords: z.ZodArray<z.ZodString>;
+    externalIdentifiers: z.ZodArray<z.ZodObject<{
+        type: z.ZodString;
+        value: z.ZodString;
+        url: z.ZodOptional<z.ZodString>;
+    }, z.core.$strip>>;
+}, z.core.$strip>, undefined>;
+//# sourceMappingURL=researcher-profile.resource.d.ts.map

package/dist/mcp-server/resources/definitions/researcher-profile.resource.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"researcher-profile.resource.d.ts","sourceRoot":"","sources":["../../../../src/mcp-server/resources/definitions/researcher-profile.resource.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,OAAO,EAAY,CAAC,EAAE,MAAM,wBAAwB,CAAC;AAIrD,eAAO,MAAM,yBAAyB;;;;;;;;;;;;;;;6BAoEpC,CAAC"}

package/dist/mcp-server/resources/definitions/researcher-profile.resource.js

@@ -0,0 +1,62 @@
+/**
+ * @fileoverview Resource for injecting a researcher's ORCID profile (person section)
+ * as stable inline context into prompts. Use when the agent needs a researcher's
+ * identity data without conditional logic over the result.
+ * @module mcp-server/resources/definitions/researcher-profile.resource
+ */
+import { resource, z } from '@cyanheads/mcp-ts-core';
+import { notFound } from '@cyanheads/mcp-ts-core/errors';
+import { getOrcidService, normalizeOrcidId } from '../../../services/orcid/orcid-service.js';
+export const researcherProfileResource = resource('orcid://researcher/{orcid_id}/profile', {
+    name: 'orcid-researcher-profile',
+    description: 'Researcher profile (person section) from ORCID: name, biography, keywords, researcher URLs, and external identifiers. Use when injecting researcher identity context into a prompt or checking for a specific external ID (e.g., Scopus ID for cross-server chaining). Prefer the orcid_get_profile tool when the response needs to flow into conditional logic.',
+    mimeType: 'application/json',
+    params: z.object({
+        orcid_id: z
+            .string()
+            .regex(/^(https?:\/\/orcid\.org\/)?\d{4}-\d{4}-\d{4}-\d{3}[\dX]$/, 'Must be a valid ORCID iD (e.g. 0000-0001-2345-6789) or full ORCID URI.')
+            .describe('ORCID iD — bare format (0000-0001-2345-6789) or full URI (https://orcid.org/0000-0001-2345-6789).'),
+    }),
+    output: z.object({
+        orcidId: z.string().describe('Normalized ORCID iD (bare format).'),
+        orcidUri: z.string().describe('Full ORCID URI.'),
+        givenNames: z.string().optional().describe('Given names, if publicly visible.'),
+        familyName: z.string().optional().describe('Family name, if publicly visible.'),
+        creditName: z.string().optional().describe('Published credit name, if set.'),
+        biography: z.string().optional().describe('Researcher biography, if publicly visible.'),
+        keywords: z.array(z.string().describe('Keyword.')).describe('Research keywords.'),
+        externalIdentifiers: z
+            .array(z
+            .object({
+            type: z.string().describe('Identifier type.'),
+            value: z.string().describe('Identifier value.'),
+            url: z.string().optional().describe('Resolver URL.'),
+        })
+            .describe('External identifier.'))
+            .describe('External scholarly identifiers (Scopus, ResearcherID, Loop, etc.).'),
+    }),
+    async handler(params, ctx) {
+        const service = getOrcidService();
+        const bareId = normalizeOrcidId(params.orcid_id);
+        ctx.log.debug('orcid-researcher-profile resource', { orcidId: bareId });
+        const person = await service.getPerson(params.orcid_id, ctx);
+        if (!person.givenNames && !person.familyName && !person.creditName) {
+            throw notFound(`No public profile found for ORCID iD ${bareId}. The record may not exist or may be fully private.`);
+        }
+        return {
+            orcidId: bareId,
+            orcidUri: `https://orcid.org/${bareId}`,
+            ...(person.givenNames && { givenNames: person.givenNames }),
+            ...(person.familyName && { familyName: person.familyName }),
+            ...(person.creditName && { creditName: person.creditName }),
+            ...(person.biography && { biography: person.biography }),
+            keywords: person.keywords,
+            externalIdentifiers: person.externalIdentifiers.map((id) => ({
+                type: id.type,
+                value: id.value,
+                ...(id.url && { url: id.url }),
+            })),
+        };
+    },
+});
+//# sourceMappingURL=researcher-profile.resource.js.map