company-change-event-feed
by mambalabsdev
README.md
# Company Change-Event Feed MCP Server
[](https://smithery.ai/servers/mambabuilt/mcp-company-change-event-feed) [](https://glama.ai/mcp/servers/mambalabsdev/mcp-company-change-event-feed) [](https://registry.modelcontextprotocol.io/v0/servers?search=com.mambabuilt/mcp-company-change-event-feed&limit=1) [](https://www.npmjs.com/package/@mambalabsdev/mcp-company-change-event-feed) [](https://www.npmjs.com/package/@mambalabsdev/mcp-company-change-event-feed) [](https://github.com/mambalabsdev/mcp-company-change-event-feed/blob/main/LICENSE) [](https://mcpservers.org/servers/mambalabsdev/mcp-company-change-event-feed)
<a href="https://mcprush.com/to/company-change-event-feed-mcp?ref=badge"><img width="380" height="200" src="https://mcprush.com/badge/company-change-event-feed-mcp/card.svg" alt="Company Change Event Feed MCP server" /></a>
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's Inside
- [What it does](#what-it-does)
- [Quick start](#quick-start)
- [Prerequisites](#prerequisites)
- [Example prompts](#example-prompts)
- [Tool and inputs](#tool-and-inputs)
- [Full actor documentation](#full-actor-documentation)
- [Mamba Labs GTM Suite](#mamba-labs-gtm-suite)
- [License](#license)
## 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:
```json
{
"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 unless `domains` is set): company domain to monitor, without https or www, e.g. stripe.com.
- `domains` (array, optional): batch mode, several company domains in one run with one output row each. When set and non-empty it overrides `domain`.
- `company_name` (string, optional): company name hint, used when the domain does not match the brand name, e.g. Deel for deel.com.
- `sources` (array, optional): which sources to monitor: `hiring`, `tech_stack`, `firmographic`, `funding`, `social`. Omit for all five. A source you do not select is not run and not charged, so this is the largest lever on cost.
- `min_severity` (string, optional): `low` (default, everything), `medium` (drops small noise), `high` (funding, acquisitions, exec moves, CRM changes and large hiring ramps only).
- `previous_snapshot` (object, optional): the `snapshot` object returned by a prior run. Supply it and it is used as the baseline instead of the stored snapshot, so you can hold delta state outside Apify. Ignored in batch mode.
- `sub_actor_timeout_secs` (integer, optional): per source run timeout in seconds, 5 to 300, default 300. The sources run in parallel, so total wall time is about the slowest source. Lower it to keep a quick test short.
- `max_charge_usd` (optional): a cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit it to rely on the maximum cost per run set in Apify.
`sources` and `sub_actor_timeout_secs` are the two controls on how long and how much a call costs: each selected source is one sub actor run.
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` / `not_selected` 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.
The funding source runs the Funding and Press Signal Scanner, so funding, exec move, product launch, and acquisition events are reported like any other source.
The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. The run is allowed 1,800 seconds. If it is still going two minutes after that, the call stops waiting and returns the run ID with a link to it in the Apify Console, where the results land when it finishes. A run that does not succeed comes back as an error with its run ID and status.
## Pricing
Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.
| Event | Price (USD) |
| --- | --- |
| Actor Start (`apify-actor-start`) | 0.00005 |
| result (`apify-default-dataset-item`) | 0.01 |
| change source resolved (`change-source-resolved`) | 0.01 |
## 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 58 MCP servers for go-to-market data, each backed by a dedicated Apify actor. The table lists the actors the suite started with; every server is listed at https://mambabuilt.com.
| Actor | Immutable Actor ID |
|---|---|
| [GTM Hiring Signal Scraper](https://console.apify.com/actors/D7O1SA2EqwHGsGr1P) | `D7O1SA2EqwHGsGr1P` |
| [GTM Tech Stack Signal Enrichment](https://console.apify.com/actors/qyd7nNyqFPelQViBx) | `qyd7nNyqFPelQViBx` |
| [GTM Signals Aggregator](https://console.apify.com/actors/xKdRfnfFNkdMpFuNs) | `xKdRfnfFNkdMpFuNs` |
| [Job Board Keyword Signal Scanner](https://console.apify.com/actors/4DvqpvhMR74NLcDDY) | `4DvqpvhMR74NLcDDY` |
| [Domain to LinkedIn URL Resolver](https://console.apify.com/actors/3HtnSaqPHOg1Qg5gx) | `3HtnSaqPHOg1Qg5gx` |
| [ICP Fit Scorer](https://console.apify.com/actors/W161DT8W4kW55dMFh) | `W161DT8W4kW55dMFh` |
| [Domain Deliverability Checker](https://console.apify.com/actors/0tVgxI7A6o9jMlxmc) | `0tVgxI7A6o9jMlxmc` |
| [Company Firmographic Enricher](https://console.apify.com/actors/YlUtLWjfPpqykmB8g) | `YlUtLWjfPpqykmB8g` |
| [Company Social Presence Mapper](https://console.apify.com/actors/4k6CCemkgBDz18m2h) | `4k6CCemkgBDz18m2h` |
| [Company Identity Resolver](https://console.apify.com/actors/lr8fTRAmZCBZmuwwh) | `lr8fTRAmZCBZmuwwh` |
| [Company Change-Event Feed](https://console.apify.com/actors/oX44rS0fkEJ3rXLWe) | `oX44rS0fkEJ3rXLWe` |
| [Funding & Press Signal Scanner](https://console.apify.com/actors/FS13X6dhQVgX3XOM6) | `FS13X6dhQVgX3XOM6` |
> Built by [Mamba Labs](https://github.com/mambalabsdev) | [npm](https://www.npmjs.com/org/mambalabsdev) | [Apify Store](https://apify.com/mambalabs)
## License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
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