digibib
Related Servers
Alternatives to digibib
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceThis server allows Large Language Models to consume S1000D data and publication modules as structured information instead of raw XML. It enables reading the content's hierarchy, applicability to specific products, and document verification status.6338 npmMIT
- AlicenseNot gradedqualityBmaintenanceThis server provides an interface to interact with the DoorsetBook dataset by enabling search, comparison, and summarization of its contents. It allows users to query data, analyze statistics, and review the provenance of the dataset using structured calls.MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to look up digitized-book holdings and catalog records by standard identifiers, retrieve bibliographic metadata, and check whether readable full-view copies are available.93 npmMIT
- AlicenseAqualityBmaintenanceThis MCP server enables AI agents to search and retrieve exact, cited passages from a large corpus of public-domain books, including full-text search, book metadata, chapters, quotes, and 'ask book' Q&A. Payments are handled via x402 micropayments on Base.8536 npmMIT
- AlicenseAqualityCmaintenanceThis server enables large-scale conversion of massive PDF book libraries into Word and Markdown formats using the Model Context Protocol. It handles all AI processing server-side, eliminating the need for local API keys and keeping system memory consumption extremely low.4MIT
- AlicenseAqualityBmaintenanceThis read-only MCP server gives agents semantic search over an OpenViking knowledge base, plus tools to read a document's full text by URI and browse directories with their generated abstracts. It exposes no write operations, so lookups are all an agent can do.332 npmMIT
TDQS
Scored across 1 tool
The single dispatcher tool exposes clearly separated operations (list_volumes, descriptor, toc, node_text, record_text, search, images) with distinct inputs and outputs. The only real overlap is node_text vs record_text, which both return decoded text and differ only by addressing scheme (TOC node vs raw TEXT.DKI record index) — the descriptions clarify this, but an agent could still pick the wrong one.
The operations inside the tool consistently follow a snake_case verb_noun pattern (list_volumes, node_text, record_text). The tool itself is a single server-named dispatcher ('digibib') rather than a verb_noun action, which is a minor deviation but acceptable for a multi-operation facade.
A single exposed tool would normally feel thin, but it packs seven substantive operations covering the whole read lifecycle, so the surface is larger than the count suggests. Still, the single-tool dispatch pattern makes discovery and selection harder than a small set of explicit tools would.
For a read-only CD-ROM library reader the coverage is strong: volume listing, metadata, TOC navigation, chapter/record extraction, full-text search, and figure retrieval. Gaps are minor — no cross-volume aggregated search and no export/citation output, but agents can work around both by iterating volumes.