mcp-new-hire-finder
Related Servers
Alternatives to mcp-new-hire-finder
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.1110 npmMIT
- AlicenseAqualityBmaintenanceEnables checking CRM contacts to learn their current employer, title, start month, role history, and whether they left, landed elsewhere, or were promoted, returning one flat row per person with match method, source, and source age. It accepts single contacts or bulk lists, works with your own search, enrichment, and email-verification keys, and runs on Apify.1113 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables users to find companies hiring by role and geography, qualify them, and monitor them for hiring changes.MIT
- AlicenseAqualityAmaintenanceDetects hiring intent signals by scanning job boards for specific companies. Returns structured role data for outbound sales targeting.1116 npm1MIT
- AlicenseAqualityCmaintenanceEnables querying job boards for a company's open roles, pulling from Greenhouse, Workday, and an opt-in LinkedIn source and normalizing the results into one shape. It discovers boards, searches one or many companies at once, and returns full postings with title-based AI/ML and junior filtering.7MIT
- AlicenseNot gradedqualityAmaintenanceEnables users to discover applicant tracking system job boards from company domains, list open roles, detect hiring changes over time, and generate hiring summaries across multiple ATS platforms.MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection between overlapping tools. Its purpose (finding new hires at target companies) is stated unambiguously in both name and description.
The single tool uses a clear snake_case verb_noun pattern (find_new_hires) that would scale predictably if more tools were added. No competing conventions exist to create inconsistency.
A single tool is on the thin side for what is otherwise a parameter-rich, multi-source lookup service; splitting discovery (companies/people lookup by run ID, retry of a failed run, credit/error inspection) into separate tools would make the surface easier to consume.
The one tool covers the core end-to-end workflow (company input, lookback window, title matching, flat per-person output plus per-company summary), which is solid for a read-only search service. Minor gaps: failed runs return a run ID but there is no tool to re-fetch or inspect a prior run, and no way to validate/normalize company domains separately.