Skip to main content
Glama
PrattyT85

theosis-ancient-context-mcp

by PrattyT85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to theosis-ancient-context-mcp

No user-submitted related servers found.

    Related Servers

    • DEFAIR MCP Server

      joblinours
      A
      license
      A
      quality
      B
      maintenance
      Exposes 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.
      7
      MIT

    • receipts

      alexjpower74-create
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      17 npm
      MIT

    • RAG-MCP

      RITIKA-SHARMAA
      F
      license
      Not graded
      quality
      C
      maintenance
      Gives an LLM client BM25 keyword search over a local corpus of Markdown and text files, letting it find ranked passages, fetch exact chunks with source offsets, read whole documents, and list what was indexed. It runs entirely locally over stdio with an in-memory index, calling no model and requiring no API key.
      -

    • pywel

      RolandSaint
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to query a local, offline Crimson Desert knowledge base through stdio MCP, providing versioned entity/claim lookups, bounded search, codebook decoding, and typed responses with provenance context.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources