Name: Job Change Tracker
Author: Mamba Labs

Job Change Tracker MCP

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

Grade A Local · stdio API key 1 tool v1.0.0

No reviews yet by Mamba Labsnpm Runs on your machine, nothing hosted

96/100

trust score

tool declared

local

runs on your machine

—

downloads a day

What it does

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

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio job-change-tracker-mcp '--' npx -y @mambalabsdev/mcp-job-change-tracker

# 2 — ask your agent for something these tools do
#   track_job_change

It needs APIFY_TOKEN: this reads it from your environment, so export it first.

Job Change Tracker costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publisher

Mamba Labs57 servers

7 categories · publishing since 2026

All 57 servers

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Job Change Tracker as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.

Claude Codedeclared by this listing

This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads APIFY_TOKEN (Apify API token from https://console.apify.com/account/integrations) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx APIFY_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.

claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio job-change-tracker-mcp '--' npx -y @mambalabsdev/mcp-job-change-tracker

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: APIFY_TOKEN — Apify API token from https://console.apify.com/account/integrations. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.

What you approve

1 tool, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

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…

Parameter	Type	Required	Notes
person_name	string	no	Full name of the person to check.
company_domain	string	no	Website 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_name	string	no	Name of that company. Used with or instead of the domain to match roles in the person's history.
last_known_title	string	no	The title your records hold. Echoed on the row as input_title.
profile_url	string	no	Optional. 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 a
email	string	no	Optional. The person's work address at the last known company. With a BounceBan key, an undeliverable answer marks the person as left.
company_linkedin_url	string	no	Optional. The strongest company match when a role history carries LinkedIn company URLs.
location	string	no	Optional. Echoed for your records.
input_id	string	no	Optional. Returned unchanged on the row so you can join it back to your CRM or table.
known_history	string	no	Optional. 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", "e
people	array	no	Many 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_i
serperApiKey	string	no	Optional. 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 ac
serpApiKey	string	no	Optional. Used for web search only when no Serper key is set. Your own key, sent as a run input; never stored by the actor.
prospeoApiKey	string	no	Optional. 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.
bouncebanApiKey	string	no	Optional. 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.
maxSourceAgeDays	string	no	A history you send that is older than this is treated as lagging, so the run also reads Prospeo and the search result. Default 30.
checkCompanySite	string	no	Free. Looks for the person on up to 4 team and about pages of the last known company domain.
checkNews	string	no	Free. 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.
verifyOldEmail	string	no	With 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.
includeRoleHistory	string	no	No keeps role_count and drops the role_history array.

Free

$0 forever

Every tool, no call limit
No card, and mcprush charges nothing for it
Source published under MIT
Runs on your machine — nothing of it reaches our gateway
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Job Change Tracker or to call it, at any volume.

ATrust score 96 / 100

Release 1.0.0 · scanned 15 Oct 2026

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score96

Findings1 threat · 3 capability

Capabilitymoderate

Coveragesource

Verificationrepo

Surface digest93f44ba426485f3b3e3e0f14dc2e34d3ffcf08b0cbff745c6597f720858d6ae4

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	moderate	capability blast radius (moderate) — client exposure if the model is manipulated	−3
verification-discount	repo	publisher verification (public source) — no provenance, but the source is public and inspectable	−1
coverage-honesty	source	inspection depth (source) — how much of the target the scan could see	−0

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

Tool surfaceread

Implementation sourceread

Package metadataread

Live transportnot available

Tools were statically extracted from the published source (1 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.

Tool	Capability tags	Why the tag was assigned
track_job_change	untrusted-inputexternal-sink	untrusted-input: declares openWorldHint: true (interacts with entities outside the server); external-sink: handler sends an HTTP POST (fetch(https://api.apify.com/v2/acts/${actorPath}/runs?timeout=${ACTOR_RUN_TIMEOUT_SECS}) at build/index.js:80

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digest93f44ba426485f3b

Scanned2026-10-15

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.