# remoty.work Remote Jobs (remote · remoty.work)

Live remote jobs filtered to the ones a person can take from the country they live in.

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

## Components

- remote · `remoty.work`: 77/100 (this document), [markdown](https://verifymcp.io/servers/work-remoty-remote-jobs/remoty.md), [page](https://verifymcp.io/servers/work-remoty-remote-jobs/remoty)

## Channel facts

- Endpoint: `https://remoty.work/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 72/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 474 tokens (~158/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the remoty.work Remote Jobs MCP server?

remoty.work Remote Jobs is a hosted endpoint at https://remoty.work/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 work-remoty-remote-jobs 'https://remoty.work/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "work-remoty-remote-jobs": {
      "url": "https://remoty.work/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "work-remoty-remote-jobs": {
      "type": "http",
      "url": "https://remoty.work/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.work-remoty-remote-jobs]
url = "https://remoty.work/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add work-remoty-remote-jobs --url 'https://remoty.work/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  work-remoty-remote-jobs:
    url: "https://remoty.work/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "work-remoty-remote-jobs": {
      "Transport": "http",
      "Url": "https://remoty.work/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add work-remoty-remote-jobs -t streamable-http -u 'https://remoty.work/mcp'
```

### Other

```json
{
  "mcpServers": {
    "work-remoty-remote-jobs": {
      "type": "http",
      "url": "https://remoty.work/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-05 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 75, 0)

- [functional regression] Schema quality: pass → fail
- [functional] New tool “match_jobs_to_profile”

### 2026-10-30 (score 75, +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-10-28 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 73, +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-24 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 71)

First indexed and scored.

## MCP tools (3)

### `match_jobs_to_profile` (~205 tokens)

Rank live remote jobs against a job seeker's profile (titles, skills, level, country, minimum pay) and say why each fits and what it also asks for. Build the profile from the person's resume or what they told you; only jobs they can take from their country are ranked.

Input parameters:

- `country` (string|null): Where the person lives: a country name or ISO code. Without it, only jobs open worldwide are ranked.
- `min_salary_usd` (integer|null): Lowest yearly pay they would accept, in US dollars.
- `seniority` (string|null): One of: intern, junior, mid, senior, staff, lead, principal, head, director.
- `skills` (array): Skills from their resume or what they said, e.g. ["Rust", "PostgreSQL", "Kubernetes"].
- `titles` (array): Roles the person wants or has held, e.g. ["Backend Engineer", "Platform Engineer"].

### `remote_jobs_open_to_country` (~99 tokens)

How many live remote jobs a person living in a given country can actually take, and the newest of them. Most 'remote' listings are limited to one country; this applies that rule.

Input parameters:

- `country` (string, required): Where the job seeker lives: a country name or ISO code ("Nigeria", "NG").
- `limit` (integer|null): How many of the newest jobs to return, 1 to 20 (default 10).

### `search_remote_jobs` (~128 tokens)

Search live remote job listings by role, skill or company. Pass the job seeker's country to get only jobs they can legally take from where they live.

Input parameters:

- `country` (string|null): Where the job seeker lives: a country name or ISO code ("Kenya", "KE"). When given, only jobs that person can legally take are returned.
- `limit` (integer|null): How many jobs to return, 1 to 20 (default 10).
- `query` (string, required): Role, skill or company, e.g. "react developer", "customer support", "Canonical".

## Diagnostics

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

## Score history

- 2026-11-05: 77
- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75
- 2026-11-01: 75
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 71

## Common questions

### What is the remoty.work Remote Jobs MCP server?

remoty.work Remote Jobs is an MCP server listed in the public MCP registry as work.remoty/remote-jobs. Live remote jobs filtered to the ones a person can take from the country they live in. This page covers its hosted endpoint (https://remoty.work/mcp).

### Is the remoty.work Remote Jobs MCP server safe to use?

remoty.work Remote Jobs scores 77 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 remoty.work Remote Jobs MCP server expose?

remoty.work Remote Jobs exposes 3 tools: match_jobs_to_profile, remote_jobs_open_to_country, search_remote_jobs. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.

### Does the remoty.work Remote Jobs MCP server require authentication?

No. We connected to remoty.work Remote Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the remoty.work Remote Jobs MCP server still maintained?

remoty.work Remote Jobs 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.

## Links

- Remote endpoint: https://remoty.work/mcp
- Website: https://remoty.work/how-it-works/
- Changelog RSS feed: https://verifymcp.io/servers/work-remoty-remote-jobs/remoty.xml
- Changelog JSON feed: https://verifymcp.io/servers/work-remoty-remote-jobs/remoty.json
- HTML version of this page: https://verifymcp.io/servers/work-remoty-remote-jobs/remoty