protogrid

Search / com.whatjobs.mcp/job-search

WhatJobs Job Search

R0· no sign-in

Search live WhatJobs jobs, salaries and hiring companies in 58 countries from AI assistants.

v2.3.0 · active · repository · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality81good
Trust96of 100
Uptime, 30 days100%
Latency p50348 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "job-search": {
      "type": "http",
      "url": "https://mcp.whatjobs.com/mcp"
    }
  }
}
claude mcp add --transport http job-search https://mcp.whatjobs.com/mcp
[mcp_servers.job-search]
url = "https://mcp.whatjobs.com/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "job-search": {
      "type": "remote",
      "url": "https://mcp.whatjobs.com/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "job-search": {
      "type": "http",
      "url": "https://mcp.whatjobs.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=job-search&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLndoYXRqb2JzLmNvbS9tY3AifQ%3D%3D"
}
{
  "servers": {
    "job-search": {
      "type": "http",
      "url": "https://mcp.whatjobs.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "job-search": {
      "httpUrl": "https://mcp.whatjobs.com/mcp"
    }
  }
}
extensions:
  "job-search":
    enabled: true
    name: "job-search"
    type: streamable_http
    uri: "https://mcp.whatjobs.com/mcp"
    timeout: 300

Quality 81 / 100good

protocol100 · weight 25
  • pass
    protocol.modernsupports 2026-07-28 (server/discover)
  • pass
    protocol.statelessanswers without a session
  • pass
    protocol.transportstreamable HTTP
  • pass
    protocol.list_ttltool list is cacheable (ttlMs 300000)
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene81 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length7 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations8 of 8 tools declare readOnlyHint or destructiveHint
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: search_jobs (idempotentHint); get_salary_insights (idempotentHint); get_top_hiring_companies (idempotentHint); …
  • pass
    tools.token_costabout 4,020 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
  • pass
    tools.hidden_textno hidden text in tool names, descriptions, schemas or annotations
stability50 · weight 15
  • warn
    stability.changes11 tool changes in 30 days
  • fail
    stability.rug_pull3 tools kept their name but changed most of their description in 30 days; review before trusting them
  • pass
    stability.new_linksno tool change named a new site
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

8 tools, about 4,020 tokens to load them all · tool set b78e2b1ebd1a · tools last changed 2026-11-09 · checked 2026-11-14 07:03 UTC

Tool changes

  • match_jobs_to_profilechangeddescription
    before

    Find WhatJobs listings that fit a person's background: searches up to 4 target job titles at once and ranks the jobs by how well the title matches and how many of their skills each listing mentions. Use this when the user shares their CV, experience or skills and asks what jobs suit them, e.g. "Here's my CV, what should I apply for in Manchester?". Inputs: - job_titles: 1-4 job titles that fit the person (you choose them from what they shared). - skills: up to 10 key skills or tools (e.g. "Python", "SQL", "forklift licence"). - location: where they want to work (the place to search). - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Pass only titles and skills. Never pass CV text, names, contact details or other personal data. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

    after · 99% of words in common

    Find WhatJobs listings that fit a person's background: searches up to 4 target job titles at once and ranks the jobs by how well the title matches and how many of their skills each listing mentions. Use this when the user shares their CV, experience or skills and asks what jobs suit them, e.g. "Here's my CV, what should I apply for in Manchester?". Inputs: - job_titles: 1-4 job titles that fit the person (you choose them from what they shared). - skills: up to 10 key skills or tools (e.g. "Python", "SQL", "forklift licence"). - location: where they want to work (the place to search). For remote work use "Remote", alone or with a place. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Pass only titles and skills. Never pass CV text, names, contact details or other personal data. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

  • search_latest_jobschangeddescription
    before

    Show only recently posted WhatJobs listings for a role and place, newest first. Use this when the user asks for new, fresh, recent or today's jobs, e.g. "Any electrician jobs posted today in Manchester?" or "New marketing jobs this week in Madrid". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - posted_within_days: 1 for today/yesterday, 7 for this week (default), up to 30. - more_keywords: optional. Other roles to search in the same call when the user asks about several. - more_locations: optional. Other places to search in the same call when the user asks about several. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. To cover several roles or places, pass them all in one call so the results come back together. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

    after · 96% of words in common

    Show only recently posted WhatJobs listings for a role and place, newest first. Use this when the user asks for new, fresh, recent or today's jobs, e.g. "Any electrician jobs posted today in Manchester?" or "New marketing jobs this week in Madrid". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - posted_within_days: 1 for today/yesterday, 7 for this week (default), up to 30. - For remote work, put "Remote" in location, alone or with a place; only listings that say they are remote come back. - more_keywords: optional. Other roles to search in the same call when the user asks about several. - more_locations: optional. Other places to search in the same call when the user asks about several. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. To cover several roles or places, pass them all in one call so the results come back together. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

  • search_jobschangeddescription
    before

    Search live WhatJobs job listings by role and place. Use this when the user wants to find jobs, vacancies, internships or other work, or asks to see more results from a job search. Inputs: - keyword: the role, job function, skill or industry only. Leave out the place and filler words such as jobs, vacancies, roles, hiring, in, near, around, at or within. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. It can also be a remote preference. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France), dk (Denmark), eg (Egypt), id (Indonesia), my (Malaysia), om (Oman), ph (Philippines), qa (Qatar), sa (Saudi Arabia), sg (Singapore), tz (Tanzania), ug (Uganda), fi (Finland), gr (Greece), gt (Guatemala), hk (Hong Kong), ie (Ireland), it (Italy), kw (Kuwait), lt (Lithuania), lu (Luxembourg), ma (Morocco), no (Norway), nz (New Zealand), pa (Panama), pe (Peru), pl (Poland), pr (Puerto Rico), pt (Portugal), ru (Russia), se (Sweden), th (Thailand), tr (Turkey), ve (Venezuela), bd (Bangladesh), bo (Bolivia), cn (China), cz (Czech Republic), gh (Ghana), ke (Kenya), hu (Hungary), jp (Japan), kr (South Korea), lk (Sri Lanka), mg (Madagascar), py (Paraguay), ro (Romania), sn (Senegal), sv (El Salvador), tn (Tunisia), ua (Ukraine), uy (Uruguay), vn (Vietnam). - chunk_number: the result batch. Use 1 for a new search and add 1 each time the user asks for more. - more_keywords: optional. Other roles to search in the same call when the user asks about several. - more_locations: optional. Other places to search in the same call when the user asks about several. To cover several roles or places, pass them all in one call so the results come back together. Examples: - sales in Bracknell -> keyword="sales", location="Bracknell", market="uk" - software engineer jobs near Manchester -> keyword="software engineer", location="Manchester", market="uk" - nurse jobs in Berlin -> keyword="nurse", location="Berlin", market="de" - comptable à Paris -> keyword="comptable", location="Paris", market="fr" - accountant jobs in Dubai -> keyword="accountant", location="Dubai, United Arab Emirates", market="ae" - developer jobs in Singapore -> keyword="developer", location="Singapore", market="sg" - nurse or carer jobs in Leeds and York -> keyword="nurse", location="Leeds", more_keywords=["carer"], more_locations=["York"], market="uk" Returns up to 10 listings per batch (up to 20 across several roles or places), each with title, company, location, salary when the listing states one, posted date, summary and apply link, plus paging details. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

    after · 98% of words in common

    Search live WhatJobs job listings by role and place. Use this when the user wants to find jobs, vacancies, internships or other work, or asks to see more results from a job search. Inputs: - keyword: the role, job function, skill or industry only. Leave out the place and filler words such as jobs, vacancies, roles, hiring, in, near, around, at or within. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. For remote work use "Remote", alone or with a place such as "California remote"; only listings that say they are remote come back. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France), dk (Denmark), eg (Egypt), id (Indonesia), my (Malaysia), om (Oman), ph (Philippines), qa (Qatar), sa (Saudi Arabia), sg (Singapore), tz (Tanzania), ug (Uganda), fi (Finland), gr (Greece), gt (Guatemala), hk (Hong Kong), ie (Ireland), it (Italy), kw (Kuwait), lt (Lithuania), lu (Luxembourg), ma (Morocco), no (Norway), nz (New Zealand), pa (Panama), pe (Peru), pl (Poland), pr (Puerto Rico), pt (Portugal), ru (Russia), se (Sweden), th (Thailand), tr (Turkey), ve (Venezuela), bd (Bangladesh), bo (Bolivia), cn (China), cz (Czech Republic), gh (Ghana), ke (Kenya), hu (Hungary), jp (Japan), kr (South Korea), lk (Sri Lanka), mg (Madagascar), py (Paraguay), ro (Romania), sn (Senegal), sv (El Salvador), tn (Tunisia), ua (Ukraine), uy (Uruguay), vn (Vietnam). - chunk_number: the result batch. Use 1 for a new search and add 1 each time the user asks for more. - more_keywords: optional. Other roles to search in the same call when the user asks about several. - more_locations: optional. Other places to search in the same call when the user asks about several. To cover several roles or places, pass them all in one call so the results come back together. Examples: - sales in Bracknell -> keyword="sales", location="Bracknell", market="uk" - software engineer jobs near Manchester -> keyword="software engineer", location="Manchester", market="uk" - nurse jobs in Berlin -> keyword="nurse", location="Berlin", market="de" - comptable à Paris -> keyword="comptable", location="Paris", market="fr" - accountant jobs in Dubai -> keyword="accountant", location="Dubai, United Arab Emirates", market="ae" - developer jobs in Singapore -> keyword="developer", location="Singapore", market="sg" - nurse or carer jobs in Leeds and York -> keyword="nurse", location="Leeds", more_keywords=["carer"], more_locations=["York"], market="uk" Returns up to 10 listings per batch (up to 20 across several roles or places), each with title, company, location, salary when the listing states one, posted date, summary and apply link, plus paging details. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

  • report_view_statusadded

    Records whether the WhatJobs results view finished loading, so loading problems can be found. Called by the results view itself, not by the assistant. Inputs: status (loaded or failed), kind (the type of result shown) and query (the search that result shows).

  • match_jobs_to_profilechangeddescription
    before

    Find WhatJobs listings that fit a person's background: searches up to 4 target job titles at once and ranks the jobs by how well the title matches and how many of their skills each listing mentions. Use this when the user shares their CV, experience or skills and asks what jobs suit them, e.g. "Here's my CV, what should I apply for in Manchester?". Inputs: - job_titles: 1-4 job titles that fit the person (you choose them from what they shared). - skills: up to 10 key skills or tools (e.g. "Python", "SQL", "forklift licence"). - location: where they want to work (the place to search). - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). Pass only titles and skills. Never pass CV text, names, contact details or other personal data. The result includes a link to all matching jobs on WhatJobs.

    after · 56% of words in common

    Find WhatJobs listings that fit a person's background: searches up to 4 target job titles at once and ranks the jobs by how well the title matches and how many of their skills each listing mentions. Use this when the user shares their CV, experience or skills and asks what jobs suit them, e.g. "Here's my CV, what should I apply for in Manchester?". Inputs: - job_titles: 1-4 job titles that fit the person (you choose them from what they shared). - skills: up to 10 key skills or tools (e.g. "Python", "SQL", "forklift licence"). - location: where they want to work (the place to search). - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Pass only titles and skills. Never pass CV text, names, contact details or other personal data. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

  • search_latest_jobschangeddescription, input schemameaning changed
    before

    Show only recently posted WhatJobs listings for a role and place, newest first. Use this when the user asks for new, fresh, recent or today's jobs, e.g. "Any electrician jobs posted today in Manchester?" or "New marketing jobs this week in Madrid". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - posted_within_days: 1 for today/yesterday, 7 for this week (default), up to 30. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). The result includes a link to all matching jobs on WhatJobs.

    after · 47% of words in common

    Show only recently posted WhatJobs listings for a role and place, newest first. Use this when the user asks for new, fresh, recent or today's jobs, e.g. "Any electrician jobs posted today in Manchester?" or "New marketing jobs this week in Madrid". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - posted_within_days: 1 for today/yesterday, 7 for this week (default), up to 30. - more_keywords: optional. Other roles to search in the same call when the user asks about several. - more_locations: optional. Other places to search in the same call when the user asks about several. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. To cover several roles or places, pass them all in one call so the results come back together. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

  • compare_job_countschangeddescriptionmeaning changed
    before

    Compare how many jobs are live on WhatJobs right now across places and/or roles. Use this when the user asks where the most jobs are, how much demand there is, or to compare cities or roles, e.g. "Where are the most data analyst jobs in Germany?", "More jobs for nurses or carers in Leeds?", "Paris vs Berlin for developers". Inputs: - keywords: one or more job roles (may be [""] to count all jobs). - locations: one or more places to search, not the user's own location unless they ask about jobs near them. Up to 6 keyword x location combinations are compared. - market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Each row includes a link to that search on WhatJobs.

    after · 46% of words in common

    Compare how many jobs are live on WhatJobs right now across places and/or roles. Use this when the user asks where the most jobs are, how much demand there is, or to compare cities or roles, e.g. "Where are the most data analyst jobs in Germany?", "More jobs for nurses or carers in Leeds?", "Paris vs Berlin for developers". Inputs: - keywords: one or more job roles (may be [""] to count all jobs). - locations: one or more places to search, not the user's own location unless they ask about jobs near them. Up to 6 keyword x location combinations are compared. - market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Each row includes a link to that search on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

  • get_top_hiring_companieschangeddescription
    before

    List the companies posting the most jobs for a role and place right now on WhatJobs, with their job counts and example listings. Use this when the user asks who is hiring, which companies or employers have openings, or the biggest employers for a role, e.g. "Who's hiring software engineers in Berlin?". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). Counts come from the latest 50 listings. The result includes links to each company's listings and to all matching jobs on WhatJobs.

    after · 51% of words in common

    List the companies posting the most jobs for a role and place right now on WhatJobs, with their job counts and example listings. Use this when the user asks who is hiring, which companies or employers have openings, or the biggest employers for a role, e.g. "Who's hiring software engineers in Berlin?". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Counts come from the latest 50 listings. The result includes links to each company's listings and to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

  • compare_salarieschangeddescription
    before

    Compare what a job pays across places, or what different jobs pay in one place, from the salaries in current WhatJobs listings: the typical range and median for each, side by side. Use this when the user wants pay compared, e.g. "Nurse salary in London vs Manchester", "Do developers earn more in Berlin or Munich?", "Which pays more in Toronto, accountant or bookkeeper?". Inputs: - keywords: one or more job roles only (e.g. ["nurse"], or ["accountant", "bookkeeper"]). - locations: one or more places to compare (city, region or country), not the user's own location unless they ask about jobs near them. - market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). Up to 4 role x place combinations are compared. Each row is in that country's own currency (amounts are not converted between currencies) and says its pay period (per year in most countries). Each row links to that search on WhatJobs.

    after · 57% of words in common

    Compare what a job pays across places, or what different jobs pay in one place, from the salaries in current WhatJobs listings: the typical range and median for each, side by side. Use this when the user wants pay compared, e.g. "Nurse salary in London vs Manchester", "Do developers earn more in Berlin or Munich?", "Which pays more in Toronto, accountant or bookkeeper?". Inputs: - keywords: one or more job roles only (e.g. ["nurse"], or ["accountant", "bookkeeper"]). - locations: one or more places to compare (city, region or country), not the user's own location unless they ask about jobs near them. - market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Up to 4 role x place combinations are compared. Each row is in that country's own currency (amounts are not converted between currencies) and says its pay period (per year in most countries). Each row links to that search on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

  • get_salary_insightschangeddescription
    before

    Show what a job pays, from the salaries in current WhatJobs listings: typical range, median, lowest and highest, plus a few listings with salaries. Use this when the user asks how much a role pays or earns, salary ranges, or whether a salary is good, e.g. "How much does a nurse earn in Paris?" or "Data analyst salary in London". Inputs: - keyword: the job role only (e.g. "nurse", "software engineer"). - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. May be empty for the whole country. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). Figures are in the country's own currency, for the pay period most listings use (per year in most countries, per month in some); the result says which. The result includes a link to all matching jobs on WhatJobs.

    after · 55% of words in common

    Show what a job pays, from the salaries in current WhatJobs listings: typical range, median, lowest and highest, plus a few listings with salaries. Use this when the user asks how much a role pays or earns, salary ranges, or whether a salary is good, e.g. "How much does a nurse earn in Paris?" or "Data analyst salary in London". Inputs: - keyword: the job role only (e.g. "nurse", "software engineer"). - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. May be empty for the whole country. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Figures are in the country's own currency, for the pay period most listings use (per year in most countries, per month in some); the result says which. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 96 / 100

provenance85
liveness100
freshness100
hygiene100

+repository +dns-namespace +website +reachable +uptime-100% +updated-5d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://mcp.whatjobs.com/mcp streamable-httpnoneyes100%348 ms2026-07-282026-11-14

Tools (8)

compare_job_countsread-onlyCompare how many jobs are live on WhatJobs right now across places and/or roles. Use this when the user asks where the most jobs are, how much demand there is, or to compare cities or roles, e.g. "Where are the most data analyst jobs in Germany?", "More jobs for nurses or carers in Leeds?", "Paris vs Berlin for developers". Inputs: - keywords: one or more job roles (may be [""] to count all jobs). - locations: one or more places to search, not the user's own location unless they ask about jobs near them. Up to 6 keyword x location combinations are compared. - market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Each row includes a link to that search on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.
compare_salariesread-onlyCompare what a job pays across places, or what different jobs pay in one place, from the salaries in current WhatJobs listings: the typical range and median for each, side by side. Use this when the user wants pay compared, e.g. "Nurse salary in London vs Manchester", "Do developers earn more in Berlin or Munich?", "Which pays more in Toronto, accountant or bookkeeper?". Inputs: - keywords: one or more job roles only (e.g. ["nurse"], or ["accountant", "bookkeeper"]). - locations: one or more places to compare (city, region or country), not the user's own location unless they ask about jobs near them. - market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Up to 4 role x place combinations are compared. Each row is in that country's own currency (amounts are not converted between currencies) and says its pay period (per year in most countries). Each row links to that search on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.
get_salary_insightsread-onlyShow what a job pays, from the salaries in current WhatJobs listings: typical range, median, lowest and highest, plus a few listings with salaries. Use this when the user asks how much a role pays or earns, salary ranges, or whether a salary is good, e.g. "How much does a nurse earn in Paris?" or "Data analyst salary in London". Inputs: - keyword: the job role only (e.g. "nurse", "software engineer"). - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. May be empty for the whole country. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Figures are in the country's own currency, for the pay period most listings use (per year in most countries, per month in some); the result says which. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.
get_top_hiring_companiesread-onlyList the companies posting the most jobs for a role and place right now on WhatJobs, with their job counts and example listings. Use this when the user asks who is hiring, which companies or employers have openings, or the biggest employers for a role, e.g. "Who's hiring software engineers in Berlin?". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Counts come from the latest 50 listings. The result includes links to each company's listings and to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.
match_jobs_to_profileread-onlyFind WhatJobs listings that fit a person's background: searches up to 4 target job titles at once and ranks the jobs by how well the title matches and how many of their skills each listing mentions. Use this when the user shares their CV, experience or skills and asks what jobs suit them, e.g. "Here's my CV, what should I apply for in Manchester?". Inputs: - job_titles: 1-4 job titles that fit the person (you choose them from what they shared). - skills: up to 10 key skills or tools (e.g. "Python", "SQL", "forklift licence"). - location: where they want to work (the place to search). For remote work use "Remote", alone or with a place. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. Pass only titles and skills. Never pass CV text, names, contact details or other personal data. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.
report_view_statusread-onlyRecords whether the WhatJobs results view finished loading, so loading problems can be found. Called by the results view itself, not by the assistant. Inputs: status (loaded or failed), kind (the type of result shown) and query (the search that result shows).
search_jobsread-onlySearch live WhatJobs job listings by role and place. Use this when the user wants to find jobs, vacancies, internships or other work, or asks to see more results from a job search. Inputs: - keyword: the role, job function, skill or industry only. Leave out the place and filler words such as jobs, vacancies, roles, hiring, in, near, around, at or within. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. For remote work use "Remote", alone or with a place such as "California remote"; only listings that say they are remote come back. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France), dk (Denmark), eg (Egypt), id (Indonesia), my (Malaysia), om (Oman), ph (Philippines), qa (Qatar), sa (Saudi Arabia), sg (Singapore), tz (Tanzania), ug (Uganda), fi (Finland), gr (Greece), gt (Guatemala), hk (Hong Kong), ie (Ireland), it (Italy), kw (Kuwait), lt (Lithuania), lu (Luxembourg), ma (Morocco), no (Norway), nz (New Zealand), pa (Panama), pe (Peru), pl (Poland), pr (Puerto Rico), pt (Portugal), ru (Russia), se (Sweden), th (Thailand), tr (Turkey), ve (Venezuela), bd (Bangladesh), bo (Bolivia), cn (China), cz (Czech Republic), gh (Ghana), ke (Kenya), hu (Hungary), jp (Japan), kr (South Korea), lk (Sri Lanka), mg (Madagascar), py (Paraguay), ro (Romania), sn (Senegal), sv (El Salvador), tn (Tunisia), ua (Ukraine), uy (Uruguay), vn (Vietnam). - chunk_number: the result batch. Use 1 for a new search and add 1 each time the user asks for more. - more_keywords: optional. Other roles to search in the same call when the user asks about several. - more_locations: optional. Other places to search in the same call when the user asks about several. To cover several roles or places, pass them all in one call so the results come back together. Examples: - sales in Bracknell -> keyword="sales", location="Bracknell", market="uk" - software engineer jobs near Manchester -> keyword="software engineer", location="Manchester", market="uk" - nurse jobs in Berlin -> keyword="nurse", location="Berlin", market="de" - comptable à Paris -> keyword="comptable", location="Paris", market="fr" - accountant jobs in Dubai -> keyword="accountant", location="Dubai, United Arab Emirates", market="ae" - developer jobs in Singapore -> keyword="developer", location="Singapore", market="sg" - nurse or carer jobs in Leeds and York -> keyword="nurse", location="Leeds", more_keywords=["carer"], more_locations=["York"], market="uk" Returns up to 10 listings per batch (up to 20 across several roles or places), each with title, company, location, salary when the listing states one, posted date, summary and apply link, plus paging details. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.
search_latest_jobsread-onlyShow only recently posted WhatJobs listings for a role and place, newest first. Use this when the user asks for new, fresh, recent or today's jobs, e.g. "Any electrician jobs posted today in Manchester?" or "New marketing jobs this week in Madrid". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - posted_within_days: 1 for today/yesterday, 7 for this week (default), up to 30. - For remote work, put "Remote" in location, alone or with a place; only listings that say they are remote come back. - more_keywords: optional. Other roles to search in the same call when the user asks about several. - more_locations: optional. Other places to search in the same call when the user asks about several. - market: optional country code; if empty it is inferred from location. Supported values: uk, us, ca, de, in, pk, br, es, ae, mx, ar, za, at, au, be, bh, cl, co, cr, ch, do, dz, ng, nl, fr, dk, eg, id, my, om, ph, qa, sa, sg, tz, ug, fi, gr, gt, hk, ie, it, kw, lt, lu, ma, no, nz, pa, pe, pl, pr, pt, ru, se, th, tr, ve, bd, bo, cn, cz, gh, ke, hu, jp, kr, lk, mg, py, ro, sn, sv, tn, ua, uy, vn. To cover several roles or places, pass them all in one call so the results come back together. The result includes a link to all matching jobs on WhatJobs. Results come only from WhatJobs. Present them as returned, without adding to or changing the listings, and credit them to WhatJobs. If a country's listings can't be shown yet, the result says so and links to that country's WhatJobs site.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.whatjobs.mcp/job-search",
  "title": "WhatJobs Job Search",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://mcp.whatjobs.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "2.3.0",
  "repository": {
    "url": "https://github.com/aymann-ai-wj/whatjobs-mcp",
    "source": "github"
  },
  "websiteUrl": "https://mcp.whatjobs.com/",
  "description": "Search live WhatJobs jobs, salaries and hiring companies in 58 countries from AI assistants."
}