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.

Remotejobify

REMOTE · REMOTEJOBIFY.APP

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

Available components

+3 this week 78 Trust /100

Last scanned (15 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 20 Nov 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.

  • 18 Nov 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.

  • 15 Nov 26 +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.

  • 13 Nov 26 +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.

  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 74

    First indexed and scored.

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 21 Nov 2026 · Probed https://remotejobify.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=remotejobify.app CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 76fb635a1c37e3730e9bd5966dfc4dab
SANs: remotejobify.app, www.remotejobify.app, *.www.remotejobify.app
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 remotejobify.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
remotejobify.app. No DS 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
Header Value
strict-transport-security max-age=31536000
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://remotejobify.app/mcp Verified 200
http (plaintext) http://remotejobify.app/mcp HTTPS enforced 301 https://remotejobify.app/mcp
MCP tools · 4 exposed · ~410 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
fetch ~40

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

NameTypeReqDescription
idstringyesThe id from search.
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_job ~87

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.

NameTypeReqDescription
countrystring–Where the person lives, to say whether they can apply. Optional.
idstringyesThe job id from search_jobs, or its link on remotejobify.app.
NameTypeReqDescription
all_proofarray––
companystringyes–
descriptionstring|null––
idstringyes–
locationstring|null––
paystring|null––
postedstring––
proofstring|nullyes–
titlestringyes–
urlstringyes–
who_can_applystringyes–

No examples provided.

search ~60

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.

NameTypeReqDescription
querystringyesWhat to search for.
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_jobs ~223

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.

NameTypeReqDescription
countrystring–The country the person lives in: a name ("Philippines", "UK") or a two-letter code ("PH", "GB").
limitinteger–How many jobs, up to 20. 10 if not given.
querystring–Words for the job title or company, like "customer support", "python" or "nurse". Optional.
rolestring–A job type, to narrow the search. Optional.
working_hoursstring–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…
NameTypeReqDescription
countrystring|nullyes–
jobsarrayyes–
morestringyes–
totalintegeryes–

No examples provided.

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.

remote · remotejobify.app

# add to Claude Code
claude mcp add --transport http app-remotejobify-remote-jobs 'https://remotejobify.app/mcp'
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.