# io.github.smeet666/mcp-books (npm · mcp-books)

Search the Internet Archive, the Library of Congress and data.bnf.fr at once, in one answer.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-13

## Components

- mcpb · `mcp-books-1.2.0.mcpb`: 40/100, [markdown](https://verifymcp.io/servers/smeet666-mcp-books/https-github-com-smeet666-mcp-books-releases-download-v1-2-0-mcp-books-1-2-0-mcp.md), [page](https://verifymcp.io/servers/smeet666-mcp-books/https-github-com-smeet666-mcp-books-releases-download-v1-2-0-mcp-books-1-2-0-mcp)
- npm · `mcp-books`: 78/100 (this document), [markdown](https://verifymcp.io/servers/smeet666-mcp-books/mcp-books.md), [page](https://verifymcp.io/servers/smeet666-mcp-books/mcp-books)

## Channel facts

- Registry: `npm`
- Package: `mcp-books`
- Version: `1.2.0`
- 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-08-13.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 98 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to smeet666/mcp-books).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3759 tokens (~1253/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add smeet666-mcp-books -- npx -y mcp-books
```

### Codex

```bash
codex mcp add smeet666-mcp-books -- npx -y mcp-books
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "smeet666-mcp-books": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-books"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add smeet666-mcp-books --command npx --arg -y --arg mcp-books
```

### Hermes

```yaml
mcp_servers:
  smeet666-mcp-books:
    command: "npx"
    args: ["-y", "mcp-books"]
```

### Other

```json
{
  "mcpServers": {
    "smeet666-mcp-books": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-books"
      ]
    }
  }
}
```

## 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-08-12 (score 78, +1)

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

### 2026-08-11 (score 77, +8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-10 (score 69, +1)

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

### 2026-08-09 (score 68, −6)

- [functional regression] Schema quality: 1088 → 1253
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → poor
- [functional] Package version: 1.1.0 → 1.2.0

### 2026-08-08 (score 74)

First indexed and scored.

## MCP tools (3)

### `search_inside` (~929 tokens)

Find a phrase in the scanned text of every archive

Search the machine-read text of every archive this server reads that holds any, at the same time, and get one list of where a phrase was printed. The archives behind this tool hold different material, so the list is additive: it is the places a phrase appears in each corpus, put together, rather than the same question answered twice. 'per_source' names what each corpus is. A match carries 'page_number', which is a real leaf on an archive whose index holds one and null on an archive whose index holds none. That null is the index having no leaf, never a page this server dropped, and no page is ever invented. A match also carries 'excerpt_kind'. 'passage' is the text around the words that matched. 'page_opening' is the start of the page, sent because the machine-read text that came back stops before the searched words appear, so it does not carry the match. The notes say how many excerpts are openings. Every count is that archive's own and counts something of its own: documents in one place, leaves in another. They are never added together, and there is no total across archives. Rows are interleaved one archive at a time. Nothing ranks them against each other and nothing orders them by date, because a year is measured on different things in each archive. Matches whose excerpt carries the searched words are placed before matches whose excerpt is a 'page_opening' and carries them nowhere. That rests on what each row states about its own excerpt rather than on any score, no match is ever dropped for it, and the interleaving holds inside each of the two groups. The archives read the words given in different ways, and 'per_source' says which each one does. An index that answers only where every word appears returns nothing for a question written as a sentence, even on a work it holds several copies of; an index that scores the words instead answers such a question with the pages it ranks highest, which can carry only some of them. Either way it is the words: a character th…

Input parameters:

- `fan_out` (boolean): Whether to derive shorter and differently spelled wordings from the query and ask each archive for the union of what they return. A question written as a sentence returns nothing where every word giv…
- `limit` (integer): Matches to take from each archive, so one archive cannot fill the whole list. The text block shows about six matches; the rest of what comes back is in the structured output.
- `max_excerpt_chars` (integer): Budget for one passage. Read it together with 'max_excerpts_per_match': the size of the answer is the product of the two, the limit, and the number of archives.
- `max_excerpts_per_match` (integer): Passages to keep per match. A long work matches in several places, and the later ones rarely say anything the first did not.
- `page` (integer): Which page of matches, from 1. Each archive is paged separately.
- `query` (string, required): Words, or a phrase in double quotes such as '"call me ishmael"'.
- `sources` (array): Archives to ask, by id. Left out, every archive that reads machine-read text is asked, which is the point of this tool.

Output parameters:

- `excerpt_kinds` (object): How many excerpts here are of each kind.
- `hit_count` (integer): Matches in this answer, across every archive. It is a count of what came back, never a total of what exists.
- `hits` (array)
- `non_word_characters` (array): Characters in the query that are neither letters nor digits. These indexes answer on words, so a match here can carry none of them, and 'requires_every_word' covers the words that were given rather t…
- `notes` (array)
- `order` (string): How the list was built, in words.
- `page` (integer)
- `per_source` (array)
- `queries_run` (integer): Requests this server sent for this answer, counting every wording on every archive. Each archive's own wordings are in 'per_source'.
- `query` (string)

### `search_items` (~1192 tokens)

Search every catalogue at once

Search the catalogue of every archive this server reads, at the same time, for a title, a creator or a subject, and get one merged list. Each row carries the id get_item takes, and that id names the archive it came from, so nothing has to be guessed afterwards. 'media_type' keeps one name across the archives and a vocabulary per archive, because the same word does not name the same set of things twice. An archive that files nothing under the name you give is not asked and is named as absent, with its own names listed, rather than asked under a translation. An archive that keeps one catalogue per kind of material is asked for its default when you name none, and the answer says which catalogue that was. Rows are interleaved one archive at a time. No score orders them against each other, and 'sort' is applied inside each archive rather than across them: a year is the date of an edition in one place and the date on a catalogue record in another, so there is no date order that spans the answer. 'oldest' and 'newest' order on a date field carrying a year and no era, so a date before the common era is filed there as a year of this one, and a record stating no date is placed by a stand-in rather than by its age. The first row of a date order is therefore not established as the oldest or newest thing an archive holds, the notes count the rows carrying no year, and this server orders nothing itself. Every count in 'per_source' is that archive's own and counts something of its own. They are never added together, and there is no total across archives. The catalogues read the words given in different ways, and 'per_source' says which each one does. One answers only where every word appears, so a question written as a sentence comes back empty; another scores the words and answers with the records it ranks highest, so a row of its can carry only some of them. Either way it is the words: a character that is neither a letter nor a digit is no word to an index, and 'non_word_charac…

Input parameters:

- `fan_out` (boolean): Whether to derive further wordings from the query and ask each archive for the union of what they return. A question written as a sentence returns nothing where every word given has to appear, and th…
- `limit` (integer): Rows to take from each archive, so one archive cannot fill the whole list.
- `media_type` (string): The kind of material, in the vocabulary of whichever archive uses that name. the Internet Archive files texts, movies, audio, image, software, data, web; the Library of Congress files books, photos,…
- `page` (integer): Which page of rows, from 1. Each archive is paged separately.
- `query` (string, required): A title, a creator, a subject, or plain words.
- `sort` (string): Applied inside each archive. The merged list stays interleaved, because no order runs across archives. 'oldest' and 'newest' run on a date field carrying a year and no era, and a record stating no da…
- `sources` (array): Archives to ask, by id. Left out, they are all asked, which is the point of this tool.
- `year_from` (integer): Earliest year, in each archive's own reading of what a year is. Given with 'year_to', it must not be the later of the two: a range running backwards names no year and is refused rather than read diff…
- `year_to` (integer): Latest year, in each archive's own reading of what a year is. It cannot be earlier than 'year_from'.

Output parameters:

- `item_count` (integer): Rows in this answer, across every archive. Never a total of what exists.
- `items` (array)
- `media_types` (array): Which name each archive was asked under, published rather than reconciled, so a caller can map the vocabularies once and read what was actually searched.
- `non_word_characters` (array): Characters in the query that are neither letters nor digits. These catalogues answer on words, so a row here can carry none of them, and 'requires_every_word' covers the words that were given rather…
- `notes` (array)
- `order` (string): How the list was built, in words.
- `page` (integer)
- `per_source` (array)
- `queries_run` (integer): Requests this server sent for this answer, counting every wording on every archive. Each archive's own wordings are in 'per_source'.
- `query` (string)

### `get_item` (~446 tokens)

Read one record, routed by the archive its identifier names

Read one record in full from the archive its identifier names: what it is, who made it, when, what the archive says about it, and what a reader can open. 'identifier' must come from search_inside or search_items. It names the archive, so this reads the right one without guessing; a string no archive would have minted is refused, and a shape more than one archive mints is refused rather than sent to a guess, because sending it anywhere answers about the wrong thing. Terms of reuse come back on every read and belong to that record alone. A record stating none has granted nothing, and silence is never read as permission. 'sections' decides what else comes back, and the answer names what was left out and what this archive files nothing under: a field empty because nobody asked for it is a different thing from a field the archive never fills. 'description_means' says what the archive files under the field this reads a description out of, which holds an account of the thing on one record and a line of the catalogue entry on the next. Long prose is returned one window at a time: 'text_offset' says where to resume, and a window ends at a line boundary. An offset past the end says so rather than answering with an empty description. An answer can take several seconds, because one of the archives publishes a request ceiling this server keeps to.

Input parameters:

- `identifier` (string, required): From a search, such as 'archive:mobydickorwhale01melv' or 'loc:sn83030214/1900-01-01/ed-1/seq-1'.
- `max_copies` (integer): Copies to list. The answer says how many more the record holds.
- `max_text_chars` (integer): Characters of prose to return. The text block shows roughly the first 1400 of them and the whole window is in the structured output. The answer says where to resume.
- `sections` (array): Which parts to return besides the record's identity and its terms of reuse.
- `text_offset` (integer): Where to resume in the record's prose, in characters from its start.

Output parameters:

- `fields_not_read_from_this_archive` (array): Fields this server reads nothing into from this archive. A field named here is empty for every record it returns, which is a different thing from a record that left it blank.
- `id_read_as`: How a raw identifier was routed, when it was not spelled with its archive.
- `item` (object)
- `notes` (array)
- `sections_omitted` (array): Sections this call did not ask for. A field belonging to one of these is empty for that reason alone.
- `sections_returned` (array)
- `text_window` (object): Which part of the record's prose this answer carries.

## Diagnostics

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

## Score history

- 2026-08-13: 78
- 2026-08-12: 78
- 2026-08-11: 77
- 2026-08-10: 69
- 2026-08-09: 68
- 2026-08-08: 74

## Links

- npm package: https://www.npmjs.com/package/mcp-books
- Socket report: https://socket.dev/npm/package/mcp-books
- Repository: https://github.com/smeet666/mcp-books
- Changelog RSS feed: https://verifymcp.io/servers/smeet666-mcp-books/mcp-books.xml
- Changelog JSON feed: https://verifymcp.io/servers/smeet666-mcp-books/mcp-books.json
- HTML version of this page: https://verifymcp.io/servers/smeet666-mcp-books/mcp-books