Skip to main content
Glama

Related Servers

Alternatives to ClickTrail MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables local, read-only checks of financial disclosure claims against fixed research snapshots, including cutoff queries, operating metric scope, cash-bridge arithmetic, claim tracing, and replayable evidence packets.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI coding agents to perform evidence-based, read-only audits of supported software projects by exposing bounded project inventory and static-analysis findings for discovery, code review, integration tracing, security, and tests. Reports are returned as Markdown or JSON directly in the tool response, with no code executed or files written.
      8
      38 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to inspect recorded browser flows—including user actions, network activity, console output, storage, DOM events, and screen recordings—for debugging, bug reporting, and regression testing without reproducing the issue.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Gives coding agents local access to a project's code-quality rules, located findings, previewable safe fixes, schema details, dependency advisories, and quality-gate results, with analysis confined to the project root and secrets masked.
      198 npm
      MIT
    • 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

    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

    ActivitySlowing
    ResponsivenessNo issues