Skip to main content
Glama

Related Servers

Alternatives to armature-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query a repository's verified semantic model, including capabilities, ownership, contracts, constraints, impact, health, and verification status, without re-deriving project facts. It exposes read-only tools for inspecting, reasoning about, and verifying the provenance-tracked surface.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to read-only query a self-hosted repository knowledge base, searching documents, source code, and symbols across GitHub and GitLab imports while retrieving source and dependency traces by commit and path.
      3
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      Enables read-only querying of a source-linked programming-language catalogue, including language lookup, tool availability checks, candidate comparison, and evidence-backed stack recommendations from committed snapshots.
      7
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to query a CompanyGraph instance read-only, retrieving types, schemas, entities, skill evidence, and search results with verbatim answers from a specific model commit.
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target clearly distinct read operations (schema vs. records vs. history vs. coverage vs. attestation). The pairs that could be confused are module_coverage/course_coverage and trace_record/what_references, but the descriptions explicitly state the scope relationship (course-level rollup vs. one module; lifecycle walk vs. inbound links only), which helps.

    Naming Consistency3/5

    All names are snake_case, but the convention is mixed: verb_noun (describe_hub, list_modules, get_record, find_records, compare_record), noun_phrases (record_history, branch_changes, module_coverage, alignment_gaps, attestation_status, module_content, item_statistics), and one interrogative (what_references). Readable and mostly predictable, but not a single pattern.

    Tool Count4/5

    Seventeen tools for a genuinely broad domain (branches/commits, schema, records, coverage, alignment, tracing, attestation, psychometrics) with little redundancy. Slightly heavy but each tool maps to a distinct analysis question.

    Completeness4/5

    Read coverage of the design lifecycle is strong: schema, records, history/diffs, branch diffs, two-level coverage, alignment, tracing, references, attestation and item statistics. Minor gaps exist—there is no branch-level commit log (only latest commit per branch and per-record history) and no free-text/full-design search—but agents can work around them via branch_changes and record_history.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues