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.

Nomado24 Remote Jobs

REMOTE · API.NOMADO24.DE · SCANNED SEP 21

Search 13,000+ remote/hybrid jobs in Germany/EU, open a posting, get market stats. Free, no auth.

Available components

0 this week 85 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1052 tokens (~350/item across 3 items; 3 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 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the Nomado24 Remote Jobs MCP server?

Nomado24 Remote Jobs is a hosted endpoint at https://api.nomado24.de/api/public/v1/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 · api.nomado24.de

# add to Claude Code
claude mcp add --transport http de-nomado24-jobs 'https://api.nomado24.de/api/public/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "de-nomado24-jobs": {
      "url": "https://api.nomado24.de/api/public/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "de-nomado24-jobs": {
      "type": "http",
      "url": "https://api.nomado24.de/api/public/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.de-nomado24-jobs]
url = "https://api.nomado24.de/api/public/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-nomado24-jobs": {
      "type": "remote",
      "url": "https://api.nomado24.de/api/public/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add de-nomado24-jobs --url 'https://api.nomado24.de/api/public/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  de-nomado24-jobs:
    url: "https://api.nomado24.de/api/public/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "de-nomado24-jobs": {
      "Transport": "http",
      "Url": "https://api.nomado24.de/api/public/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add de-nomado24-jobs -t streamable-http -u 'https://api.nomado24.de/api/public/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "de-nomado24-jobs": {
      "type": "http",
      "url": "https://api.nomado24.de/api/public/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 6 Sept 26 +6
    • Authorization: unverified → partial security
    • Tool “get_job” changed its title: Get job posting cosmetic
    • Tool “get_job_statistics” changed its title: Job board statistics cosmetic
    • Tool “search_jobs” changed its title: Search remote jobs cosmetic
  • 1 Sept 26 +1
    • Stability: 0.97 → pass security
  • 30 Aug 26 +1

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

  • 28 Aug 26 +1

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

  • 27 Aug 26 0
    • Tool “search_jobs” rewrote its description, which is the text the model reads security
    • Schema quality: 314 → 350 functional
    • “search_jobs” reworded the description of “include_total” cosmetic
    • “search_jobs” reworded the description of “work_arrangement” cosmetic
  • 26 Aug 26 −2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 21 Sept 2026 · Probed https://api.nomado24.de/api/public/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.nomado24.de CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2026 1 Feb 2027 RSA 2048 SHA256-RSA 4730d30c5d68dc364396571907e1925
SANs: api.nomado24.de
CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 2 Nov 2017 2 Nov 2027 RSA 2048 SHA256-RSA d07782a133fc6f9a57296e131ffd179
CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US 1 Aug 2013 15 Jan 2038 RSA 2048 SHA256-RSA 33af1e6a711a9a0bb2864b11d09fae5

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.nomado24.de. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
de. present 26755 8 Verified
nomado24.de. 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
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.nomado24.de/api/public/v1/mcp Verified 200
http (plaintext) http://api.nomado24.de/api/public/v1/mcp HTTPS enforced 301 https://api.nomado24.de/api/public/v1/mcp
MCP tools · 3 exposed · ~1,052 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 ~138

Fetch ONE nomado24 job posting by id, with the complete v2 payload: the posting body where the source permits redistribution, per-field provenance (dataOrigin: who asserted each field, by which method, when), salaryOrigin, firstSeenAt, lastVerifiedAt with its verification method, and updatedAt (the last genuine content change). Returns an error result for an id that is not a live posting; expired and withdrawn postings are not served. Read-only, free, attribution required (see structuredContent.attribution).

NameTypeReqDescription
idstringyesJob id as returned by search_jobs ('job_<slug>'). A bare slug is also accepted

No output schema declared.

No examples provided.

get_job_statistics ~41

Get aggregate statistics (active jobs, new-this-week/month, top sources, salary ranges) for nomado24's remote-jobs board. No input required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_jobs ~873

Search nomado24's remote/hybrid job board. Read-only, free, attribution required (see structuredContent.attribution). Answers over one of two contracts, chosen by the arguments you send. Send only q/language/page/per_page and you get the legacy v1 result shape with page-based paging. Send any structured filter (country, applicant_region, work_arrangement, employment_type, seniority, skills, salary_min/max, published_after, verified_after, source, company, sort, include_total) or a cursor and you get the v2 contract: richer job objects, per-posting provenance (salaryOrigin, firstSeenAt, lastVerifiedAt, verification.method, updatedAt), a corpus changeWatermark, a snapshotId and keyset paging via pagination.nextCursor. The two are mutually exclusive: page plus a structured filter is refused rather than silently resolved. Structured results omit the posting body and the per-field dataOrigin to stay cheap to read; call get_job for those. A filter nomado24 cannot answer honestly is refused with the reason, never answered with the unfiltered corpus. For the same reason pagination.total is null (totalRelation 'not_computed') whenever a post-projection filter (skills, seniority, salary bounds, employment_type=unknown) is in play — a null total is deliberate, not an error.

NameTypeReqDescription
applicant_regionarrayWhere a CANDIDATE may be: WORLDWIDE, EU or an ISO 3166-1 alpha-2 code. EEA/DACH/EMEA are refused, nomado24 does not classify them
companyarrayCompany name, exact match, case-insensitive. Aggregated postings carry no verified employer identity
countryarrayWhere the ROLE sits, ISO 3166-1 alpha-2 uppercase (DE, US)
cursorstringContinuation cursor from pagination.nextCursor. Send it ALONE (with per_page at most), never alongside filters: the cursor already carries the filter set it traverses
employment_typearrayEmployment type. 'unknown' means the field is absent in the response, not a stored value
include_totalstringWhether to compute a total. 'exact' returns a number only when the database saw the whole predicate. With a post-projection filter active (skills, seniority, salary_min/salary_max, employment_type=un…
languagestringFilter by job content language
pageinteger1-based page number, default 1
per_pageintegerResults per page, 1-25, default 20
published_afterstringRFC 3339 date-time, e.g. 2026-08-01T00:00:00Z
qstringFree-text search over job title/company/tags
salary_currencystringISO 4217. Only EUR: every salary is normalized to EUR at ingest and no conversion is performed
salary_maxnumberUpper bound in normalized ANNUAL EUR (gross)
salary_minnumberLower bound in normalized ANNUAL EUR (gross). Matches jobs whose salary interval overlaps it
seniorityarraySeniority. 'unknown' means the field is absent in the response, not a stored value
skillsarraySkill slugs, lowercase kebab-case (react, node-js)
skills_matchstringHow to combine skills. Requires skills
sortstringOne of published_desc, verified_desc, salary_asc, salary_desc. Default published_desc
sourcearrayFeed/source ids, lowercase kebab-case
verified_afterstringRFC 3339 date-time. Compares against the SAME value the response reports as lastVerifiedAt
work_arrangementarrayWork arrangement. The board serves remote and hybrid postings only, so these are the only two values

No output schema declared.

No examples provided.

Common questions

What is the Nomado24 Remote Jobs MCP server?

Nomado24 Remote Jobs is an MCP server listed in the public MCP registry as de.nomado24/jobs. Search 13,000+ remote/hybrid jobs in Germany/EU, open a posting, get market stats. Free, no auth. This page covers its hosted endpoint (https://api.nomado24.de/api/public/v1/mcp).

Is the Nomado24 Remote Jobs MCP server safe to use?

Nomado24 Remote Jobs scores 85 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 Nomado24 Remote Jobs MCP server expose?

Nomado24 Remote Jobs exposes 3 tools: search_jobs, get_job_statistics, get_job. Their descriptions and schemas cost roughly 1,052 tokens of context every time the server is loaded.

Does the Nomado24 Remote Jobs MCP server require authentication?

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

Is the Nomado24 Remote Jobs MCP server still maintained?

Nomado24 Remote Jobs is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.