# LibraryAPI (pypi · libraryapi-mcp)

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

- Trust score: 81/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `libraryapi-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/dev-libraryapi-libraryapi-mcp/libraryapi-mcp.md), [page](https://verifymcp.io/servers/dev-libraryapi-libraryapi-mcp/libraryapi-mcp)

## Channel facts

- Registry: `pypi`
- Package: `libraryapi-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 34 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add dev-libraryapi-libraryapi-mcp -- uvx libraryapi-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-libraryapi-libraryapi-mcp": {
      "command": "uvx",
      "args": [
        "libraryapi-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-libraryapi-libraryapi-mcp": {
      "command": "uvx",
      "args": [
        "libraryapi-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-libraryapi-libraryapi-mcp -- uvx libraryapi-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-libraryapi-libraryapi-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "libraryapi-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-libraryapi-libraryapi-mcp --command uvx --arg libraryapi-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-libraryapi-libraryapi-mcp:
    command: "uvx"
    args: ["libraryapi-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-libraryapi-libraryapi-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "libraryapi-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-libraryapi-libraryapi-mcp -t stdio -c uvx -a libraryapi-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-libraryapi-libraryapi-mcp": {
      "command": "uvx",
      "args": [
        "libraryapi-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 79, −3)

- [functional] Stability: pass → 0.80

### 2026-09-15 (score 82, +15)

- [security improvement] Malware scan: unverified → pass
- [security] Stability: 0.97 → pass

### 2026-09-14 (score 67, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-12 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-11 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-10 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `find_libraries_near_address` (~135 tokens)

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)

Input parameters:

- `address` (string, required)
- `include_closed` (boolean)
- `limit` (integer)
- `radius_miles` (number)

### `find_libraries_near_coordinates` (~166 tokens)

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)

Input parameters:

- `include_closed` (boolean)
- `lat` (number, required)
- `limit` (integer)
- `lng` (number, required)
- `radius_miles` (number)

### `get_outlet` (~57 tokens)

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

Input parameters:

- `outlet_id` (string, required)

### `search_libraries` (~163 tokens)

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)

Input parameters:

- `city` (string)
- `limit` (integer)
- `name` (string)
- `offset` (integer)
- `state` (string)

### `get_library` (~72 tokens)

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"

Input parameters:

- `fscs_id` (string, required)

### `get_state_summary` (~55 tokens)

Get statewide public library totals — systems, branch outlets, collections,
and usage — for one state.

Args:
    state_code: Two-letter state abbreviation, e.g. "IL"

Input parameters:

- `state_code` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-libraryapi-libraryapi-mcp/libraryapi-mcp#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 82
- 2026-09-14: 67
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 65
- 2026-09-10: 80
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 77
- 2026-09-04: 77
- 2026-09-03: 76
- 2026-09-02: 76
- 2026-09-01: 75
- 2026-08-31: 75
- 2026-08-30: 75
- 2026-08-29: 74
- 2026-08-28: 74
- 2026-08-27: 73
- 2026-08-26: 73
- 2026-08-25: 70
- 2026-08-24: 70
- 2026-08-23: 66
- 2026-08-22: 66

## 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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.

## Links

- PyPI project: https://pypi.org/project/libraryapi-mcp/
- Socket report: https://socket.dev/pypi/package/libraryapi-mcp
- Repository: https://github.com/library-api/libraryapi-mcp
- Website: https://libraryapi.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-libraryapi-libraryapi-mcp/libraryapi-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-libraryapi-libraryapi-mcp/libraryapi-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-libraryapi-libraryapi-mcp/libraryapi-mcp