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.

AI4L Library

NPM · AI4L-LIBRARY

Local Markdown library of the papers an evidence review cites: metadata, abstract and full text

Available components

0 this week 59 Trust /100

Last scanned (4 hours ago)

Scores higher than 30% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 9 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 511 tokens (~170/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: 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.

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.

  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 44

    First indexed and scored.

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/ai4l-library@0.1.1

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 101 packages
Packages resolved 101
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~215 tokens

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 →

Tool Tokens
get_version ~37

Get the running ai4l-library MCP server's package name and version, and the resolved library directory. Useful to confirm which build is loaded.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

library_add ~104

Build the library entry for one paper ID and return its status JSON. v0.1: pmid: only, pubmed tier only (level abstract). Idempotent — an existing entry is returned without refetching.

NameTypeReqDescription
idstringyesPaper ID as "type:value", e.g. "pmid:30955454"; bare digits count as pmid.
urlstring–A download location obtained elsewhere (ignored in v0.1).

No output schema declared.

No examples provided.

library_status ~74

Read-only status of the library entry for one paper ID: the same status JSON as library_add, or level "missing" when there is no entry. Never fetches.

NameTypeReqDescription
idstringyesPaper ID as "type:value", e.g. "pmid:30955454"; bare digits count as pmid.

No output schema declared.

No examples provided.

Install

How do I install the AI4L Library MCP server?

AI4L Library runs locally as an npm package, launched with npx -y ai4l-library. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ai4l-library

# add to Claude Code
claude mcp add forever-healthy-ai4l-library -- npx -y ai4l-library
Common questions

What is the AI4L Library MCP server?

AI4L Library is an MCP server listed in the public MCP registry as io.github.forever-healthy/ai4l-library. Local Markdown library of the papers an evidence review cites: metadata, abstract and full text. This page covers its npm package (ai4l-library).

Is the AI4L Library MCP server safe to use?

AI4L Library scores 59 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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.

What tools does the AI4L Library MCP server expose?

AI4L Library exposes 3 tools: library_add, library_status, get_version. Their descriptions and schemas cost roughly 215 tokens of context every time the server is loaded.

Is the AI4L Library MCP server still maintained?

AI4L Library 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 AI4L Library MCP server under?

AI4L Library declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.