Company Change Event Feed MCP Server

Company Change-Event Feed MCP Server

Company Change-Event Feed monitors a company domain for changes across hiring, tech stack, funding, firmographics, and social presence, then diffs the current state against your last run and returns only what changed as typed change events. Flat, Clay-ready JSON, one row per company, built for RevOps teams, outbound agencies, Clay users, and AI agents that need delta intelligence on target accounts.

What it does

This server gives an AI client one tool:

• get_company_changes: monitor a company domain for changes across hiring, tech stack, funding, firmographics, and social since the last run. The first run for a domain records a clean baseline (no changes); every run after that returns only the deltas as typed change events, each with a severity, a confidence, an old and new value, and the immutable Actor ID of the source that produced it.

All of the work runs on Apify. This package is a thin client that routes the tool call to the actor and hands back the result.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:

{
  "mcpServers": {
    "company-change-event-feed": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-company-change-event-feed"],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The tool will be available.

Prerequisites

• Node.js 18 or newer
• An Apify account with an API token

Example prompts

• "What changed at stripe.com since the last check across hiring, tech stack, and firmographics?"
• "Monitor hubspot.com and tell me only the high-severity changes."
• "Run a baseline for deel.com (company name Deel), then check it next week for deltas."
• "Did anything change in the GTM signals for notion.so?"

Tool and inputs

get_company_changes:

• domain (string, required): company domain to monitor, without https or www, e.g. stripe.com.
• company_name (string, optional): company name hint, used when the domain does not match the brand name, e.g. Deel for deel.com.

The output is one row per company: company_domain, company_name, run_date, is_baseline, total_changes, has_high_severity, latest_change_date, a changes array of typed change events, a source_status object (ok / degraded / skipped per source), and a snapshot object carrying the current state for the next run's comparison. Each change event has event_type, severity, confidence, old_value, new_value, and the source_actor immutable Actor ID.

Funding signals are coming soon: the funding source ships as skipped until its sub-actor goes live, after which funding, exec move, product launch, and acquisition events appear automatically.

Full actor documentation

For the complete input and output reference, pricing, and run history, see the Company Change-Event Feed actor on the Apify Store:

https://apify.com/mambalabs/company-change-event-feed

---

Mamba Labs GTM Suite

This server is part of the Mamba Labs GTM Suite, a fleet of eleven specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor.

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs