Name: Career Change Signal Engine
Author: Mamba Labs

Career Change Signal Engine MCP

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

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

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

93/100

trust score

tool declared

local

runs on your machine

—

downloads a day

What it does

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

Quickstart

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

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

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

Career Change Signal Engine 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 Career Change Signal Engine 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 career-change-signal-engine-mcp '--' npx -y @mambalabsdev/mcp-career-change-signal-engine

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

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…

Parameter	Type	Required	Notes
people	array	yes	Your 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
watch_list_id	string	no	Names the list. State is kept per watch list id when state_source is actor.
state_source	string	no	actor: the engine keeps state between runs in a named store. caller: you send last_reading per person and keep state yourself.
read_mode	string	no	stored_first: your known_history first, then your keys. live_only: ignore known_history. stored_only: only known_history, no key calls.
first_run_mode	string	no	report: the first run returns every change it finds. baseline: the first run stores state and returns nothing, charging only contact_checked.
max_people_per_run	integer	no	A list longer than this fails the run before any read or charge. Default 150, at most 1,000.
providerKeys	object	no	Your 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 t
linkedin_reader_dataset_id	string	no	Optional: the dataset id of a Proofed LinkedIn reader run on the same Apify account. Rows join to people by profile URL.
replies	array	no	Optional 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.
bounces	array	no	Optional bounces: work_email, bounce_type, smtp_code, smtp_text, bounced_at.
posting_changes	array	no	Optional Account Hiring Watch rows. A closed posting starts a new hire search at that company.
suppression	object	no	emails, profile_urls, opted_out_emails, opted_out_profile_urls, company_domains, company_names. Suppressed people are dropped before the read and cost nothing.
icp_tiers	object	no	Optional map of company domain to tier, shown on landed rows. Never blocks a row.
features	object	no	Switches: replacement, closed_posting, contact_data, first_line, icp, include_promotions. Defaults on except include_promotions.
sender_context	string	no	Optional topic phrase for the first line draft, for example: content production at scale.
max_replacement_candidates	integer	no	Candidates proposed per leaver. A person confirms each.
max_spend_usd	integer	no	Stops the run before a charge that would cross it.
sweep_interval_days	integer	no	With state_source actor, a person read within this many days is skipped.
concurrency	integer	no	People read at once.
webhook_url	string	no	Optional: signed Standard Webhooks POST of up to 100 signal rows per request.

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 Career Change Signal Engine or to call it, at any volume.

ATrust score 93 / 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 score93

Findings1 threat · 3 capability

Capabilityhigh

Coveragesource

Verificationrepo

Surface digestf3b4e7c16a0c784535457fd6c1e88370515c97ab6cb0c2bc12f8e64c17da66d1

Score vectorthreat 100 → client 93

Term	Level	What it prices	Points
capability-exposure	high	capability blast radius (high) — client exposure if the model is manipulated	−6
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. high is the level these add up to.

Tool	Capability tags	Why the tag was assigned
watch_career_changes	external-sinksensitive-source	external-sink: parameter "webhook", declares readOnlyHint: false, openWorldHint: true, handler sends an HTTP POST (fetch(https://api.apify.com/v2/acts/${actorPath}/runs?timeout=${ACTOR_RUN_TIMEOUT_SECS}) at build/index.js:80; sensitive-source: parameter "secret"

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

Tool "watch_career_changes" both reads sensitive data and can send it externally.

Supply chain and provenance

Integrityfirst-seen

Surface digestf3b4e7c16a0c7845

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.