Skip to main content
Glama
efficjump

Architecture Drift MCP

by efficjump
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Architecture Drift MCP

No user-submitted related servers found.

    Related Servers

    • Verinoda

      Verinoda-Labs
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to analyze a repository evidence-first, answering questions as verifiable claims with source evidence, targeted test observations, and reference resolution.
      5
      3
      Apache 2.0

    • trigsight

      Raghu23-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables verification of portfolio claims by resolving citations to exact supporting sentences at build time, providing read-only tools to list work, find evidence, check stack mentions, and read case studies while failing the build on any unverifiable claim.
      MIT

    • RefSentry

      LloydPhuc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to verify citations and bibliographies and to check whether source documents support factual claims, using local inference, exact evidence provenance, and deterministic verdicts.
      MIT

    • clearon-source-audit

      kwgoodwin
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct responsibility, from audit lifecycle (create/list/get) to the analysis pipeline (discover/extract/compare/adjudicate) to output generation (propose/build). No two tools appear to perform overlapping actions, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, with specific verbs like create, list, get, discover, extract, compare, adjudicate, propose, and build. There is no mixing of conventions or ambiguous verbs.

    Tool Count5/5

    Ten tools is within the optimal range for a specialized workflow. Each tool contributes a unique step in the architecture drift detection process without redundancy or unnecessary bloat.

    Completeness4/5

    The tool set covers the full drift detection workflow: audit creation, source discovery, claim/fact extraction, comparison, adjudication, patch proposal, and report generation. Minor gaps exist such as no explicit audit deletion or patch application, but these are not core to the domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources