Skip to main content
Glama
chinese-history-mcp

chinese-history-mcp

by lizhuojunx86

Related Servers

Alternatives to chinese-history-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Self-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 etc
      14
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to query a dated, provenance-backed history distilled from any text stream, turning raw records into observations, bi-temporal facets, and narratives over MCP.
      12
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for evidence retrieval in Yellow River Basin human–earth systems reviews, exposing PostgreSQL-backed tools for searching and comparing evidence, entities, and spatiotemporal data while preserving source provenance.
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A stdio MCP server for traceable scholarly retrieval and evidence-grounded literature review, with deterministic provider fusion, conservative ID canonicalization, and provenance-preserving citation traversal.
      2
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A local MCP server for querying Chinese scientific literature from the CSL dataset, enabling paper search, detail retrieval, and dataset statistics via MCP clients.
      5
      -

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct search dimension: events, persons, places, and qualities. The descriptions clearly separate their use cases, leaving no ambiguity about which tool to select for a given query.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (search_events, get_person), while two use query_by_ (place, quality). This minor deviation is still readable and doesn't confuse the overall naming convention.

    Tool Count5/5

    With 4 tools, the server is well-scoped for its purpose. Each tool earns its place, covering different aspects of Chinese history knowledge without redundancy or bloat.

    Completeness4/5

    The toolset covers core search dimensions (event, person, place, quality), but lacks time-based or dynasty-specific queries and direct source text retrieval. These are minor gaps that agents can work around using the provided tools.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data