Skip to main content
Glama
API Change Monitor MCP Server

API Change Monitor MCP Server

Related Servers

Alternatives to API Change Monitor MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables evidence-bearing change monitoring for public text pages, providing normalized diffing, SHA-256 hashing, and signed webhook notifications.
      6
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Monitors a company domain for changes in hiring, tech stack, funding, firmographics, and social presence, returning only the deltas as typed change events.
      1
      114 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to register RSS/Atom/JSON Feed URLs and be alerted when their content changes, including in-place edits to existing items that produce no new entry. It reports field-level diffs (what field changed, from what to what) and pushes HMAC-signed webhook notifications, with SSRF protection and retry handling.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables an AI client to track a watch list of contacts and retrieve only what changed since the last run — departures, new employers, replacements, and new hires after a role closed — each row carrying match evidence, source dates, and ready-to-use outreach payloads. It runs the analysis on Apify using the caller's own provider keys, supports stored or caller-held state, and can push results to a signed webhook.
      1
      110 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there are no competing tools to confuse; an agent has a single unambiguous entry point for all monitoring tasks.

    Naming Consistency5/5

    The sole tool name monitor_api_changes follows a clear verb_noun convention and accurately reflects its purpose.

    Tool Count3/5

    A single tool is thin for a server covering many source types and row types; while the monitoring purpose is focused, there is no separate operation for state management, source listing, or run history, making the surface borderline.

    Completeness3/5

    The tool covers change detection across changelogs, status pages, and OpenAPI specs well, but lacks explicit operations for managing monitors, resetting or inspecting state_key history, or retrieving past runs, creating notable lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing