de.nomado24/jobs

Est-ce que de.nomado24/jobs est sûr ?

Au dernier audit MCP Hub, le serveur MCP « de.nomado24/jobs » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 3 outils

• get_job≈ 244 tokens

  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).

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Job id as returned by search_jobs ('job_<slug>'). A bare slug is also accepted

  Exemple d'appel

  {"name": "get_job", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_job_statistics≈ 97 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_job_statistics", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_jobs≈ 1364 tokens

  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. Structured pagination.total is currently null (totalRelation 'not_computed') for every query, because a current-text on-site-only serving gate cannot be counted accurately by the database. A null total is deliberate, not an error.

  Paramètres, retour & exemple (21)

  Paramètres

  • q · string · optionnel
    Free-text search over job title/company/tags
  • page · integer · optionnel
    1-based page number, default 1
  • sort · string · optionnel
    One of published_desc, verified_desc, salary_asc, salary_desc. Default published_desc
  • cursor · string · optionnel
    Continuation cursor from pagination.nextCursor. Send it ALONE (with per_page at most), never alongside filters: the cursor already carries the filter set it traverses
  • skills · array · optionnel
    Skill slugs, lowercase kebab-case (react, node-js)
  • source · array · optionnel
    Feed/source ids, lowercase kebab-case
  • company · array · optionnel
    Company name, exact match, case-insensitive. Aggregated postings carry no verified employer identity
  • country · array · optionnel
    Where the ROLE sits, ISO 3166-1 alpha-2 uppercase (DE, US)
  • language · string · optionnel · de | en | fr
    Filter by job content language
  • per_page · integer · optionnel
    Results per page, 1-25, default 20
  • seniority · array · optionnel
    Seniority. 'unknown' means the field is absent in the response, not a stored value
  • salary_max · number · optionnel
    Upper bound in normalized ANNUAL EUR (gross)
  • salary_min · number · optionnel
    Lower bound in normalized ANNUAL EUR (gross). Matches jobs whose salary interval overlaps it
  • skills_match · string · optionnel · any | all
    How to combine skills. Requires skills
  • include_total · string · optionnel · none | estimated | exact
    Requested total mode (none, estimated, exact). Totals are currently withheld for every structured search: a current-text on-site-only serving gate is not visible to the database count, even without a named filter. The response reports total: null and totalRelation: 'not_computed' for all three modes.
  • verified_after · string · optionnel
    RFC 3339 date-time. Compares against the SAME value the response reports as lastVerifiedAt
  • employment_type · array · optionnel
    Employment type. 'unknown' means the field is absent in the response, not a stored value
  • published_after · string · optionnel
    RFC 3339 date-time, e.g. 2026-08-01T00:00:00Z
  • salary_currency · string · optionnel
    ISO 4217. Only EUR: every salary is normalized to EUR at ingest and no conversion is performed
  • applicant_region · array · optionnel
    Where a CANDIDATE may be: WORLDWIDE, EU or an ISO 3166-1 alpha-2 code. EEA/DACH/EMEA are refused, nomado24 does not classify them
  • work_arrangement · array · optionnel
    Work arrangement. The board serves remote and hybrid postings only, so these are the only two values

  Exemple d'appel

  {"name": "search_jobs", "arguments": {"q": "texte", "page": 1, "sort": "texte", "cursor": "texte", "skills": [], "source": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://api.nomado24.de/api/public/v1/mcp