Skip to main content
Glama
aston-cook

changelog

by aston-cook
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to changelog

No user-submitted related servers found.

    Related Servers

    • Selvedge

      masondelan
      A
      license
      A
      quality
      A
      maintenance
      Change tracking for AI-era codebases. AI agents call it to log structured change events (entity + diff + reasoning) before the session ends, then query history with diff, blame, history, changeset, and search. Captures the intent that would otherwise evaporate.
      8
      24
      MIT

    • staysfixed

      asadev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to prove that previously working behavior still works after code changes by running the product through the same steps twice and surfacing only unintended differences as actionable findings.
      110 npm
      MIT

    • Gizmo Analytics

      sudomichael
      A
      license
      A
      quality
      D
      maintenance
      Privacy friendly, cookieless web analytics built MCP-first. "Add analytics to my Next.js app" → an AI agent runs the setup_analytics_for_site tool, picks the right install snippet, edits your layout file, and verifies the script is loading. OAuth onboarding, no API keys to paste.
      28
      27 npm
      1
      MIT
    • BarrHawk by barrhawk

      BarrHawkofficial

      barrhawk
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables automated end-to-end testing and verification of web applications through natural language, with self-healing selectors and dual-mode execution.
      15
      -

    • Causal Decision Agent

      vikranthviki
      A
      license
      C
      quality
      C
      maintenance
      Enables evidence-backed business decisions by connecting questions to experiment and metric data, applying statistical analyses, and producing rollout, hold, or investigate verdicts with reproducible audit traces.
      500
      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

    A4.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    log_change records a new change while check_changes evaluates already-logged changes. They operate on different phases of the same lifecycle, so there is no practical ambiguity about which tool to call.

    Naming Consistency5/5

    Both tool names follow a clear verb_noun pattern: log_change and check_changes. The naming style is consistent and immediately communicates each tool's action.

    Tool Count4/5

    Two tools is below the typical 3-15 range, but the server is narrowly scoped to logging and evaluating changes. Each tool is necessary and the pair covers the full intended workflow without redundancy.

    Completeness5/5

    The server covers the complete lifecycle for its stated purpose: log a user-visible change, then check whether that change moved a metric. There are no obvious dead ends or missing operations for this narrow domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources