theosis-ancient-context-mcp
Related Servers
Alternatives to theosis-ancient-context-mcp
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceGives any MCP client outcome-oriented tools to find official primary-source documents, read their facts with provenance, count the corpus, and check ingestion-pipeline health. Runs over stdio locally or as a bearer-token Streamable HTTP service, with toolsets enabled per deployment.1MIT- AlicenseAqualityBmaintenanceSelf-hosted read-only MCP server over a local library of ancient-text corpora — 2.47M documents and 118M passages from 258 sources (cuneiform, Classical, biblical, medieval and more), with the license class tracked on every passage. 14 research tools: full-text search, concordance, passage display, dictionary definitions, etymologies, cognates, parallel passages, text alignment, place lookup etc146MIT
- AlicenseAqualityCmaintenanceProvides read-only access to ORACC open cuneiform data, enabling listing of projects, retrieval of metadata, manifests, and text excerpts, and searching of catalogues.6MIT
- AlicenseAqualityCmaintenanceProvides read-only Codex consultation tools over MCP, enabling fresh threads, continuation, and project reviews via local stdio.3MIT
- AlicenseAqualityBmaintenanceExposes forensic case and evidence management operations over stdio, including case creation, evidence registration with SHA-256 hashing, and integrity verification, so clients can manage DFIR investigations programmatically.7MIT
- AlicenseNot gradedqualityBmaintenanceEnables any agent to query the same interview corpus as the UI over stdio, exposing tools to list transcripts, search quoted lines, retrieve verified themes with citations and dropped reasons, and fetch source lines.9 npmMIT
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: listing all corpora, checking one corpus's detailed status, searching within a corpus, retrieving text content, and fetching text metadata. There is no meaningful functional overlap, and even the status-related tools are cleanly separated by all-versus-one scope.
All tools use a consistent verb_noun snake_case pattern: list_corpora, get_corpus_status, search_corpus, get_text, get_text_metadata. Plural and singular nouns are used naturally for collection-level versus single-item operations, so the naming is predictable.
Five tools is a well-scoped size for a read-only ancient-text corpus access server. Each tool earns its place in the workflow without redundancy or unnecessary surface area.
The tool surface covers the apparent domain completely: discover available corpora, inspect corpus status, search for texts, retrieve text content, and retrieve metadata. Deferred or remote-only sources are handled explicitly rather than resulting in dead-end errors, and no CRUD operations are expected for this read-only context.