mcpField
M
mcp-company-change-event-feed

mcp-company-change-event-feed

Local
github.com/mambalabsdevBusiness & Marketing0Updated 1w ago

About mcp-company-change-event-feed

An MCP server that monitors company domains for changes in hiring, technology stack, funding, firmographics, and social presence. Built for RevOps teams, agencies, Clay users, and AI agents, it compares runs and returns typed change events rather than unchanged company data.

Key features

  1. 01Monitor five company signal categories
  2. 02Compare each run with a prior snapshot
  3. 03Return typed events with severity and confidence
  4. 04Select sources and minimum severity
  5. 05Check multiple company domains in batch

Use cases

  1. 01Track target-account changes between checks
  2. 02Surface only high-severity company signals
  3. 03Create a baseline before ongoing monitoring
  4. 04Monitor multiple domains in one run

MCP support

Exposes the `get_company_changes` tool to MCP clients and routes requests to an Apify actor. The tool returns change events and a snapshot that can serve as the next comparison baseline.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"com-mambabuilt-mcp-company-change-event-feed": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-company-change-event-feed"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}
Run commandnpx -y @mambalabsdev/mcp-company-change-event-feed
Environment variables to set
APIFY_TOKENSecretApify API token from https://console.apify.com/account/integrations

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@mambalabsdev/mcp-company-change-event-feed1.4.1

Tools

1

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
domainstringNoCompany domain to monitor, without https or www, e.g. stripe.com. Required unless domains is set.
domainsarrayNoBatch mode: several company domains in one run, one output row each. When set and non-empty it overrides domain. previous_snapshot is ignored in batch mode.
sourcesarrayNoWhich sources to monitor. Omit for all five, the historical behavior. A source you do not select is not run and not charged, so this is the largest lever on the cost of a call: five sub actor runs become one. An unselected source is reported not_selected in source_status, which is deliberately different from degraded.
company_namestringNoOptional company name hint, used when the domain does not match the brand name, e.g. Deel for deel.com.
min_severityenumNoReport only changes at or above this severity. low is everything and is the default. medium drops small noise such as follower count wobble. high keeps only funding, acquisitions, exec moves, CRM or sequencer changes and large hiring ramps, which is the setting for an alerting feed.low | medium | high
previous_snapshotobjectNoSnapshot 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 and keep a scheduled run cheap.
sub_actor_timeout_secsintegerNoPer-child run timeout in seconds, 5 to 300. Children run in parallel, so total wall time is about the slowest child. Lower it to keep a quick test run short. Default: 90.

Details

From the project README

Company Change-Event Feed MCP Server

Smithery Glama score MCP Registry npm version npm downloads license mcpservers.org

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's Inside

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 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.

EventPrice (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.

ActorImmutable Actor ID
GTM Hiring Signal ScraperD7O1SA2EqwHGsGr1P
GTM Tech Stack Signal Enrichmentqyd7nNyqFPelQViBx
GTM Signals AggregatorxKdRfnfFNkdMpFuNs
Job Board Keyword Signal Scanner4DvqpvhMR74NLcDDY
Domain to LinkedIn URL Resolver3HtnSaqPHOg1Qg5gx
ICP Fit ScorerW161DT8W4kW55dMFh
Domain Deliverability Checker0tVgxI7A6o9jMlxmc
Company Firmographic EnricherYlUtLWjfPpqykmB8g
Company Social Presence Mapper4k6CCemkgBDz18m2h
Company Identity Resolverlr8fTRAmZCBZmuwwh
Company Change-Event FeedoX44rS0fkEJ3rXLWe
Funding & Press Signal ScannerFS13X6dhQVgX3XOM6

Built by Mamba Labs | npm | Apify Store

License

MIT

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.