Skip to main content
Glama

Related Servers

Alternatives to Engagement MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to query a single-source ontology of types, entities, statements, evidence, and controlled vocabulary, including bitemporal "as of" and "as recorded" fact lookups. Supports writing by letting agents propose candidate statements while keeping approval, review transitions, and authoritative reasoning restricted to approved facts.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables grounded read-only queries over a local knowledge base, reviewable pending updates, and audited merging of changes.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a local-first, evidence-backed ledger for physical property, enabling agents to search inventory, prepare capture reviews, and inspect proposals through MCP. Enforces strict boundaries: scoped reads by default, with private write access limited to preparing, not applying, mutations.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables software agents to maintain a signed, evidence-aware local ledger of claims, with policy-gated proposals, conflict queries, and constitution-pinned access through an MCP stdio server.
      7
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to view active beliefs, read owner-selected source text, submit inferred extraction for selected sources, and consult bounded choices from a local personal profile.
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation3/5

    The core resource/action pairs are mostly understandable, but job_overview, open_items, gate_check, and run_check overlap around gate states, HIGH-severity items, and validation. Descriptions help separate summary vs listing vs validation, but an agent can still reasonably hesitate among several tools for a status or gate query.

    Naming Consistency3/5

    All names use lowercase snake_case, which is readable, but the semantic patterns are mixed: verb_noun (get_node, read_doc), noun_phrase (job_overview, open_items, intake_status), and single verb (find). The convention is not chaotic, but it is not predictably consistent.

    Tool Count5/5

    Eight tools is a well-scoped size for a read-only engagement oversight server. Each tool appears to earn its place across overview, search, node inspection, open items, gates, validation, intake, and document reading.

    Completeness4/5

    The surface covers the apparent read-only domain well: status, search, node retrieval, open items, gate validation, intake tracking, and document reading. Minor gaps remain, such as no explicit broad node listing beyond keyword search, but agents can mostly work around this via find and get_node.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues