mcp-job-board-keyword-signal-scanner
Related Servers
Alternatives to mcp-job-board-keyword-signal-scanner
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceDetects hiring intent signals by scanning job boards for specific companies. Returns structured role data for outbound sales targeting.1107 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables live reads of public job boards across Greenhouse, Lever, Ashby, Personio, Pinpoint, and Gem, including fetching boards, resolving companies, checking whether jobs remain open, and retrieving full job details. Supports location- and role-based searches of verified starter boards plus paid multi-company search and monitoring with history, new/closed, and repost signals.MIT
- FlicenseNot gradedqualityDmaintenanceTransforms job postings into qualified sales leads by searching for active jobs, enriching company data, and identifying decision-maker contact information.-
- 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 gradedqualityBmaintenanceEnables 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
- AlicenseAqualityAmaintenanceEnables monitoring of job postings by keyword, returning companies currently advertising those roles enriched with firmographics and LinkedIn URLs via Apify.177 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purpose. Its scope (scanning a company's job board for keyword matches across several ATS platforms) is stated clearly and unambiguously.
The single name 'scan_job_board_keywords' follows a clear verb_noun pattern in snake_case, which is readable and idiomatic. With only one tool there is no pattern to verify across the set, so it cannot be judged fully consistent.
A single tool is thin for a server, even though this one is substantive and well-scoped rather than trivial. Common adjacent needs (multi-company scans, listing supported boards, output shaping) would naturally live here, making one tool feel minimal.
The core read-only scanning operation is covered, including category selection and custom keywords, but there are notable gaps: no batch/multi-company scanning, no way to discover supported boards or categories programmatically, and no output configuration. Agents can still accomplish the primary task, but only one company per call and with fixed output.