Mcp Job Change Tracker

com.mambabuilt由 mambabuilt.com 发布v1.0.2更新于 Nov 7, 2026

Track contact job changes: current employer, start month, role history, and left or landed status.

已验证STDIO仅桌面网页搜索与抓取商业与电商

概览

AI 生成的概览

核查 CRM 联系人是否仍在记录中的公司任职，返回现雇主、职位、履历以及离职、跳槽或晋升状态。

可以做什么
  • 按记录中的公司核查单个联系人或一批联系人，并做同名排查
  • 每人返回一行扁平 JSON：现雇主、职位、入职月份、履历、状态与匹配方式
  • 说明每条答案的来源及来源的新旧程度，可选附公司官网与新闻佐证
  • 支持传入自有履历、搜索、信息补全与邮箱验证密钥，并提供缓存与单次费用上限
适用场景
适合在对外联系或清理名单前，维护 CRM 或联系人列表并想了解哪些人换了工作、去了哪里或是否获得晋升的场景。
运行要求
通过 npx 在本地运行，需要 Node.js 18 或更高版本。调用需要 Apify 账号和 APIFY_TOKEN。可选的第三方密钥（Serper 或 SerpApi、Prospeo、BounceBan）作为工具输入传入。需要能访问 Apify 的网络。
安装前请注意
每次调用都会消耗计入 Apify 账号的额度，按每人读取和每次运行启动计费；可用 max_charge_usd 限制单次花费。可选的第三方密钥作为运行输入发送，并由 Apify 以机密输入形式保存。姓名、邮箱、个人主页链接等联系人信息会发送给 Apify 及其服务商。工具为只读，但本身不抓取 LinkedIn。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Mcp Job Change Tracker，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Job Change Tracker MCP Server

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

[Job Change Tracker MCP server]

An MCP server for the Mamba Labs CRM Contact Job Change Checker actor on Apify. Send the contacts in your CRM. Get one row back per person: where they work now, their title, when they started, their role history, and whether they left the company you know them at, landed somewhere new, or moved up inside the same company. Every row says how the person was matched, which source the answer came from, and how old that source is.

What's Inside

What it does

Check whether one contact, or a list of contacts, still works at the company your records hold. Returns one flat, Clay-ready JSON row per person: current employer, title, start month, role history, status (left, landed, promoted, or still there), how the person was matched, the source of the answer, and that source's date, with a namesake check. Runs on data you send (known_history) and on your own Serper or SerpApi, Prospeo, and BounceBan keys passed as inputs; this tool never fetches LinkedIn and holds no key of its own. Provide person_name with company_domain or company_name, or a people list. A run that does not succeed is returned as an error with its run ID. Read-only; 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-job-change-tracker": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-job-change-tracker"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The track_job_change tool appears.

Prerequisites

Example prompts

  • "Check whether Jane Doe still works at example.com and where she went if she left."
  • "Run these 20 contacts and tell me who changed jobs in the last 6 months."

Tool

track_job_change. One tool. Example arguments:

json
{  "person_name": "Jane Doe",  "company_domain": "example.com",  "company_name": "Example Inc"}

Inputs

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

InputTypeRequiredDescription
person_namestringnoFull name of the person to check.
company_domainstringnoWebsite domain of the company your records place this person at, for example microsoft.com. Left, landed, and promoted are worked out against this company.
company_namestringnoName of that company. Used with or instead of the domain to match roles in the person's history.
last_known_titlestringnoThe title your records hold. Echoed on the row as input_title.
profile_urlstringnoOptional. The person's LinkedIn profile URL, used as the identity. This actor never opens it. Without it, the run looks the profile up with your search key and charges profile_resolved when it finds and accepts one.
emailstringnoOptional. The person's work address at the last known company. With a BounceBan key, an undeliverable answer marks the person as left.
company_linkedin_urlstringnoOptional. The strongest company match when a role history carries LinkedIn company URLs.
locationstringnoOptional. Echoed for your records.
input_idstringnoOptional. Returned unchanged on the row so you can join it back to your CRM or table.
known_historystringnoOptional. A role history you already have, as JSON: {"source": "heyreach", "source_date": "2026-10-07", "experiences": [...]} or {"source": "crm", "roles": [{"company_name", "title", "start_month", "end_month"}]}. Read before any paid key; a history newer than Max source age skips Prospeo.
peoplearraynoMany people at once. Each item takes the same keys as the single person fields: person_name, company_domain, company_name, last_known_title, profile_url, email, company_linkedin_url, location, input_id, and known_history (an object).
serperApiKeystringnoOptional. Web search (serper.dev): finds profile URLs and reads the search result line for the current role. About 1 to 3 searches per person. Your own key, sent as a run input; never stored by the actor.
serpApiKeystringnoOptional. Used for web search only when no Serper key is set. Your own key, sent as a run input; never stored by the actor.
prospeoApiKeystringnoOptional. Prospeo enrich-person: the person's role history with start and end months. Skipped when you send a fresh history of your own. Your own key, sent as a run input; never stored by the actor.
bouncebanApiKeystringnoOptional. Verifies the old work address only while the person still reads as at the company. Only an undeliverable answer is used. Your own key, sent as a run input; never stored by the actor.
maxSourceAgeDaysstringnoA history you send that is older than this is treated as lagging, so the run also reads Prospeo and the search result. Default 30.
checkCompanySitestringnoFree. Looks for the person on up to 4 team and about pages of the last known company domain.
checkNewsstringnoFree. Cites up to 3 headlines from the last year that name the person with a move word. Evidence only; a headline never sets the employer.
verifyOldEmailstringnoWith a BounceBan key: one check per person who still reads as at the company. Uses the address you send, or one Prospeo returns on the company domain.
includeRoleHistorystringnoNo keeps role_count and drops the role_history array.
cacheTtlDaysstringnoReuse a reading made in the last N days, uncharged, from a store in your own Apify account. 0 turns it off. Rows with your own history are never cached. Default 7.
maxPeoplestringnoStop after this many people. Default 1000.
max_charge_usdstringnoOptional. The run stops before any row that would take its event charges past this amount.

Pricing

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

EventFree planBronzeSilverGold
person_read, per person read$0.025$0.02375$0.0225$0.02125
profile_resolved, per profile resolved by web search$0.006$0.0057$0.0054$0.0051
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/job-change-tracker

License

MIT. See LICENSE.

来源：README.md，提交 7714b7d

工具

1

track_job_change

Track job change

Check whether one contact, or a list of contacts, still works at the company your records hold. Returns one flat, Clay-ready JSON row per person: current employer, title, start month, role history, status (left, landed, promoted, or still there), how the person was matched, the source of the answer, and that source's date, with a namesake check. Runs on data you send (known_history) and on your own Serper or SerpApi, Prospeo, and BounceBan keys passed as inputs; this tool never fetches LinkedIn and holds no key of its own. Provide person_name with company_domain or company_name, or a people list. A run that does not succeed is returned as an error with its run ID. Reads public data and writes nothing; requires an APIFY_TOKEN and consumes Apify credits per call.

输入参数emailpeopleinput_idlocationcheckNewsmaxPeopleserpApiKeyperson_nameprofile_urlcacheTtlDayscompany_nameserperApiKey另有 11 个

版本历史

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 分