job-search-mcp
Related Servers
Alternatives to job-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search company job boards, filter roles by location, remote status, posting date, and H-1B sponsorship history, track applications through status changes, and check employers' USCIS sponsorship records.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search and filter thousands of tech job postings across nine boards and eight countries — including salary-transparent listings and Swiss and Singapore government portals — and to apply directly. It also tracks prior applications locally so already-applied roles are hidden from results.-
- AlicenseNot gradedqualityCmaintenanceEnables Claude to run a UK job-search pipeline end to end: fetching and de-duplicating postings from public Greenhouse/Lever/Ashby boards, checking visa-sponsor status and hard eligibility rules, then scoring and banding jobs against a rubric. Every model score must quote the job description, and the server verifies those quotes in code so fabricated evidence voids the dimension rather than counting.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search, filter, and apply across nine job boards in eight countries — including ~4,700 salary-transparent tech postings plus ~50,000 Swiss and ~9,000 Singapore IT listings — with salary, remote, tech, and date filters. It also tracks applications locally so already-applied jobs are returned as data rather than errors.-
- AlicenseAqualityBmaintenanceEnables agents to search and deduplicate UK job vacancies across multiple boards, match them against local CVs, and submit complete applications through an automated browser with persistent logins and application memory.29MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to sweep company job boards on Greenhouse, Lever and Ashby through their public APIs, filtering postings by title words and location while tracking which jobs have already been applied to.MIT
TDQS
Scored across 4 tools
Each tool addresses a clearly distinct aspect: sponsor verification, posting screening, application history, and job searching. No overlap in purpose and each has a specific trigger condition.
Three tools follow a verb_noun pattern (check_sponsor, screen_posting, search_roles), but application_history deviates as noun_noun. The naming is still descriptive and predictable, with only minor inconsistency.
Four tools is well-scoped for a focused job-search assistant, covering the core workflow without bloat. Each tool contributes a distinct function and none seem redundant.
The surface covers search, screening, sponsor checks, and local history, which addresses the primary workflow. A minor gap is the lack of a tool to update or add to the application ledger, but this may be handled externally.