Skip to main content
Glama

Related Servers

Alternatives to aleph-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables read-only search and exploration of the GenizahSearch research API, including manuscript search, page browsing, parallel finding, and multi-phrase queries, along with policy resources and research prompts.
      4
      Creative Commons Attribution Non Commercial Share Alike 4.0 International
    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to query OpenCTI read-only during triage: resolving hashes, IPs, domains, URLs and emails against observables, and retrieving indicators, reports and relationships with scores, markings and external references. Enforces a TLP ceiling and input/output hardening so no data above the configured marking level is exposed.
      5
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only interaction with Elasticsearch, supporting listing indices, retrieving mappings, and executing search/aggregation queries via MCP.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Provides read-only access to a Mailfact tenant, letting users list domains, sending sources, and aggregate reports, and query DMARC alignment, reporter coverage, and record-level data through MCP tools. It returns counts and rows only, without recommending policies or scoring domains.
      9
      36 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct Aleph operation: search, entity retrieval, network expansion, identity matching, collection metadata, statistics, schema lookup, xref result reading, and document text extraction. The closest pair (aleph_similar_entities and aleph_xref_results) is separated clearly by entity-level versus dataset-level scope.

    Naming Consistency3/5

    All tools share the aleph_ prefix and snake_case, but they do not follow one verb_noun convention: get_entity, list_collections, and fetch_document_text are verb-object, while statistics, xref_results, and similar_entities are noun/adjective phrases and search is a bare verb. Names are readable and predictable enough to navigate, but the pattern is mixed.

    Tool Count5/5

    Ten tools is well-scoped for an Aleph data exploration server: each tool covers a distinct read-side capability with no redundant utility tools or bloat.

    Completeness4/5

    The read-side investigation workflow is well covered: discover collections, search, inspect, expand, match, and read document text. However, the surface is explicitly read-only—there is no way to create or update casefile entities, write collections, or start a new cross-reference run—so it is not a full Aleph admin or casefile API.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues