Skip to content
MCP server

Headcount Labs

By headcountlabsAll Headcount Labs servers

Job-postings data API: 8M listings from 1,200+ job boards

Listed on

First seen 15 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

3
Directories
1 via MCP Toplist
9
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
0
GitHub stars
From MCP Toplist

Tools

ToolDescriptionBehaviour
count_jobsCount matching jobs without listing them. This is the live count; prefer it over market_lookup and market_breakdown for "how many" and "which employers are hiring". A count by title_advanced with no company, company_id or job_id is an estimate (count_is_estimate is true); if it is refused as too slow, add one of those three filters or count by title. count_jobs refuses these combinations unless company, company_id or job_id is also set: near together with title, title_advanced or q (use city with state instead; that counts fast); source, exclude_source, source_type, has_location, last_fetch_since, last_fetch_until or application_check_since together with title, title_advanced or q; has_description in any count. A refusal is invalid_request and is not temporary: change the filters as its message says instead of retrying the same call. Counting by description alone returns an estimate: count_is_estimate is true and count_margin gives the 95% range. search_jobs pages carry the same number as total when the filters are fast to count. Every error has code, message, retryable (true or false) and next_step; retryable errors also have retry_after_seconds. A call that runs past 25 seconds is stopped with query_too_broad: narrow it, do not repeat it. To answer "which companies are hiring for X" or "how are these jobs split by ...", pass group_by: employer (company works too), work_arrangement (remote, hybrid or in_person), title, state (US), city, country or employment_type. The answer then also has group_by, groups (the top 25 values by number of matching jobs, each with value and jobs), groups_from_jobs (how many matching jobs the breakdown is based on), groups_sampled (true when this is not an exact count of every match) and groups_unknown_jobs (jobs with no known value). The breakdown is exact up to 3,000 matching jobs, estimate from a random sample above. Either way the top 25 values are returned. Above 3,000, groups_are_estimates is true, groups_note states the sample size in plain words, and each jobs number is scaled from that random sample of matching jobs (picked by job id, which is random) up to the total, not a raw sample count. If the breakdown times out, the count is still returned with no groups and groups_note says the breakdown timed out. A job with several locations or postings can count under more than one value. group_by employer keeps its own keys: employers (each with employer_name, company_id and jobs), employers_from_jobs, employers_sampled and employers_unknown_jobs, and when the breakdown is an estimate, employers_are_estimates and employers_note. When a filter is too broad to count exactly in time, count is an estimate: the answer then has count_is_estimate: true, count_margin (the 95% range either side of count) and count_note.Read-only
get_jobGet a job by job_id. Default shape matches search_jobs, plus the full description, currentness, stale, last_checked_at, and linked postings. Pass view: "full" for every REST field, or fields to pick top-level properties (job_id is always included). One whole reply (every text part and structuredContent together) stays under about 50,000 characters. Each job lists its first 10 locations; locations_total and locations_truncated: true say when there are more. A search page that would not fit gets fewer jobs, with page_note saying so; next_cursor continues at the first job not shown, so no job is skipped and only jobs shown are counted. Only one job too big on its own is shortened (description_truncated; truncated.how_to_get_rest says where the rest is).Read-only
list_fieldsFind search_jobs filters and job fields matching keywords, with type and a short description. Pass words such as ["pay", "remote"]; no keywords lists everything. kind is filter, option (sort, a search_jobs argument beside filters) or field (postings[].x is a posting property). A field state object says whether the source published the value (known), Atlas derived it, the source omitted it, or extraction failed.Read-only
market_breakdownRank one dimension (by: title, state, city, company, seniority, employment_type or remote) by jobs, pay or another figure, optionally inside a filter. Daily snapshot (see as_of). For live counts or who is hiring now, use count_jobs. Cells with fewer than 30 jobs are omitted. No account needed.Read-only
market_dimensionsList dimensions and metrics for market_lookup, market_breakdown and salary_range; pass dimension (and optional q) to list that dimension's values. No account needed.Read-only
market_lookupLook up job count, pay, pay share, work arrangement, posting age, new postings or top employers for up to two of title, place, company, seniority, employment_type and remote. Omit metric for every figure. Daily snapshot (see as_of). For live counts or who is hiring now, use count_jobs. Cells with fewer than 30 jobs are omitted. No account needed.Read-only
salary_rangePosted pay percentiles (25/50/75/90) for a title, place (default US) and optional seniority, with sample size and a short recommendation. Daily snapshot (see as_of). For live counts or who is hiring now, use count_jobs. Cells with fewer than 30 jobs are omitted. No account needed.Read-only
search_docsSearch Headcount Labs docs (filters, limits, MCP setup, errors) and return matching sections with URLs. Works without an account.Read-only
search_jobsSearch current job postings by keyword, title, company, place, pay and date. Call list_fields for filter names. Country and employment_type accept comma-separated values or arrays. Pages return up to 50 jobs (limit, default 10), or 10 when descriptions is "full" (default 8, about as many whole descriptions as fit in one reply). Pass next_cursor as cursor for the next page. One search shows up to 250 jobs; narrow filters or use count_jobs for how many match. Default results are compact summaries (employer, title, locations, pay, dates, urls, snippet). Pass view: "full", fields, or get_job for more. descriptions: "snippet" (default) previews text; "full" returns whole descriptions. title matches one phrase in order. title_advanced and description_advanced are Boolean: an operator between every two words or groups, for example title_advanced: "(engineer OR developer) AND NOT manager" (write AND NOT, never a bare NOT after a word; keep at least one word that is not negated). sort: relevance needs q, title or description; with only title_advanced or description_advanced use updated. Each page also has total (how many jobs match, the same number count_jobs gives) and total_is_estimate (true when total is an estimate; total_margin is then the 95% range either side). total is null, with total_note saying why, when the filters are slow to count (description, description_advanced, title_advanced or q without company, near or source filters) or the count did not finish within the time the page took; then call count_jobs. One whole reply (every text part and structuredContent together) stays under about 50,000 characters. Each job lists its first 10 locations; locations_total and locations_truncated: true say when there are more. A search page that would not fit gets fewer jobs, with page_note saying so; next_cursor continues at the first job not shown, so no job is skipped and only jobs shown are counted. Only one job too big on its own is shortened (description_truncated; truncated.how_to_get_rest says where the rest is). Every error has code, message, retryable (true or false) and next_step; retryable errors also have retry_after_seconds. A call that runs past 25 seconds is stopped with query_too_broad: narrow it, do not repeat it.Read-only

Directory listings

DirectoryListingTierFirst seen
ClaudeHeadcount Labscommunity20 Oct 2026
Official MCP RegistryHeadcount Labs-15 Oct 2026
GlamaListed there according to MCP Toplist’s dataset; not collected by InvokeRank.
Headcount Labs MCP server | InvokeRank