LabscoMCP early access ↗
mambalabsdevMCP SERVER

Company Change-Event Feed

Monitor a company domain and get back only what changed since last time — hiring, tech stack, funding, firmographics and social, as typed events.

by mambalabsdev ↗Company Registries & Business Intelligence DataCommunity

LABSCO SUMMARY

Baselines first, deltas after — and the first run tells you nothing.

That is by design, not a bug: run it once per target to establish the snapshot, then again later for the changes. Plan the first pass accordingly. The two knobs that matter are both cost knobs disguised as filters — picking sources means the ones you skipped are never run, and raising the severity floor cuts the noise a weekly check would otherwise produce. The per-source status object is the part that keeps it honest: a source that failed reads as degraded rather than as no changes.

What it is

A one-tool MCP server for account monitoring. The first run on a domain records a clean baseline and reports no changes; every run after that diffs against the stored snapshot and returns only the deltas. That framing is the point — you get change events, not another full enrichment record to compare by hand.

What you get

  • A company domain monitored across hiring, tech stack, funding, firmographics and social, returning typed change events since the last run — get_company_changes
  • Each change event carrying an event_type, a severity, a confidence, an old_value, a new_value, and the immutable Actor ID of the source that produced it
  • Severity filtering that is also a cost control: low returns everything, medium drops small noise, high narrows to funding, acquisitions, exec moves, CRM changes and large hiring ramps
  • Source selection that is the largest lever on cost — a source you do not choose is not run and not charged
  • Flat, one-row-per-company JSON built for Clay: company_domain, company_name, run_date, is_baseline, total_changes, has_high_severity, latest_change_date, plus a source_status object reporting ok, degraded, skipped or not-selected per source
  • A snapshot object carrying the current state forward, which is what makes the next run a diff
  • A company_name hint for the cases where the domain does not match the brand

Requirements

An Apify account with an API token, passed as APIFY_TOKEN — the work runs as an Apify actor and this package is a thin client that routes the call and hands back the result, so the cost model is Apify's. Node.js 18 or newer. Launch with npx -y @mambalabsdev/mcp-company-change-event-feed; the package is @mambalabsdev/mcp-company-change-event-feed (1.2.0) over stdio. One gap to plan around: the funding source ships as skipped until its sub-actor goes live, after which funding, exec move, product launch and acquisition events appear automatically.

Setup effort

One command plus a key — npx -y @mambalabsdev/mcp-company-change-event-feed, then supply credentials

See installation options