calibreweb-mcp

MCPattested
v0.3.1io.github.ni-cMITUpdated 26d agonpmGitHub

Read-only MCP server for Calibre-Web: library search, browsing and covers via the OPDS feed

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
26d agoLast update
Reads these credentials
  • CALIBRE_WEB_PASSWORDAPI keyoptional

    Password of that account (web login password)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.ni-c
LicenseMIT
Version0.3.1
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · ba1688d
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.2.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedAug 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev0.2.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

search_booksSearches the library by title, author, series, publisher and tags.

Searches the library by title, author, series, publisher and tags.

No input schema was published for this tool.

list_booksLists books from one of the Calibre-Web views: new (recently added,

Lists books from one of the Calibre-Web views: new (recently added,

No input schema was published for this tool.

get_coverFetches the cover of a book and returns it as an image. Book ids come

Fetches the cover of a book and returns it as an image. Book ids come

No input schema was published for this tool.

list_shelvesLists the shelves visible to the configured user: every public shelf

Lists the shelves visible to the configured user: every public shelf

No input schema was published for this tool.

get_shelf_booksLists the books on a shelf, in the shelf’s own order. Shelf ids

Lists the books on a shelf, in the shelf’s own order. Shelf ids

No input schema was published for this tool.

get_statsReturns the total number of books, authors, categories (tags) and

Returns the total number of books, authors, categories (tags) and

No input schema was published for this tool.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Read-only MCP server for Calibre-Web: library search, browsing and covers via the OPDS feed

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

63 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+51 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.