Job Change Tracker MCP Server
Related Servers
Alternatives to Job Change Tracker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables an AI client to track a watch list of contacts and retrieve only what changed since the last run — departures, new employers, replacements, and new hires after a role closed — each row carrying match evidence, source dates, and ready-to-use outreach payloads. It runs the analysis on Apify using the caller's own provider keys, supports stored or caller-held state, and can push results to a signed webhook.1242 npmMIT
- AlicenseAqualityAmaintenanceClassifies job titles into department and seniority using deterministic rules, and optionally verifies if a person is listed on their employer's website via the Mamba Labs Contact Classifier Apify actor.1258 npmMIT
- AlicenseAqualityAmaintenanceExtracts people (names and titles) from a company's team, leadership, or about page given a domain. Uses Apify to crawl and return structured data, with optional filters for seniority and email inclusion.1217 npmMIT

Ask Xverumofficial
AlicenseNot gradedqualityAmaintenanceFind and enrich the right people from 750M professional profiles. Search by role, seniority, skills, industry, and location in plain English. Pull profiles with work history, education, and seniority, then see who's likely to change jobs next with Next Move Signal. Built for AI products and agents: sourcing candidates, building lead lists, and mapping markets and accounts.28 npmMIT- AlicenseAqualityBmaintenanceEnables users to track a list of company domains and retrieve only the job-board changes since the previous run, including new, closed, and reposted postings with full descriptions, stable posting keys, and 30-day hiring velocity per company. It runs on Apify and exposes this through a single tool call.1226 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs People Finder & Email Verifier actor on Apify. Give it a company domain, name or LinkedIn URL and it returns the people at that company who match your role, seniority and department filters, each as a structured contact record with an optional verified business email.1241 npmMIT
TDQS
Scored across 1 tool
There is only a single tool, so there is no possibility of misselection or overlapping purpose. Its scope (batch job-change verification for contacts) is clearly stated.
The lone tool follows a clean verb_noun snake_case pattern (track_job_change). With one tool there is no convention mixing to penalize.
A single tool is defensible for a narrow, one-shot enrichment service that accepts a list of people, but it is thin: there is no companion tool for retrieving async run results, checking credits, or inspecting history.
The core verification operation is covered and returns rich per-person output, but the surface has a dead end: failures return a run ID with no tool to fetch results by that ID, and there is no way to query past runs or validate configuration/keys separately.