# Remotejobify (remote · remotejobify.app)

Search remote jobs by the country you live in, each with the line that proves you can apply.

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

## Components

- remote · `remotejobify.app`: 78/100 (this document), [markdown](https://verifymcp.io/servers/app-remotejobify-remote-jobs/remotejobify.md), [page](https://verifymcp.io/servers/app-remotejobify-remote-jobs/remotejobify)

## Channel facts

- Endpoint: `https://remotejobify.app/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-21.

- **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**: 76/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 515 tokens (~128/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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.
  - Structured output schemas are declared (100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Remotejobify MCP server?

Remotejobify is a hosted endpoint at https://remotejobify.app/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 app-remotejobify-remote-jobs 'https://remotejobify.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-remotejobify-remote-jobs": {
      "url": "https://remotejobify.app/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  app-remotejobify-remote-jobs:
    url: "https://remotejobify.app/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "app-remotejobify-remote-jobs": {
      "type": "http",
      "url": "https://remotejobify.app/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-20 (score 78, +1)

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

### 2026-11-18 (score 77, +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-15 (score 76, +1)

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

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

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

### 2026-11-12 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 74)

First indexed and scored.

## MCP tools (4)

### `search_jobs` (~223 tokens)

Search remote jobs

Search open remote jobs on Remotejobify by where the person lives. Each job comes with who can apply, the line from the listing that proves it, pay when listed, and a link. Pass country whenever you know where they live: most remote jobs are only open to some countries. Without it you get jobs open worldwide.

Input parameters:

- `country` (string): The country the person lives in: a name ("Philippines", "UK") or a two-letter code ("PH", "GB").
- `limit` (integer): How many jobs, up to 20. 10 if not given.
- `query` (string): Words for the job title or company, like "customer support", "python" or "nurse". Optional.
- `role` (string): A job type, to narrow the search. Optional.
- `working_hours` (string): daytime: the job keeps business hours that are daytime where they live. night_shift: night there (only jobs whose listing states its hours). part_time: part-time jobs. daytime and night_shift need co…

Output parameters:

- `country` (string|null)
- `jobs` (array)
- `more` (string)
- `total` (integer)

### `get_job` (~87 tokens)

Get a remote job

One job on Remotejobify by its id or its remotejobify.app link: who can apply, the lines from the listing that prove it, pay, and the job description.

Input parameters:

- `country` (string): Where the person lives, to say whether they can apply. Optional.
- `id` (string, required): The job id from search_jobs, or its link on remotejobify.app.

Output parameters:

- `all_proof` (array)
- `company` (string)
- `description` (string|null)
- `id` (string)
- `location` (string|null)
- `pay` (string|null)
- `posted` (string)
- `proof` (string|null)
- `title` (string)
- `url` (string)
- `who_can_apply` (string)

### `search` (~60 tokens)

Search

Search Remotejobify’s open remote jobs. Put the country the person lives in into the query ("customer support jobs in the Philippines"): most remote jobs are only open to some countries. Returns ids for fetch.

Input parameters:

- `query` (string, required): What to search for.

Output parameters:

- `results` (array)

### `fetch` (~40 tokens)

Fetch

One Remotejobify job by the id search gave: who can apply, the proof line and the description.

Input parameters:

- `id` (string, required): The id from search.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74

## Common questions

### What is the Remotejobify MCP server?

Remotejobify is an MCP server listed in the public MCP registry as app.remotejobify/remote-jobs. Search remote jobs by the country you live in, each with the line that proves you can apply. This page covers its hosted endpoint (https://remotejobify.app/mcp).

### Is the Remotejobify MCP server safe to use?

Remotejobify scores 78 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 Remotejobify MCP server expose?

Remotejobify exposes 4 tools: search_jobs, get_job, search, fetch. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.

### Does the Remotejobify MCP server require authentication?

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

### Is the Remotejobify MCP server still maintained?

Remotejobify 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 Remotejobify MCP server?

VerifyMCP ran 13 checks on Remotejobify, 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://remotejobify.app/mcp
- Website: https://remotejobify.app/connect-ai/
- Changelog RSS feed: https://verifymcp.io/servers/app-remotejobify-remote-jobs/remotejobify.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-remotejobify-remote-jobs/remotejobify/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-remotejobify-remote-jobs/remotejobify.json
- HTML version of this page: https://verifymcp.io/servers/app-remotejobify-remote-jobs/remotejobify
