Job Posting Liveness Checker MCP Server
Related Servers
Alternatives to Job Posting Liveness Checker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables searching live job postings pulled directly from 10 applicant-tracking-system APIs — including Greenhouse, Lever, Ashby, Workday, Personio, Recruitee, Teamtailor, Workable, SmartRecruiters and Breezy HR — using just a company website, domain or ATS handle, with filters for keywords, location, remote work and posting date. Also supports multi-company lookups, ATS detection, and stateless "only new since last call" monitoring for scheduled agents.MIT
- AlicenseNot gradedqualityCmaintenanceEnables job search and scraping across multiple job boards (LinkedIn, Indeed, Glassdoor, etc.) with advanced filtering, directly from Claude Desktop or other MCP clients.6MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to pull live job listings from major ATS platforms (Greenhouse, Lever, Ashby, Workable), Hacker News hiring threads, and detect hiring signals on company career pages.-
- AlicenseAqualityBmaintenanceEnables MCP clients to search live, normalized job postings across eight applicant-tracking platforms, auto-detect a company's ATS and board token, and list supported platforms through simple tool calls without API keys or accounts.5MIT
- 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.1112 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.1298 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purpose. The tool's scope (batch URL liveness check across five named ATS platforms) is clearly stated and self-contained.
A single descriptive snake_case verb_noun name (check_job_posting_liveness) is used, which is fully consistent and immediately readable. There is no competing convention to conflict with.
One tool for a narrowly scoped batch-checking service is defensible, but it feels thin—batch input of URLs is folded into a single call with no way to list supported ATSs, validate URLs, or retrieve history separately. The surface is minimal even for this focused purpose.
The tool covers the core lifecycle (live/closed status plus metadata like title, company, location, posted date, age, and last-seen-live) across five major ATS platforms in one call. Minor gaps exist—no discovery of supported platforms, no per-URL validation endpoint, and unclear handling of mixed supported/unsupported batches beyond the free-unsupported note.