Mcp Career Change Signal Engine

com.mambabuilt由 mambabuilt.com 發布v1.0.2更新於 Nov 7, 2026

Watch your contacts and get back only job changes: leavers, landings, replacements, new hires.

已驗證STDIO僅桌面資料與分析商業與電商

概覽

AI 產生的概覽

針對 Apify actor 的輕量 MCP 用戶端，監控聯絡人名單並只回傳職務異動：離職、去向、接替者與新到任。

可以做什麼
  • 執行聯絡人觀察名單，只回傳自上次執行以來的變化：誰離職、去了哪裡、誰接替、職缺關閉後誰新到任
  • 每列附上比對依據、來源日期、區隔標籤、開場白草稿，以及 Slack、HubSpot、HeyReach、Instantly 承載資料
  • 可控制狀態保存方式、讀取模式、首次執行基準或報告、花費上限、掃描間隔與並行數
  • 可選擇傳入回覆、退信、職缺變化、封鎖名單、ICP 分層及自有服務商金鑰
  • 可選擇將每次最多 100 筆訊號列推送到帶簽章的 webhook
適用情境
適合業務、招募或合作團隊定期追蹤老客戶、潛在客戶或交易聯絡人名單，只取得職務異動摘要而不必重新讀取全部資料。也適合把異動推送到 CRM 或外聯工具的工作流程。
執行需求
透過 npx 在本機執行，需要 Node.js 18 或更新版本、Apify 帳號以及 APIFY_TOKEN 環境變數。呼叫會消耗 Apify 額度。可選的服務商金鑰（serper 或 serpapi、prospeo、bounceban、findymail、exa）與 webhook 密鑰以執行輸入傳入。
安裝前請注意
呼叫依事件計費並計入你的 Apify 帳號（聯絡人檢查、訊號交付、執行啟動），費用隨名單規模增加，可設定花費上限。APIFY_TOKEN、服務商金鑰與 webhook 密鑰會傳送給 Apify，服務商金鑰以秘密輸入形式儲存。聯絡人資料、回覆與退信會傳送給第三方服務商及你設定的 webhook 網址；回覆文字僅保留雜湊。結果包含外聯文案草稿，寄送前請先審閱。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Mcp Career Change Signal Engine，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Career Change Signal Engine MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Career Change Signal Engine MCP server]

An MCP server for the Mamba Labs Career Change Signal Engine actor on Apify. Career Change Signal Engine reads the people on your watch list and returns only what changed since you last checked: who left, who landed where, who replaced them, and who started after a role closed. Every row says how the person was matched, which source answered, and how old that source is.

What's Inside

What it does

Read a watch list of contacts and return only what changed since the last run: who left, who landed where, who replaced them, and who started after a role closed. Each row carries evidence, a source date, a segment, a first line draft, and Slack, HubSpot, HeyReach, and Instantly payloads. Pass people (required) and, optionally, replies, bounces, posting changes, suppression, and your own provider keys in providerKeys; it never fetches LinkedIn and holds no key of its own. State is kept per watch_list_id. A run that does not succeed is returned as an error with its run ID. Requires an APIFY_TOKEN and consumes Apify credits per call.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

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

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-career-change-signal-engine": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-career-change-signal-engine"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The watch_career_changes tool appears.

Prerequisites

Example prompts

  • "Check my 50 past champions and tell me who left and where they landed."
  • "Run my watch list and draft a first line for each person who changed jobs."

Tool

watch_career_changes. One tool. Example arguments:

json
{  "people": [    {      "person_name": "Jane Doe",      "company_domain": "example.com",      "company_name": "Example Inc",      "title": "Head of Content",      "external_id": "example-1"    }  ],  "watch_list_id": "default"}

Inputs

Every buyer facing input of the live actor, unchanged. Omitted inputs take the actor's own defaults.

InputTypeRequiredDescription
peoplearrayyesYour watch list, one object per person: person_name, profile_url (optional), company_domain, company_name, title, work_email, relationship (prospect, mgl, deal_contact, customer_champion), external_id, crm_id, deal_id, known_history (a HeyReach copy, a Proofed LinkedIn reader row, or generic roles), last_reading (with state_source caller). The engine reads only these people. At most max_people_per_run per run.
watch_list_idstringnoNames the list. State is kept per watch list id when state_source is actor.
state_sourcestringnoactor: the engine keeps state between runs in a named store. caller: you send last_reading per person and keep state yourself.
read_modestringnostored_first: your known_history first, then your keys. live_only: ignore known_history. stored_only: only known_history, no key calls.
first_run_modestringnoreport: the first run returns every change it finds. baseline: the first run stores state and returns nothing, charging only contact_checked.
max_people_per_runintegernoA list longer than this fails the run before any read or charge. Default 150, at most 1,000.
providerKeysobjectnoYour own keys: serper or serpapi (web search), prospeo, bounceban (verifier), findymail, exa. Never written to state, output, logs, or the webhook. Your own key, sent as a run input; never stored by the actor.
linkedin_reader_dataset_idstringnoOptional: the dataset id of a Proofed LinkedIn reader run on the same Apify account. Rows join to people by profile URL.
repliesarraynoOptional reply texts: external_id or work_email or profile_url, text, received_at, channel, is_auto_reply. Text is classified and dropped; only its sha1 is kept.
bouncesarraynoOptional bounces: work_email, bounce_type, smtp_code, smtp_text, bounced_at.
posting_changesarraynoOptional Account Hiring Watch rows. A closed posting starts a new hire search at that company.
suppressionobjectnoemails, profile_urls, opted_out_emails, opted_out_profile_urls, company_domains, company_names. Suppressed people are dropped before the read and cost nothing.
icp_tiersobjectnoOptional map of company domain to tier, shown on landed rows. Never blocks a row.
featuresobjectnoSwitches: replacement, closed_posting, contact_data, first_line, icp, include_promotions. Defaults on except include_promotions.
sender_contextstringnoOptional topic phrase for the first line draft, for example: content production at scale.
max_replacement_candidatesintegernoCandidates proposed per leaver. A person confirms each.
max_spend_usdintegernoStops the run before a charge that would cross it.
sweep_interval_daysintegernoWith state_source actor, a person read within this many days is skipped.
concurrencyintegernoPeople read at once.
webhook_urlstringnoOptional: signed Standard Webhooks POST of up to 100 signal rows per request.
webhook_secretstringnoSigning secret; a whsec_ value is base64 decoded. Your own key, sent as a run input; never stored by the actor.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
contact_checked, per contact checked$0.02$0.019$0.018$0.017
signal_delivered, per change row delivered$0.068$0.0646$0.0612$0.0578
apify-actor-start, per run start$0.001$0.001$0.001$0.001

Your keys

The actor holds no provider key of its own. Every paid provider key is yours, passed as an input and stored by Apify as a secret input. Without a key, the actor skips that step and says so in the run.

Full actor documentation

apify.com/mambalabs/career-change-signal-engine

License

MIT. See LICENSE.

來源：README.md，提交 5ab2873

工具

1

watch_career_changes

Watch career changes

Read a watch list of contacts and return only what changed since the last run: who left, who landed where, who replaced them, and who started after a role closed. Each row carries evidence, a source date, a segment, a first line draft, and Slack, HubSpot, HeyReach, and Instantly payloads. Pass people (required) and, optionally, replies, bounces, posting changes, suppression, and your own provider keys in providerKeys; it never fetches LinkedIn and holds no key of its own. State is kept per watch_list_id. A run that does not succeed is returned as an error with its run ID. Requires an APIFY_TOKEN and consumes Apify credits per call.

輸入參數people必填bouncesrepliesfeaturesicp_tiersread_modeconcurrencysuppressionwebhook_urlproviderKeysstate_sourcemax_spend_usd另有 9 個

版本歷史

3
  1. v1.0.2最新Nov 5, 2026
  2. v1.0.1Oct 16, 2026
  3. v1.0.0Oct 14, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分