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.

io.github.cyanheads/libofcongress-mcp-server

NPM · @CYANHEADS/LIBOFCONGRESS-MCP-SERVER · SCANNED AUG 8

Search LOC digital collections, Chronicling America newspapers (full OCR), and LC Subject Headings.

Available components

npm · @cyanheads/libofcongress-mcp-server 44
+24 this week 44 Trust /100
Trust breakdown (6 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 →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 40 of 127 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 22 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 3 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @cyanheads/libofcongress-mcp-server

# add to Claude Code
claude mcp add cyanheads-libofcongress-mcp-server -- npx -y @cyanheads/libofcongress-mcp-server
# add to Codex CLI
codex mcp add cyanheads-libofcongress-mcp-server -- npx -y @cyanheads/libofcongress-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-libofcongress-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cyanheads/libofcongress-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-libofcongress-mcp-server --command npx --arg -y --arg @cyanheads/libofcongress-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-libofcongress-mcp-server:
    command: "npx"
    args: ["-y", "@cyanheads/libofcongress-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "cyanheads-libofcongress-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/libofcongress-mcp-server"
      ]
    }
  }
}
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.

  • 8 Aug 26 +1
    • Security disclosure: fail → pass ▲ functional
  • 7 Aug 26 +3
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 0.85 functional
  • 6 Aug 26 +5
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: Tool coverage not yet verified: this package declared that it provides tools, but our sandbox run could not list them. functional
    • Schema quality: Schema quality not yet verified: this package declared that it provides tools, but our sandbox run could not list them, so the captured schema is incomplete. functional
  • 5 Aug 26 +1
    • CVE-2026-69207 no longer affects this package ▲ security
    • Known CVEs: fail → partial ▲ security
  • 4 Aug 26 −1
    • CVE-2026-69207 affects this package: medium ▼ security
    • Known CVEs: partial → fail ▼ security
  • 2 Aug 26 +15
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Known CVEs: unverified → partial ▲ security
    • License: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • Licence: Apache-2.0 functional
  • 1 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 8 Aug 2026 · Analysed npm/@cyanheads/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 127 packages
Packages resolved 127
Stale 40
Tree resolution Complete
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.

The sandbox run completed and this package exposed no tools.