com.mambabuilt/mcp-job-change-tracker
NPM · @MAMBALABSDEV/MCP-JOB-CHANGE-TRACKER
Track contact job changes: current employer, start month, role history, and left or landed status.
Available components
Last scanned (13 hours ago)
Scores higher than 38% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1063 tokens (~1063/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 0
- Package version: 1.0.0 → 1.0.1 functional
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 1.0.0 → 1.0.1 functional
- 15 Oct 26 +28
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Analysed npm/@mambalabsdev/mcp-job-change-tracker@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
track_job_change Track job change ~1,063
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bouncebanApiKey | string | – | 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. |
| cacheTtlDays | string | – | Reuse 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. |
| checkCompanySite | string | – | Free. Looks for the person on up to 4 team and about pages of the last known company domain. |
| checkNews | string | – | 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. |
| company_domain | string | – | 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_linkedin_url | string | – | Optional. The strongest company match when a role history carries LinkedIn company URLs. |
| company_name | string | – | Name of that company. Used with or instead of the domain to match roles in the person's history. |
| string | – | Optional. The person's work address at the last known company. With a BounceBan key, an undeliverable answer marks the person as left. | |
| includeRoleHistory | string | – | No keeps role_count and drops the role_history array. |
| input_id | string | – | Optional. Returned unchanged on the row so you can join it back to your CRM or table. |
| known_history | string | – | 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", "… |
| last_known_title | string | – | The title your records hold. Echoed on the row as input_title. |
| location | string | – | Optional. Echoed for your records. |
| maxPeople | string | – | Stop after this many people. Default 1000. |
| maxSourceAgeDays | string | – | 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. |
| max_charge_usd | string | – | Optional. The run stops before any row that would take its event charges past this amount. |
| people | array | – | 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_… |
| person_name | string | – | Full name of the person to check. |
| profile_url | string | – | 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… |
| prospeoApiKey | string | – | 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. |
| serpApiKey | string | – | 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. |
| serperApiKey | string | – | 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 a… |
| verifyOldEmail | string | – | 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. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-job-change-tracker server?
com.mambabuilt/mcp-job-change-tracker runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-job-change-tracker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-job-change-tracker
claude mcp add com-mambabuilt-mcp-job-change-tracker -- npx -y @mambalabsdev/mcp-job-change-tracker
What is the com.mambabuilt/mcp-job-change-tracker server?
com.mambabuilt/mcp-job-change-tracker is listed in the public MCP registry as com.mambabuilt/mcp-job-change-tracker. Track contact job changes: current employer, start month, role history, and left or landed status. This page covers its npm package (@mambalabsdev/mcp-job-change-tracker).
Is the com.mambabuilt/mcp-job-change-tracker server safe to use?
com.mambabuilt/mcp-job-change-tracker scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-job-change-tracker server expose?
com.mambabuilt/mcp-job-change-tracker exposes 1 tool: track_job_change. Their descriptions and schemas cost roughly 1,063 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-job-change-tracker server still maintained?
com.mambabuilt/mcp-job-change-tracker is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-job-change-tracker server under?
com.mambabuilt/mcp-job-change-tracker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.