WhatJobs Job Search
REMOTE · MCP.WHATJOBS.COM
Search live WhatJobs jobs, salaries and hiring companies in 58 countries from AI assistants.
Available components
Last scanned (23 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability34
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3752 tokens (~375/item across 10 items; 8 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “match_jobs_to_profile” rewrote its description, which is the text the model reads security
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- Tool “search_latest_jobs” rewrote its description, which is the text the model reads security
- Schema quality: 335 → 375 ▼ functional
- “search_jobs” added an optional parameter “more_keywords” cosmetic
- “search_jobs” added an optional parameter “more_locations” cosmetic
- “search_latest_jobs” added an optional parameter “more_keywords” cosmetic
- “search_latest_jobs” added an optional parameter “more_locations” cosmetic
- 9 Nov 26 0
- Tool “compare_job_counts” rewrote its description, which is the text the model reads security
- Tool “compare_salaries” rewrote its description, which is the text the model reads security
- Tool “get_salary_insights” rewrote its description, which is the text the model reads security
- Tool “get_top_hiring_companies” rewrote its description, which is the text the model reads security
- Tool “match_jobs_to_profile” rewrote its description, which is the text the model reads security
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- Tool “search_latest_jobs” rewrote its description, which is the text the model reads security
- Schema quality: 288 → 335 ▼ functional
- Server version: 2.2.1 → 2.3.0 functional
- Server version: 2.2.0 → 2.2.1 functional
- New tool “report_view_status” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.whatjobs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.whatjobs.com | CN=YE1,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 561dc48af31eaea6f46ae579fb556af7826 |
| SANs: mcp.whatjobs.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.whatjobs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| whatjobs.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.whatjobs.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.whatjobs.com/mcp | HTTPS enforced | 301 | https://mcp.whatjobs.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_job_counts Compare job counts ~404
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | yes | – |
| locations | array | yes | – |
| market | string | – | – |
No output schema declared.
No examples provided.
compare_salaries Compare salaries ~456
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | yes | – |
| locations | array | yes | – |
| market | string | – | – |
No output schema declared.
No examples provided.
get_salary_insights Salary insights ~429
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| location | string | – | – |
| market | string | – | – |
No output schema declared.
No examples provided.
get_top_hiring_companies Top hiring companies ~380
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| location | string | yes | – |
| market | string | – | – |
No output schema declared.
No examples provided.
match_jobs_to_profile Match jobs to profile ~445
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_titles | array | yes | – |
| location | string | yes | – |
| market | string | – | – |
| skills | – | – | – |
No output schema declared.
No examples provided.
report_view_status Report view status ~82
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).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| query | – | – | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
search_jobs Search jobs ~916
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 role…
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_number | integer | – | – |
| keyword | string | yes | – |
| location | string | yes | – |
| market | string | – | – |
| more_keywords | – | – | – |
| more_locations | – | – | – |
No output schema declared.
No examples provided.
search_latest_jobs Latest jobs ~493
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.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
| location | string | yes | – |
| market | string | – | – |
| more_keywords | – | – | – |
| more_locations | – | – | – |
| posted_within_days | integer | – | – |
No output schema declared.
No examples provided.
How do I install the WhatJobs Job Search MCP server?
WhatJobs Job Search is a hosted endpoint at https://mcp.whatjobs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.whatjobs.com
claude mcp add --transport http com-whatjobs-mcp-job-search 'https://mcp.whatjobs.com/mcp'
What is the WhatJobs Job Search MCP server?
WhatJobs Job Search is an MCP server listed in the public MCP registry as com.whatjobs.mcp/job-search. Search live WhatJobs jobs, salaries and hiring companies in 58 countries from AI assistants. This page covers its hosted endpoint (https://mcp.whatjobs.com/mcp).
Is the WhatJobs Job Search MCP server safe to use?
WhatJobs Job Search scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WhatJobs Job Search MCP server expose?
WhatJobs Job Search exposes 8 tools: search_jobs, get_salary_insights, compare_salaries, get_top_hiring_companies, compare_job_counts, and 3 more. Their descriptions and schemas cost roughly 3,605 tokens of context every time the server is loaded.
Does the WhatJobs Job Search MCP server require authentication?
No. We connected to WhatJobs Job Search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WhatJobs Job Search MCP server still maintained?
WhatJobs Job Search is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the WhatJobs Job Search MCP server?
VerifyMCP ran 14 checks on WhatJobs Job Search, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.