Skip to main content
Glama

Related Servers

Alternatives to Plot & Kin

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to conduct inspectable research with native Codex or Claude providers, producing locally saved dossiers with source-linked findings, evidence levels, falsifiers, limitations, and recorded retrieval events.
      1 npm
      2
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables revision-bound source audits with exact article fingerprinting, claim-to-source mapping, quotation verification, and immutable JSON evidence reports for prepublication review.
      9
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Family history research toolkit with 79 archives and databases, name variants, historical calendars, kinship, evidence checks, GEDCOM auditing and archive-request drafts. An MIT-licensed Python MCP server that runs locally without API keys or network requests.
      28
      1,199 PyPI
      3
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables locally-first literature research through an MCP host by collecting sources, parsing documents, retrieving evidence, validating citations, and exporting research records in multiple formats.
      38
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides local, evidence-aware research memory with human review, revision history, and an inspector, allowing assistants to preserve source reports, inferences, assumptions, and evidence across sessions.
      2 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables scientists and their AI agents to check quoted passages against pinned open-access PubMed Central full texts, look up retraction status from PMC and Crossref, and run recorded literature searches. Every quote check, search and annotation is written to an append-only, hash-chained log that can be verified, giving a dated record of what was searched and found.
      7
      MIT

    TDQS

    C2.9/5.0

    Scored across 37 tools

    Disambiguation3/5

    Many tools have distinct purposes, but setup_status and welcome have identical descriptions, and the processing cluster (processing_queue, pages_process, page_process, page_retry) plus the transfer trio (project_transfer, transfer_recover, transfer_status) can be confused. Descriptions help, but an agent may still misselect among similar-sounding operations.

    Naming Consistency4/5

    Nearly all names use snake_case and are readable, with predictable noun_verb or verb_noun patterns for related resources (project_*, source_*, page_*). Minor inconsistencies include singular/plural (page_process vs pages_process) and one-word welcome, but no chaotic mixing.

    Tool Count2/5

    37 tools is excessive for most agent workflows; while the property-history research domain is complex, this count exceeds the 25+ threshold where tools become hard to discover and select. Several tools could be consolidated (setup_status/welcome, processing queue/process/retry).

    Completeness4/5

    The surface covers the core research lifecycle: project creation, source import/read/search, page processing, passage/entity/claim proposal, review, budget, transfer, restore, export, and dossier. Minor gaps include no explicit delete/archive or direct update for projects/claims/sources, but provenance-preserving design makes these less critical.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues