hiringindex-mcp
Related Servers
Alternatives to hiringindex-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables users to search public job listings and retrieve details for individual postings from inside AI assistants, including ranked results, filters, and pagination. It is read-only and requires no account, authentication, or API key.MIT- AlicenseAqualityCmaintenanceEnables real-time job search across thousands of companies' open roles from Greenhouse, Lever, Ashby, and SmartRecruiters, with full-text filtering and company-specific queries, no API key required.2MIT
- AlicenseAqualityCmaintenanceEnables querying open job postings directly from company applicant-tracking systems (Greenhouse, Ashby, Lever), finding a company's job board, listing and comparing roles, and accessing salary data, all without scraping or API keys.3181 PyPI1MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search salary-transparent tech job postings across nine boards and eight countries, filter them by pay, remote work, tech stack, level, and language, and retrieve apply URLs or track applications. All commands are JSON-first, so duplicates and unfilterable criteria come back as data rather than errors.-
- 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
- AlicenseAqualityCmaintenanceEnables asking what companies are hiring right now by querying live job postings from their applicant-tracking system board APIs (Greenhouse, Lever, Ashby, Recruitee, Rippling, Personio), with filters, parsed location, remote flag, and structured salary.3MIT
TDQS
Scored across 4 tools
Each tool targets a distinct question: individual postings, aggregate market stats, single-post detail, and posting-age distribution. The overlap between search_jobs and job_market_insights is explicitly addressed in the descriptions, so an agent can reliably select the right tool.
Two tools use an imperative verb_noun pattern (search_jobs, get_job), while the other two use descriptive noun phrases (job_market_insights, posting_age_report). This is a minor convention split, but the names are still clear and the pattern is readable.
Four tools is well-scoped for a read-only job-market data server. Each tool covers a distinct and necessary operation without redundancy or bloat.
For the stated domain of job posting search and market analysis, the surface is complete: search, detail retrieval, aggregate insights, and posting-age reporting cover the core workflows. No obvious dead ends or missing lifecycle steps exist for this read-only domain.