Mcp Job Change Tracker

com.mambabuiltPublished by mambabuilt.comv1.0.2Updated Nov 7, 2026

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

VerifiedSTDIODesktop onlyWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Checks whether CRM contacts still work at the company you have on file, returning current employer, title, role history and left/landed/promoted status.

What you can do
  • Check one contact or a list of contacts against the company your records hold, with namesake checks
  • Return one flat JSON row per person: current employer, title, start month, role history, status and match method
  • Report the source of each answer and how old that source is, plus optional company-site and news evidence
  • Accept your own role history, search, enrichment and email-verification keys as run inputs, with caching and a per-run charge cap
When to use it
Useful when you maintain a CRM or contact list and want to know which people have changed jobs, where they went, or whether they were promoted, before outreach or list cleanup.
Requirements
Runs locally via npx, so Node.js 18 or newer is needed. An Apify account and an APIFY_TOKEN are required for calls. Optional provider keys (Serper or SerpApi, Prospeo, BounceBan) are passed as tool inputs. Network access to Apify is required.
Before you install
Each call consumes Apify credits billed to your Apify account, with per-person and per-run-start event charges; max_charge_usd can cap a run. Optional third-party keys are sent as run inputs and stored by Apify as secret inputs. Contact details such as names, emails and profile URLs are sent to Apify and its providers. Read-only, but it does not fetch LinkedIn itself.

Installation

In SourceWeft

  1. Open Mcp Job Change Tracker in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit 7714b7d

Tools

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.

Parametersemailpeopleinput_idlocationcheckNewsmaxPeopleserpApiKeyperson_nameprofile_urlcacheTtlDayscompany_nameserperApiKey+11 more

Version history

3
  1. v1.0.2LatestNov 5, 2026
  2. v1.0.1Oct 16, 2026
  3. v1.0.0Oct 14, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts