com.headcountlabs/jobs

Est-ce que com.headcountlabs/jobs est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.headcountlabs/jobs » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 9 outils

• count_jobs≈ 2321 tokens

  Count the current jobs matching the filters, without listing them. This is the live count: it reads the job database as it is now, so use it for "how many jobs" and "which employers are hiring" questions, and prefer its numbers over market_lookup and market_breakdown, which read a daily snapshot. No account needed. 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 (metro works too), 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 were grouped, at most 1,000, taken in the default list order), groups_sampled (true when more jobs matched than were grouped, so the counts are from a sample) and groups_unknown_jobs (grouped jobs with no known value). 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. 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • filters · object · optionnel
  • group_by · string · optionnel · employer | company | work_arrangement | title | state | city | metro | country
    Break the matching jobs down by employer (company), work_arrangement, title, state, city (metro), country or employment_type.

  Exemple d'appel

  {"name": "count_jobs", "arguments": {"filters": {}, "group_by": "employer"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_job≈ 441 tokens

  Get a job by its job_id. No account needed. By default the answer has the same compact shape search_jobs returns (rank 1, job_id, job_ad, company_id, locations, work_arrangement, pay, posted_at, first_seen_at, posting_url, apply_url) with the whole description in job_ad.description, currentness, stale and last_checked_at (is it still open, and when was it last checked), and every linked posting in postings (status, last_fetched_at, application_check). Pass view: "full" for every field as the REST API returns it. Use fields to select top-level job properties; job_id is always included.

  Paramètres, retour & exemple (3)

  Paramètres

  • view · string · optionnel · compact | full
    compact (default): the same summary search_jobs returns, plus the whole description, whether the job is still open, when it was last checked, and the linked postings. full: every field of the job, as the REST API returns it.
  • fields · ? · optionnel
    Top-level job properties as a comma-separated string or field array; job_id is always included.
  • job_id · string · requis

  Exemple d'appel

  {"name": "get_job", "arguments": {"job_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_fields≈ 236 tokens

  Find the search_jobs filters and the job fields that match some keywords, with each one's type and a short description. Pass words such as ["pay", "remote"]; no keywords lists everything. kind is filter (pass it in search_jobs filters) or field (a property of each returned job; postings[].x is a property of each linked posting). A field state is an object whose state says whether the source published the value (known), Atlas derived it, the source omitted it, or extraction failed.

  Paramètres, retour & exemple (1)

  Paramètres

  • keywords · array · optionnel

  Exemple d'appel

  {"name": "list_fields", "arguments": {"keywords": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• market_breakdown≈ 634 tokens

  Rank the values of one dimension (by: title, state, metro, city, company, seniority, employment_type or remote) by jobs, pay or another figure, over all jobs or inside one filter, such as which states pay Software Engineers the most (by=state, title=Software Engineer, sort=pay_median). Answers come from a daily snapshot of open US jobs and give their as_of date; for current job counts or the employers hiring right now, count_jobs is the live source. Cells with fewer than 30 jobs are left out. No account needed.

  Paramètres, retour & exemple (10)

  Paramètres

  • by · string · optionnel
    breakdown only: what to rank (title, state, metro, city, company, seniority, employment_type or remote; place means state).
  • role · string · optionnel
    A standard job title such as "Registered Nurse" or "Software Engineer"; leave out for every job. Same as title.
  • sort · string · optionnel
    breakdown only: jobs (the default), pay_median, pay_p75, pay_p90, share_with_pay, remote_share, new_7_days or new_30_days.
  • limit · integer · optionnel
    breakdown rows or dimension values to return.
  • place · string · optionnel
    US (the default), a state code such as TX, a state name, a metro area such as "Austin-Round Rock-Georgetown, TX" or a city such as "Austin, TX" (cities and metros only for lookup, breakdown and negotiate).
  • title · string · optionnel
    A standard job title; lookup, breakdown and negotiate match more than 6,000 titles. Same as role.
  • remote · string · optionnel
    remote, hybrid or in_person (lookup and breakdown).
  • company · string · optionnel
    An employer name (lookup and breakdown).
  • seniority · string · optionnel
    intern, entry, senior, lead, manager, director or executive, read from the job title (lookup, breakdown, negotiate).
  • employment_type · string · optionnel
    full_time, part_time, contract, temporary, internship or per_diem (lookup and breakdown).

  Exemple d'appel

  {"name": "market_breakdown", "arguments": {"by": "texte", "role": "texte", "sort": "texte", "limit": 1, "place": "texte", "title": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• market_dimensions≈ 229 tokens

  List what market_lookup, market_breakdown and salary_range accept: the dimensions, how many values each has and the metrics; with dimension (and optionally q) the values of that dimension, such as the metro names. No account needed.

  Paramètres, retour & exemple (3)

  Paramètres

  • q · string · optionnel
    dimensions only: search the values of dimension.
  • limit · integer · optionnel
    breakdown rows or dimension values to return.
  • dimension · string · optionnel
    dimensions only: list the values of this dimension.

  Exemple d'appel

  {"name": "market_dimensions", "arguments": {"q": "texte", "limit": 1, "dimension": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• market_lookup≈ 561 tokens

  Job count, pay percentiles, share of jobs showing pay, remote/hybrid/in-person shares, posting age, new postings or top employers for up to two of title, place, company, seniority, employment_type and remote, such as the pay range for Registered Nurses in Texas. Leave metric out for every figure. Answers come from a daily snapshot of open US jobs and give their as_of date; for current job counts or the employers hiring right now, count_jobs is the live source. Cells with fewer than 30 jobs are left out. No account needed.

  Paramètres, retour & exemple (8)

  Paramètres

  • role · string · optionnel
    A standard job title such as "Registered Nurse" or "Software Engineer"; leave out for every job. Same as title.
  • place · string · optionnel
    US (the default), a state code such as TX, a state name, a metro area such as "Austin-Round Rock-Georgetown, TX" or a city such as "Austin, TX" (cities and metros only for lookup, breakdown and negotiate).
  • title · string · optionnel
    A standard job title; lookup, breakdown and negotiate match more than 6,000 titles. Same as role.
  • metric · string · optionnel
    lookup only: job_count, pay, pay_share, work_arrangement, posting_age, new_postings or top_employers; leave out for all of them.
  • remote · string · optionnel
    remote, hybrid or in_person (lookup and breakdown).
  • company · string · optionnel
    An employer name (lookup and breakdown).
  • seniority · string · optionnel
    intern, entry, senior, lead, manager, director or executive, read from the job title (lookup, breakdown, negotiate).
  • employment_type · string · optionnel
    full_time, part_time, contract, temporary, internship or per_diem (lookup and breakdown).

  Exemple d'appel

  {"name": "market_lookup", "arguments": {"role": "texte", "place": "texte", "title": "texte", "metric": "texte", "remote": "texte", "company": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• salary_range≈ 386 tokens

  What salary to ask for: for a title, a place (default US) and an optional seniority, the 25th, 50th, 75th and 90th percentile of posted pay, the sample size and a plain recommendation. Answers come from a daily snapshot of open US jobs and give their as_of date; for current job counts or the employers hiring right now, count_jobs is the live source. Cells with fewer than 30 jobs are left out. No account needed.

  Paramètres, retour & exemple (4)

  Paramètres

  • role · string · optionnel
    A standard job title such as "Registered Nurse" or "Software Engineer"; leave out for every job. Same as title.
  • place · string · optionnel
    US (the default), a state code such as TX, a state name, a metro area such as "Austin-Round Rock-Georgetown, TX" or a city such as "Austin, TX" (cities and metros only for lookup, breakdown and negotiate).
  • title · string · optionnel
    A standard job title; lookup, breakdown and negotiate match more than 6,000 titles. Same as role.
  • seniority · string · optionnel
    intern, entry, senior, lead, manager, director or executive, read from the job title (lookup, breakdown, negotiate).

  Exemple d'appel

  {"name": "salary_range", "arguments": {"role": "texte", "place": "texte", "title": "texte", "seniority": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_docs≈ 170 tokens

  Ask a question about Headcount Labs (filters, limits, MCP setup, errors) and get the best-matching sections of the headcountlabs.com docs, each with its URL. Works without an account.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • question · string · requis

  Exemple d'appel

  {"name": "search_docs", "arguments": {"question": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_jobs≈ 2688 tokens

  Search current job postings by keyword, title, company, place, pay, date and more. No account needed. Call list_fields to find the filter names. Country and employment_type accept comma-separated values or arrays and match any listed value. Pages return up to 50 jobs (limit, default 10), or up to 10 jobs when descriptions is "full"; a larger limit is refused. Pass next_cursor as cursor to see the next page. One search shows up to 250 jobs in total (the last page is shortened to fit), so narrow it with filters to find the right ones; count_jobs tells you how many jobs match without listing them. sort is relevance (best match) or updated (most recently updated). By default each job is a compact summary: rank, job_id, job_ad (the employer-written title, employer and a 200-character snippet of the description), company_id, locations, work_arrangement, pay (min, max, currency, period), posted_at, first_seen_at, posting_url and apply_url. For every field of each job pass view: "full" (descriptions cut to 400 characters, or descriptions: "full" for the whole text), name the top-level properties you need in fields (job_id is always included), or call get_job for one job. You choose how much description each job gets: descriptions: "snippet" (the default) gives a short preview and allows up to 50 jobs per page; descriptions: "full" gives the whole text but allows only 10 jobs per page. To read the full text of just a few jobs, search with snippets, then call get_job on the ones you want. Leave description out of fields to drop it entirely. For job titles, title matches the words as one phrase in that order, so "senior software engineer" misses "Software Engineer, Senior"; title_advanced matches words in any order with AND, OR and NOT, for example senior AND ("software engineer" OR "software developer"), and usually finds more.

  Paramètres, retour & exemple (7)

  Paramètres

  • sort · string · optionnel · relevance | updated
  • view · string · optionnel · compact | full
    compact (default): one short summary per job. full: every field of every job, as the REST API returns it.
  • limit · integer · optionnel
    Jobs per page, 1-50 (1-10 when descriptions is "full"). Default 10.
  • cursor · string · optionnel
    The next_cursor from the previous result, to see the next page.
  • fields · ? · optionnel
    Top-level job properties as a comma-separated string or field array; job_id is always included.
  • filters · object · optionnel
  • descriptions · string · optionnel · snippet | full
    snippet (default): a short preview of each description, up to 50 jobs per page. full: the whole text, up to 10 jobs per page.

  Exemple d'appel

  {"name": "search_jobs", "arguments": {"sort": "relevance", "view": "compact", "limit": 1, "cursor": "texte", "fields": "texte", "filters": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.headcountlabs.com/mcp/public