getwork.dev
REMOTE · GETWORK.DEV
Search developer jobs read straight from employers' hiring systems: stack, level, remote, salary.
Available components
Last scanned (13 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1065 tokens (~133/item across 8 items; 8 tools + 0 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 53% of tool parameters carry a description.Partial
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
- Tool “list_companies” rewrote its description, which is the text the model reads security
- “list_companies” added an optional parameter “limit” cosmetic
- “list_companies” added an optional parameter “query” cosmetic
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 72
First indexed and scored.
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 5 Nov 2026 · Probed https://getwork.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getwork.dev | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 30ba1e8e828a57d90ed56ff7e55371c3 |
| SANs: getwork.dev, *.getwork.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of getwork.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| getwork.dev. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://getwork.dev/mcp | Verified | 200 | |
| http (plaintext) | http://getwork.dev/mcp | HTTPS enforced | 301 | https://getwork.dev/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 →
fetch Fetch a job ~26
Full text and metadata for one job id returned by search.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_job Get a job ~32
Full JobSpec for one job, including the employer's description as untrusted_description.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| apply_url | string|null | – | – |
| company | object | yes | – |
| getwork_url | string | – | – |
| id | string | yes | – |
| injection_flag | boolean | – | – |
| security_notice | string | – | – |
| title | string | yes | – |
| untrusted_description | string | yes | – |
No examples provided.
list_companies List companies ~50
Companies in the index with their number of active developer jobs, most jobs first. Filter by name with query.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | Part of the company name. |
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| total | integer | yes | – |
No examples provided.
market_overview Market overview ~21
Totals and the most requested technologies across all active jobs.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| active_jobs | integer | yes | – |
| companies | integer | – | – |
| jobs_with_salary | integer | – | – |
| top_stack | array | yes | – |
No examples provided.
salary_insights Salary insights ~279
Yearly salary percentiles per currency for active jobs matching the filters, from employer-published ranges.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company slug from list_companies. |
| countries | array | – | ISO 3166-1 alpha-2 codes, e.g. NL, DE, GB. |
| currency | string | – | ISO currency code (EUR, USD, GBP). Restricts to jobs that publish pay in this currency. |
| exclude | array | – | Leave out jobs matching any of these: a stack tag (not in the primary stack or title), a role family, or a topic like 'crypto' or 'gambling' (not mentioned anywhere, synonyms included). |
| posted_within_days | integer | – | – |
| query | string | – | Free text, e.g. 'distributed systems' or 'payments'. Every word must match (a word also matches its synonyms). |
| regions | array | – | Any of these regions. Worldwide-remote jobs are always included. |
| remote | string | – | – |
| role_family | array | – | – |
| seniority | array | – | – |
| stack | array | – | Technology tags that must all be in the role's primary stack, lowercase: rust, go, typescript, python, react, postgres, kubernetes, ... Passing mentions (stack_mentioned) do not match. |
| Name | Type | Req | Description |
|---|---|---|---|
| by_currency | array | yes | – |
| note | string | – | – |
| period | string | – | – |
No examples provided.
search Search (natural language) ~96
Natural-language job search, e.g. 'remote senior Rust jobs in Europe'. Understands salary floors ('over €120k') and exclusions ('no crypto'). Returns ids, titles and URLs, the total, filters: how the query was read (as search_jobs arguments), and broadened: filters it dropped to find any results. Use fetch for details. Prefer search_jobs when you can set filters directly.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
search_jobs Search developer jobs ~366
Search active developer jobs. Returns compact JobSpecs (no description) sorted by relevance or recency. Use get_job for details.
| Name | Type | Req | Description |
|---|---|---|---|
| collapse | boolean | – | Group the same role posted for several locations into one result; same_role_other_locations tells how many more exist. |
| company | string | – | Company slug from list_companies. |
| countries | array | – | ISO 3166-1 alpha-2 codes, e.g. NL, DE, GB. |
| currency | string | – | ISO currency code (EUR, USD, GBP). Restricts to jobs that publish pay in this currency. |
| exclude | array | – | Leave out jobs matching any of these: a stack tag (not in the primary stack or title), a role family, or a topic like 'crypto' or 'gambling' (not mentioned anywhere, synonyms included). |
| limit | integer | – | – |
| min_salary | integer | – | Minimum yearly salary (upper end of the published range must reach it). Combine with currency. |
| offset | integer | – | – |
| posted_within_days | integer | – | – |
| query | string | – | Free text, e.g. 'distributed systems' or 'payments'. Every word must match (a word also matches its synonyms). |
| regions | array | – | Any of these regions. Worldwide-remote jobs are always included. |
| remote | string | – | – |
| role_family | array | – | – |
| salary_required | boolean | – | Only jobs that publish a salary range. |
| seniority | array | – | – |
| stack | array | – | Technology tags that must all be in the role's primary stack, lowercase: rust, go, typescript, python, react, postgres, kubernetes, ... Passing mentions (stack_mentioned) do not match. |
| Name | Type | Req | Description |
|---|---|---|---|
| jobs | array | yes | – |
| next_offset | integer|null | – | – |
| offset | integer | – | – |
| security_notice | string | – | – |
| total | integer | yes | – |
No examples provided.
similar_jobs Similar jobs ~44
Roles similar to a given job (title, stack and description overlap), excluding the same role at other locations.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| jobs | array | yes | – |
| security_notice | string | – | – |
| similar_to | object | yes | – |
No examples provided.
How do I install the getwork.dev MCP server?
getwork.dev is a hosted endpoint at https://getwork.dev/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 · getwork.dev
claude mcp add --transport http dev-getwork-jobs 'https://getwork.dev/mcp'
What is the getwork.dev MCP server?
getwork.dev is an MCP server listed in the public MCP registry as dev.getwork/jobs. Search developer jobs read straight from employers' hiring systems: stack, level, remote, salary. This page covers its hosted endpoint (https://getwork.dev/mcp).
Is the getwork.dev MCP server safe to use?
getwork.dev scores 76 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 getwork.dev MCP server expose?
getwork.dev exposes 8 tools: search_jobs, get_job, similar_jobs, search, fetch, and 3 more. Their descriptions and schemas cost roughly 914 tokens of context every time the server is loaded.
Does the getwork.dev MCP server require authentication?
No. We connected to getwork.dev without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the getwork.dev MCP server still maintained?
getwork.dev is still listed as active in the MCP registry. We last reached this channel on 5 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 getwork.dev MCP server?
VerifyMCP ran 13 checks on getwork.dev, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.