Skip to main content
Glama
mambalabsdev

company-change-event-feed

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to company-change-event-feed

No user-submitted related servers found.

    Related Servers

    • Account Hiring Watch MCP

      mambalabsdev
      A
      license
      A
      quality
      B
      maintenance
      Enables users to track a list of company domains and retrieve only the job-board changes since the previous run, including new, closed, and reposted postings with full descriptions, stable posting keys, and 30-day hiring velocity per company. It runs on Apify and exposes this through a single tool call.
      1
      106 npm
      MIT

    • Career Change Signal Engine

      mambalabsdev
      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

    • API Change Monitor MCP Server

      mambalabsdev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables monitoring chosen API vendors and public URLs, comparing each source with its saved baseline and returning only new changelog entries, status incidents, OpenAPI operation changes, and Sunset or Deprecation header updates.
      MIT

    • TokenEnrich MCP Server

      barnsbytarquin
      A
      license
      A
      quality
      C
      maintenance
      Enables enrichment of company domains with verified firmographic signals including tech stack, hiring activity, email infrastructure, and SOC 2 compliance, returning compact typed JSON for AI agents.
      3
      7 npm
      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.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool in the set, there is no possibility of selecting the wrong tool, and the description clearly scopes it to change detection over time rather than one-time enrichment. It even explicitly names the sibling tools to use for the excluded use case, removing boundary confusion.

    Naming Consistency5/5

    The single tool uses a clean snake_case verb_noun pattern (get_company_changes) that would extend predictably to siblings. There are no competing conventions to conflict with.

    Tool Count3/5

    For a change-feed domain, one operation-centric tool is defensible since baseline/diff behavior is folded into it, but a single tool is a thin surface for a server. It leans borderline rather than comfortably scoped.

    Completeness4/5

    The tool covers the core lifecycle: baseline capture, diffing against stored or explicit snapshots, typed change events, per-source status, and batching. Minor gaps remain, such as no way to list known domains, inspect or reset a stored snapshot, or query historical change events.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources