# getwork.dev (remote · getwork.dev)

Search developer jobs read straight from employers' hiring systems: stack, level, remote, salary.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `getwork.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/dev-getwork-jobs/getwork.md), [page](https://verifymcp.io/servers/dev-getwork-jobs/getwork)

## Channel facts

- Endpoint: `https://getwork.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
  - Structured output schemas are declared (75% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-getwork-jobs 'https://getwork.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-getwork-jobs": {
      "url": "https://getwork.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-getwork-jobs": {
      "type": "http",
      "url": "https://getwork.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-getwork-jobs]
url = "https://getwork.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-getwork-jobs": {
      "type": "remote",
      "url": "https://getwork.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-getwork-jobs --url 'https://getwork.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-getwork-jobs:
    url: "https://getwork.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-getwork-jobs": {
      "Transport": "http",
      "Url": "https://getwork.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-getwork-jobs -t streamable-http -u 'https://getwork.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-getwork-jobs": {
      "type": "http",
      "url": "https://getwork.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 76, +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.

### 2026-11-02 (score 75, +1)

- [security] Tool “list_companies” rewrote its description, which is the text the model reads
- [cosmetic] “list_companies” added an optional parameter “limit”
- [cosmetic] “list_companies” added an optional parameter “query”

### 2026-10-31 (score 74, +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.

### 2026-10-29 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 72)

First indexed and scored.

## MCP tools (8)

### `search_jobs` (~366 tokens)

Search developer jobs

Search active developer jobs. Returns compact JobSpecs (no description) sorted by relevance or recency. Use get_job for details.

Input parameters:

- `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.

Output parameters:

- `jobs` (array)
- `next_offset` (integer|null)
- `offset` (integer)
- `security_notice` (string)
- `total` (integer)

### `get_job` (~32 tokens)

Get a job

Full JobSpec for one job, including the employer's description as untrusted_description.

Input parameters:

- `id` (string, required)

Output parameters:

- `apply_url` (string|null)
- `company` (object)
- `getwork_url` (string)
- `id` (string)
- `injection_flag` (boolean)
- `security_notice` (string)
- `title` (string)
- `untrusted_description` (string)

### `similar_jobs` (~44 tokens)

Similar jobs

Roles similar to a given job (title, stack and description overlap), excluding the same role at other locations.

Input parameters:

- `id` (string, required)
- `limit` (integer)

Output parameters:

- `jobs` (array)
- `security_notice` (string)
- `similar_to` (object)

### `search` (~96 tokens)

Search (natural language)

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.

Input parameters:

- `query` (string, required)

### `fetch` (~26 tokens)

Fetch a job

Full text and metadata for one job id returned by search.

Input parameters:

- `id` (string, required)

### `salary_insights` (~279 tokens)

Salary insights

Yearly salary percentiles per currency for active jobs matching the filters, from employer-published ranges.

Input parameters:

- `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.

Output parameters:

- `by_currency` (array)
- `note` (string)
- `period` (string)

### `list_companies` (~50 tokens)

List companies

Companies in the index with their number of active developer jobs, most jobs first. Filter by name with query.

Input parameters:

- `limit` (integer)
- `query` (string): Part of the company name.

Output parameters:

- `companies` (array)
- `total` (integer)

### `market_overview` (~21 tokens)

Market overview

Totals and the most requested technologies across all active jobs.

Output parameters:

- `active_jobs` (integer)
- `companies` (integer)
- `jobs_with_salary` (integer)
- `top_stack` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-getwork-jobs/getwork#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://getwork.dev/mcp
- Website: https://getwork.dev/agents/
- Changelog RSS feed: https://verifymcp.io/servers/dev-getwork-jobs/getwork.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-getwork-jobs/getwork/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-getwork-jobs/getwork.json
- HTML version of this page: https://verifymcp.io/servers/dev-getwork-jobs/getwork