com.mambabuilt/mcp-career-change-signal-engine
NPM · @MAMBALABSDEV/MCP-CAREER-CHANGE-SIGNAL-ENGINE
Watch your contacts and get back only job changes: leavers, landings, replacements, new hires.
Available components
Last scanned (9 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 Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 881 tokens (~881/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.
- 17 Oct 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 16 Oct 26 −10
- Known CVEs: pass → unverified ▼ security
- 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
- Dependency health: 0.85 → 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 Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good 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-career-change-signal-engine@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 →
watch_career_changes Watch career changes ~881
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 people (required) and, optionally, replies, bounces, posting changes, suppression, and your own provider keys in providerKeys; it never fetches LinkedIn and holds no key of its own. State is kept per watch_list_id. A run that does not succeed is returned as an error with its run ID. Requires an APIFY_TOKEN and consumes Apify credits per call.
| Name | Type | Req | Description |
|---|---|---|---|
| bounces | array | – | Optional bounces: work_email, bounce_type, smtp_code, smtp_text, bounced_at. |
| concurrency | integer | – | People read at once. |
| features | object | – | Switches: replacement, closed_posting, contact_data, first_line, icp, include_promotions. Defaults on except include_promotions. |
| first_run_mode | string | – | report: the first run returns every change it finds. baseline: the first run stores state and returns nothing, charging only contact_checked. |
| icp_tiers | object | – | Optional map of company domain to tier, shown on landed rows. Never blocks a row. |
| linkedin_reader_dataset_id | string | – | Optional: the dataset id of a Proofed LinkedIn reader run on the same Apify account. Rows join to people by profile URL. |
| max_people_per_run | integer | – | A list longer than this fails the run before any read or charge. Default 150, at most 1,000. |
| max_replacement_candidates | integer | – | Candidates proposed per leaver. A person confirms each. |
| max_spend_usd | integer | – | Stops the run before a charge that would cross it. |
| 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_i… |
| posting_changes | array | – | Optional Account Hiring Watch rows. A closed posting starts a new hire search at that company. |
| providerKeys | object | – | 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… |
| read_mode | string | – | stored_first: your known_history first, then your keys. live_only: ignore known_history. stored_only: only known_history, no key calls. |
| replies | array | – | 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. |
| sender_context | string | – | Optional topic phrase for the first line draft, for example: content production at scale. |
| state_source | string | – | actor: the engine keeps state between runs in a named store. caller: you send last_reading per person and keep state yourself. |
| suppression | object | – | emails, profile_urls, opted_out_emails, opted_out_profile_urls, company_domains, company_names. Suppressed people are dropped before the read and cost nothing. |
| sweep_interval_days | integer | – | With state_source actor, a person read within this many days is skipped. |
| watch_list_id | string | – | Names the list. State is kept per watch list id when state_source is actor. |
| webhook_secret | string | – | Signing secret; a whsec_ value is base64 decoded. Your own key, sent as a run input; never stored by the actor. |
| webhook_url | string | – | Optional: signed Standard Webhooks POST of up to 100 signal rows per request. |
No output schema declared.
No examples provided.
How do I install the com.mambabuilt/mcp-career-change-signal-engine server?
com.mambabuilt/mcp-career-change-signal-engine runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-career-change-signal-engine. 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-career-change-signal-engine
claude mcp add com-mambabuilt-mcp-career-change-signal-engine -- npx -y @mambalabsdev/mcp-career-change-signal-engine
What is the com.mambabuilt/mcp-career-change-signal-engine server?
com.mambabuilt/mcp-career-change-signal-engine is listed in the public MCP registry as com.mambabuilt/mcp-career-change-signal-engine. Watch your contacts and get back only job changes: leavers, landings, replacements, new hires. This page covers its npm package (@mambalabsdev/mcp-career-change-signal-engine).
Is the com.mambabuilt/mcp-career-change-signal-engine server safe to use?
com.mambabuilt/mcp-career-change-signal-engine 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-career-change-signal-engine server expose?
com.mambabuilt/mcp-career-change-signal-engine exposes 1 tool: watch_career_changes. Their descriptions and schemas cost roughly 881 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-career-change-signal-engine server still maintained?
com.mambabuilt/mcp-career-change-signal-engine 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-career-change-signal-engine server under?
com.mambabuilt/mcp-career-change-signal-engine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.