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.

Remote Dev Jobs

REMOTE · WWW.REMOTEFRONTENDJOBS.COM

Live remote frontend, backend and Java developer jobs: search, salaries, hiring companies.

+4 this week 75 Trust /100

Last scanned (5 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 5 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 Security74
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 752 tokens (~125/item across 6 items; 6 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 74% of tool parameters carry a description.Partial
  • 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 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.

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

  • 21 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
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://www.remotefrontendjobs.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=remotefrontendjobs.com CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 914b44db90b6e0c013c6753b3bf2217a
SANs: remotefrontendjobs.com, www.remotefrontendjobs.com, *.www.remotefrontendjobs.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 www.remotefrontendjobs.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
remotefrontendjobs.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
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.remotefrontendjobs.com/mcp Verified 200
http (plaintext) http://www.remotefrontendjobs.com/mcp HTTPS enforced 301 https://www.remotefrontendjobs.com/mcp
MCP tools · 6 exposed · ~666 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
company_jobs ~87

List all open remote roles at one company by company id (see hiring_companies for ids).

NameTypeReqDescription
boardstring–Which job board to search. Defaults to the board this server is installed from. frontend = remotefrontendjobs.com, backend = remotebackendjobs.com, java = remotejavajobs.com.
companyIdstringyesCompany id from hiring_companies.
NameTypeReqDescription
boardstringyes–
companyobjectyes–

No examples provided.

get_job ~95

Get the full description, salary, location restrictions and apply links for one job by id. Use after search_jobs when the user picks a role.

NameTypeReqDescription
boardstring–Which job board to search. Defaults to the board this server is installed from. frontend = remotefrontendjobs.com, backend = remotebackendjobs.com, java = remotejavajobs.com.
idstringyesJob id from search_jobs.
NameTypeReqDescription
boardstringyes–
jobobjectyes–

No examples provided.

hiring_companies ~84

List companies actively hiring remote roles on a board, ranked by open positions, with links to each company page.

NameTypeReqDescription
boardstring–Which job board to search. Defaults to the board this server is installed from. frontend = remotefrontendjobs.com, backend = remotebackendjobs.com, java = remotejavajobs.com.
limitinteger––
NameTypeReqDescription
boardstringyes–
companiesarrayyes–

No examples provided.

market_insights ~84

Salary and hiring-market stats computed from live postings (AI share, tech demand, tech salaries, AI pay premium, geography, PTO, volume). For "is X dying / what pays most" questions.

NameTypeReqDescription
boardstring–Board scope. Defaults to the installing board.
monthsinteger––
typestringyesWhich insight snapshot to return.
NameTypeReqDescription
boardstringyes–
insightobjectyesRaw trend snapshot (series + summary).
monthsintegeryes–
typestringyes–

No examples provided.

search_jobs ~237

Search LIVE remote jobs with real filters (stack keyword, region, minimum salary, seniority, date posted). Returns live listings with canonical job-page URLs. Always present the job URL from the result — never invent or guess job links.

NameTypeReqDescription
boardstring–Which job board to search. Defaults to the board this server is installed from. frontend = remotefrontendjobs.com, backend = remotebackendjobs.com, java = remotejavajobs.com.
limitinteger––
minSalaryYearlynumber–Minimum yearly pay in USD, e.g. 120000. Optional.
offsetinteger––
postedWithinstring–Only jobs posted within this window. Default all.
querystring–Stack/keyword, e.g. react, python, spring. Optional.
regionsstring–Comma-separated geo regions, e.g. "europe,asia". Strict: only explicitly tagged jobs. Optional.
senioritiesstring–Comma-separated seniority buckets: junior, mid, senior, staff, lead, principal, executive. Optional.
NameTypeReqDescription
boardstringyes–
jobsarrayyes–

No examples provided.

top_viewed ~79

Most-viewed remote jobs on a board right now (social proof / trending roles).

NameTypeReqDescription
boardstring–Which job board to search. Defaults to the board this server is installed from. frontend = remotefrontendjobs.com, backend = remotebackendjobs.com, java = remotejavajobs.com.
limitinteger––
NameTypeReqDescription
boardstringyes–
jobsarrayyes–

No examples provided.

Install

How do I install the Remote Dev Jobs MCP server?

Remote Dev Jobs is a hosted endpoint at https://www.remotefrontendjobs.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 · www.remotefrontendjobs.com

# add to Claude Code
claude mcp add --transport http angelnikolov-remote-jobs 'https://www.remotefrontendjobs.com/mcp'
Common questions

What is the Remote Dev Jobs MCP server?

Remote Dev Jobs is an MCP server listed in the public MCP registry as io.github.angelnikolov/remote-jobs. Live remote frontend, backend and Java developer jobs: search, salaries, hiring companies. This page covers its hosted endpoint (https://www.remotefrontendjobs.com/mcp).

Is the Remote Dev Jobs MCP server safe to use?

Remote Dev Jobs scores 75 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 Remote Dev Jobs MCP server expose?

Remote Dev Jobs exposes 6 tools: search_jobs, get_job, hiring_companies, company_jobs, top_viewed, market_insights. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded.

Does the Remote Dev Jobs MCP server require authentication?

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

Is the Remote Dev Jobs MCP server still maintained?

Remote Dev 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.