Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Northwestern University Libraries Digital Collections API

NPM · @NULIB/DC-API-MCP · 3 COMPONENTS

Agent integration with the Northwestern University Libraries Digital Collections API

0 this week 46 Trust /100

Last scanned (7 hours ago)

Scores higher than 24% of npm servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 8.0.0, reached via aws-lambda > aws-sdk > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 49 of 139 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to nulib/dc-api-v2). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 31 Oct 26 0
    • Dependency health: partial → 0.82 functional
  • 29 Oct 26 0
    • Dependency health: 0.82 → partial functional
    • Package version: 2.11.15 → 2.12.0 functional
  • 12 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Sept 26 0
    • Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. security
    • Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
    • Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
    • Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
    • Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
  • 15 Sept 26 0
    • Package version: 2.11.14 → 2.11.15 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@nulib/dc-api-mcp@2.12.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo nulib/dc-api-v2
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/nulib/dc-api-v2/.github/workflows/publish-mcp.yml@refs/tags/v2.12.0
Rekor log index 3572086982
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:c50e23a40eb908d826371747c6c5e2696cbf71e05cb3cdb23fa6ce5e758a1be73c2aec4345659200eee23e936fae49fab80e54e89f7955c2dcd3c1340

Background: How many MCP packages publish verified provenance →

Vulnerabilities 2 findings
ID CVE Severity Vector Fix available
GHSA-j965-2qgj-vjmq low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N no
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 139 packages
Packages resolved 139
Deprecated 3
Stale 47
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Northwestern University Libraries Digital Collections API MCP server?

Northwestern University Libraries Digital Collections API runs locally as an npm package, launched with npx -y @nulib/dc-api-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @nulib/dc-api-mcp

# add to Claude Code
claude mcp add nulib-dc-api -- npx -y @nulib/dc-api-mcp
Common questions

What is the Northwestern University Libraries Digital Collections API MCP server?

Northwestern University Libraries Digital Collections API is an MCP server listed in the public MCP registry as io.github.nulib/dc-api. Agent integration with the Northwestern University Libraries Digital Collections API. This page covers its npm package (@nulib/dc-api-mcp).

Is the Northwestern University Libraries Digital Collections API MCP server safe to use?

Northwestern University Libraries Digital Collections API scores 46 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the Northwestern University Libraries Digital Collections API MCP server still maintained?

Northwestern University Libraries Digital Collections API is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Northwestern University Libraries Digital Collections API MCP server under?

Northwestern University Libraries Digital Collections API declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.