Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Relomote

REMOTE · RELOMOTE.COM

Search remote jobs by the country they hire from, and jobs with relocation or visa sponsorship.

Available components

−55 this week 25 Trust /100

Last scanned (18 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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 →

Changelog

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.

  • 1 Nov 26 −56
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Stability: 0.70 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 30 Oct 26 +1

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

  • 27 Oct 26 +1

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

  • 25 Oct 26 +1

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

  • 23 Oct 26 +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.

  • 21 Oct 26 +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.

  • 19 Oct 26 +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.

  • 17 Oct 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.

Diagnostics

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://relomote.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=relomote.com CN=WE1,O=Google Trust Services,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA256 7cf02d84208d739e0ecb99a7a6f968b3
SANs: relomote.com, *.relomote.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 relomote.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
relomote.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 404
Header Value
strict-transport-security max-age=15552000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://relomote.com/mcp HTTP error 404
http (plaintext) http://relomote.com/mcp HTTPS enforced 301 https://relomote.com/mcp
MCP tools · 2 exposed · ~417 tokens

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 →

Tool Tokens
get_job ~109

Get one Relomote job by its id or Relomote URL: title, company, where it hires from or moves the person to, work type, posted date, salary when disclosed, and the start of the description, for when the person asks about a specific job. Closed jobs are not returned.

NameTypeReqDescription
boardstring–The board the id came from, if known.
job_idstringyesThe job's id from search_jobs, or its relomote.com URL.
NameTypeReqDescription
boardstringyes–
categorystring|null––
companystring|null––
description_excerptstring|null––
employment_typestring|null––
idstringyes–
locationstring|null–Remote board: where candidates can be ("Worldwide", a region or countries). Relocation board: the country the job moves you to.
logo_urlstring|null–The company's logo, a 128px image.
postedstringyesYYYY-MM-DD
relocation_supportboolean|null––
salarystring|null––
titlestringyes–
urlstringyes–
visa_sponsorshipboolean|null––
work_arrangementstring|null––

No examples provided.

search_jobs ~308

Search live job listings on Relomote, collected from company career pages. board "remote" (default) finds remote and hybrid jobs a person can do from a given country, region or anywhere in the world; for a country it also includes jobs open to its whole region and jobs open worldwide, since those are open from there too. board "relocation" finds jobs abroad that offer relocation support or visa sponsorship; there the location is where the job moves the person to. Returns at most 10 jobs per call, newest first, each with a link to its Relomote page, where the person reads the full listing and applies. A search returns at most 3 pages.

NameTypeReqDescription
boardstring–"remote" (default) or "relocation" (relocation support or visa sponsorship).
categorystring–Job category.
limitinteger––
locationstring–A country ("Nigeria", "Philippines", "DE"), a region (Africa, Asia, Europe, Latin America, Middle East, North America, Oceania) or "worldwide" (remote board only: jobs open from anywhere).
pageinteger––
querystring–Job title or keywords, e.g. "customer support", "data analyst", "react developer". Omit to list the newest jobs for the filters.
visa_sponsorshipboolean–Only jobs that sponsor a work visa. Implies the relocation board.
NameTypeReqDescription
boardstringyes–
has_morebooleanyes–
jobsarrayyes–
notestring|null–Set when the search was reinterpreted (a typo fixed, a place read as a location).
pageintegeryes–
see_all_urlstringyesThe same search on relomote.com.
totalintegeryesJobs matching the search on Relomote.
total_is_lower_boundboolean––

No examples provided.

Install

How do I install the Relomote MCP server?

Relomote is a hosted endpoint at https://relomote.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 · relomote.com

# add to Claude Code
claude mcp add --transport http com-relomote-jobs 'https://relomote.com/mcp'
Common questions

What is the Relomote MCP server?

Relomote is an MCP server listed in the public MCP registry as com.relomote/jobs. Search remote jobs by the country they hire from, and jobs with relocation or visa sponsorship. This page covers its hosted endpoint (https://relomote.com/mcp).

Is the Relomote MCP server safe to use?

Relomote scores 25 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 Relomote MCP server expose?

Relomote exposes 2 tools: search_jobs, get_job. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.

Does the Relomote MCP server require authentication?

Its publisher declares no required credentials for Relomote. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Relomote MCP server still maintained?

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

VerifyMCP ran 5 checks on Relomote, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Relomote: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.