RemoShift Remote Jobs
REMOTE · REMOSHIFT.COM
Search live remote jobs worldwide. Job search, remote salary bands, work-from-anywhere eligibility.
Available components
Last scanned (9 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 601 tokens (~120/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 0
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 4 Nov 26 0
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- 3 Nov 26 0
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- 2 Nov 26 0
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- 1 Nov 26 0
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- 31 Oct 26 0
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- 30 Oct 26 0
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- 29 Oct 26 0
- Tool “search_jobs” rewrote its description, which is the text the model reads security
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://remoshift.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=remoshift.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8bd68e7f2970e77a0e44b6259cf2e4ab |
| SANs: remoshift.com, *.remoshift.com | ||||||
| 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 remoshift.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| remoshift.com. | absent | 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://remoshift.com/mcp | Verified | 200 | |
| http (plaintext) | http://remoshift.com/mcp | HTTPS enforced | 301 | https://remoshift.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 →
get_job ~59
Fetch one job in full (description included) by the 8-hex id that appears at the end of a detail_url.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 6-16 char hex job id, e.g. "c00584a5" |
No output schema declared.
No examples provided.
job_facets ~33
Counts by source, category, country and tag across the live index — call this first to learn what filters are useful.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
salary_bands ~115
Remote salary percentiles (p25 / median / p75, USD) per role, from jobs that disclosed pay in the live index, with an optional seniority breakdown. Use this to answer "what does a remote X earn?". Call with no arguments to list every role and its median.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | Role slug or title, e.g. "data-engineer" or "Data Engineer". Omit to list all roles. |
| seniority | string | – | Optional: narrow to one seniority band |
No output schema declared.
No examples provided.
search_jobs ~279
Search 139,084+ live, scam-filtered remote jobs (updated hourly). Natural-language queries OK (keyword relevance over title + company + description). Returns title, company, location, salary when disclosed, posted date, an employer apply_url, and a canonical detail_url to link back to.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Job category, e.g. "developer", "design", "customer service", "sales", "marketing" |
| country | string | – | ISO-2 country code the job must accept applicants from, e.g. "US", "HK", "DE" |
| has_salary | boolean | – | true = only jobs that disclose salary |
| limit | number | – | Max results, 1-25 (default 10) |
| posted_within_days | number | – | Only jobs posted in the last N days |
| query | string | – | Keywords or a natural-language description, e.g. "senior react engineer" |
| seniority | string | – | – |
| sort | string | – | – |
| source | string | – | Origin board/ATS name, e.g. "Himalayas", "RemoteOK", "Greenhouse" |
| tag | string | – | Skill tag, e.g. "react", "python", "figma" |
| work_anywhere | boolean | – | true = location-independent jobs only |
No output schema declared.
No examples provided.
work_anywhere_scope ~76
Answer "can I work remotely from <country>?" — returns how many live jobs accept applicants in that country and how many are location-independent (no country restriction). This is eligibility, not a hiring guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO-2 country code, e.g. "PT", "US", "DE" |
No output schema declared.
No examples provided.
How do I install the RemoShift Remote Jobs MCP server?
RemoShift Remote Jobs is a hosted endpoint at https://remoshift.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 · remoshift.com
claude mcp add --transport http com-remoshift-jobs 'https://remoshift.com/mcp'
What is the RemoShift Remote Jobs MCP server?
RemoShift Remote Jobs is an MCP server listed in the public MCP registry as com.remoshift/jobs. Search live remote jobs worldwide. Job search, remote salary bands, work-from-anywhere eligibility. This page covers its hosted endpoint (https://remoshift.com/mcp).
Is the RemoShift Remote Jobs MCP server safe to use?
RemoShift Remote Jobs scores 74 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 RemoShift Remote Jobs MCP server expose?
RemoShift Remote Jobs exposes 5 tools: search_jobs, get_job, job_facets, salary_bands, work_anywhere_scope. Their descriptions and schemas cost roughly 562 tokens of context every time the server is loaded.
Does the RemoShift Remote Jobs MCP server require authentication?
No. We connected to RemoShift Remote Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RemoShift Remote Jobs MCP server still maintained?
RemoShift 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.