Skip to main content
Glama

Related Servers

Alternatives to ClickTrail MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      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
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only inspection of ad-bid recommendations, scenario analysis, and explanation of threshold decisions using synthetic fixtures, without requiring live ad accounts or credentials.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides coding agents with local tools to inspect project UI inventories, propose and compare visual direction boards, compile versioned design contracts and DTCG tokens, retrieve section-specific blueprints, and audit running interfaces with browser evidence including screenshots, accessibility findings, and overflow measurements.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides source-backed design context, route card validation, contract generation, critique and verification reports, evidence packages, Penpot change plans, and anti-repeat checks for design workflows. Does not directly mutate Penpot, but consumes read-only Penpot snapshots.
      1 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP tools for coding agents to audit deployment targets, detect fabricated code, review backlog, database schema, analytics, ML models, architecture docs, and decision lenses.
      11
      7 npm
      MIT

    TDQS

    C2.7/5.0

    Scored across 20 tools

    Disambiguation2/5

    Multiple tools overlap in diagnostic and validation purposes: validate_attribution_pipeline, diagnose_missing_click_ids, calculate_click_id_coverage, detect_attribution_gaps, and attribution_health all assess attribution health from slightly different angles, making selection ambiguous. The three send_* tools also differ only by payload type, adding further confusion.

    Naming Consistency4/5

    Nearly all tools follow a consistent verb_noun snake_case pattern (capture_, generate_, send_, verify_, etc.), which aids predictability. The lone exception is 'attribution_health', which breaks the pattern with a noun_noun construction, causing a minor inconsistency.

    Tool Count3/5

    With 20 tools, the server sits in the heavy range (16-25). The domain is broad, but many diagnostic and sending tools could be merged into fewer general-purpose tools without losing capability, making the count feel somewhat excessive.

    Completeness4/5

    The tool set covers the core attribution lifecycle: schema, integration generation, capture verification, conversion payload construction, delivery verification, diagnosis, and reconciliation. Minor gaps like a generic integration generator or direct conversion mutation exist but are workable for most agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues