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.

LibraryAPI

PYPI · LIBRARYAPI-MCP

US public libraries and branches near any address, with collections from the IMLS survey

Available components

+1 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 86% of PyPI servers

Category Maps and Location

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 28 dependencies flagged as unhealthy. View diagnostics → Pass
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 (MIT).Pass
  • Actively maintained (last published 30 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 727 tokens (~121/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
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 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 29 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 26 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 20 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.83 → pass security
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 4 Nov 2026 · Analysed pypi/libraryapi-mcp@0.1.3

Provenance No attestation

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

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 28 packages
Packages resolved 28
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~648 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
find_libraries_near_address ~135

Find the public library branches nearest to a US street address, sorted by distance. Args: address: Full US street address, e.g. "350 Fifth Ave, New York, NY" radius_miles: Search radius in miles (0.1–50, default 10) limit: Maximum branches to return (1–100, default 10) include_closed: Include temporarily-closed branches (default False)

NameTypeReqDescription
addressstringyes–
include_closedboolean––
limitinteger––
radius_milesnumber––

No output schema declared.

No examples provided.

find_libraries_near_coordinates ~166

Find the public library branches nearest to a latitude/longitude, sorted by distance. Use this when you already have coordinates; it skips geocoding and is faster than find_libraries_near_address. Args: lat: Latitude (WGS84) lng: Longitude (WGS84) radius_miles: Search radius in miles (0.1–50, default 10) limit: Maximum branches to return (1–100, default 10) include_closed: Include temporarily-closed branches (default False)

NameTypeReqDescription
include_closedboolean––
latnumberyes–
limitinteger––
lngnumberyes–
radius_milesnumber––

No output schema declared.

No examples provided.

get_library ~72

Get the full profile for a library system by its FSCS ID, including collections, staffing, visits, programs, and finances. Args: fscs_id: IMLS FSCS ID for the library system, e.g. "IL0021"

NameTypeReqDescription
fscs_idstringyes–

No output schema declared.

No examples provided.

get_outlet ~57

Get the full record for one library branch (outlet) by its ID, including address, phone, coordinates, and service details. Args: outlet_id: IMLS outlet ID

NameTypeReqDescription
outlet_idstringyes–

No output schema declared.

No examples provided.

get_state_summary ~55

Get statewide public library totals — systems, branch outlets, collections, and usage — for one state. Args: state_code: Two-letter state abbreviation, e.g. "IL"

NameTypeReqDescription
state_codestringyes–

No output schema declared.

No examples provided.

search_libraries ~163

Search public library *systems* by name, state, and/or city. A system is the administrative entity (e.g. "Chicago Public Library") that operates one or more branch outlets. Provide at least one of name, state, or city. Args: name: Library system name (full-text search) state: Two-letter state code, e.g. "IL" city: City name (substring match) limit: Results per page (1–100, default 20) offset: Pagination offset (default 0)

NameTypeReqDescription
citystring––
limitinteger––
namestring––
offsetinteger––
statestring––

No output schema declared.

No examples provided.

Install

How do I install the LibraryAPI MCP server?

LibraryAPI runs locally as a PyPI package, launched with uvx libraryapi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · libraryapi-mcp

# add to Claude Code
claude mcp add dev-libraryapi-libraryapi-mcp -- uvx libraryapi-mcp
Common questions

What is the LibraryAPI MCP server?

LibraryAPI is an MCP server listed in the public MCP registry as dev.libraryapi/libraryapi-mcp. US public libraries and branches near any address, with collections from the IMLS survey. This page covers its PyPI package (libraryapi-mcp).

Is the LibraryAPI MCP server safe to use?

LibraryAPI scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 LibraryAPI MCP server expose?

LibraryAPI exposes 6 tools: find_libraries_near_address, find_libraries_near_coordinates, get_outlet, search_libraries, get_library, get_state_summary. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.

Is the LibraryAPI MCP server still maintained?

LibraryAPI is still listed as active in the MCP registry. We last reached this channel on 4 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 LibraryAPI MCP server under?

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