Skip to main content
Glama

Related Servers

Alternatives to Strata

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides a compiled knowledge substrate, extracting atomic claims from an append-only capture log and querying a bitemporal claim graph over MCP. Read-only by default, with opt-in writes for trusted sources.
      4
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for querying an evidence-aware knowledge vault with temporal and provenance-aware data, supporting agent memory and semantic graph projections.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An embedded knowledge graph in one SQLite file, exposing a MCP server for agents to read and write entities and relationships with full audit trail and time travel.
      23 PyPI
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to work with an embedded graph database over MCP by exposing tools for entity storage, declarative rule creation, similarity search, association explanations, role-filtered queries, and historical edge inspection. It supports building and querying self-maintaining graphs locally with explainable derived relationships.
      5
      -
    • A
      license
      A
      quality
      C
      maintenance
      Runs a local, read-only knowledge graph over MCP, enabling graph queries, path finding, explanations, neighbor exploration, statistics, and god-node discovery without cloud dependencies.
      10
      Apache 2.0

    TDQS

    C2.8/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools occupy clearly distinct niches: single-unit inspection (describe), set-based stratigraphy (below/above), pairwise comparison (relation), and specialized readouts (date_bracket, provenance, period_sequence). The only mild overlaps are describe vs below/above (direct neighbours vs full transitive sets) and issues vs explain_issue (list vs detail), both of which the descriptions resolve. Write tools (propose_relation, resolve_order, assign_phase, add_note) are semantically distinct rather than redundant.

    Naming Consistency3/5

    All names are lowercase snake_case with no camelCase mixing, which keeps things readable. However the convention itself is split between bare imperative verbs (query, describe, revert, recheck) and noun labels (overview, issues, history, provenance), with compound verb_noun forms only in some cases (propose_relation, add_note). It is consistent in formatting but not in grammatical style.

    Tool Count4/5

    Nineteen tools is on the heavy side, but the domain genuinely spans reads (overview, describe, relation, date_bracket, provenance), analysis (period_sequence, issues, explain_issue), and transactional writes (propose_relation, resolve_order, assign_phase, revert, recheck). Each tool maps to a distinct question an archaeologist would ask, so the count feels earned rather than padded.

    Completeness4/5

    The read and interpretive-write surface is thorough: navigable stratigraphy, dating, provenance, issue triage, edit history, and reversible edits. The clear gap is unit/site lifecycle — there is no create/update/delete for units or finds, and no export, so new stratigraphic records must come from outside the server. That is likely intentional for an interpretation layer over a Relate file, but it leaves a dead end for record-level changes.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues