Skip to content

Navad MCP server

ai.navad/jobsnavad.aistreamable-httpv1.0.0Scanned

Search verified remote jobs free, and tailor resumes and cover letters with your Navad account.

18 tools: 9 change things and 9 only read.

Tools: 0 delete, 0 irreversible, 9 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

9 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Navad MCP server can do

The Navad MCP server is published by navad.ai, a domain the MCP Registry verified. It has 18 tools. It can create or change data (9 tools: tailor_resume, write_cover_letter, check_ats_score, prepare_interview and 5 more), but cannot delete data. 9 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

18 tools

Changes things 9Claude Code: ask
  • check_ats_scoreScore how well a résumé will pass the applicant tracking system for a specific job.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Score how well a résumé will pass the applicant tracking system for a specific job. Returns the score plus the per-category breakdown, keyword analysis, and concrete fixes. Uses one unit of the monthly ATS allowance. Pass generated_resume_id to score a tailored résumé rather than a stored one.
  • finish_cv_uploadComplete a CV upload started by start_cv_upload, after the bytes have been PUT to the upload URL.No findings

    Why it is in this group

    • The name "finish_cv_upload" says "upload": a word for a change.
    Description, as the server wrote it
    Complete a CV upload started by start_cv_upload, after the bytes have been PUT to the upload URL. The server verifies the file really is a PDF here, so a failure at this step usually means the upload did not land.
  • prepare_interviewGenerate likely interview questions, suggested answers, company research, and weak spots for a specific job, and return them so you can run a mock interview with the user.No findings

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    Generate likely interview questions, suggested answers, company research, and weak spots for a specific job, and return them so you can run a mock interview with the user. PREMIUM PLAN ONLY — on Free and Pro this returns a limit error prompting an upgrade, so check get_usage first if unsure.
  • start_apply_with_aiStart a background run producing a tailored résumé, a cover letter, and an ATS score for one job.No findings

    Why it is in this group

    • The name "start_apply_with_ai" says "start": a word for a change.
    Description, as the server wrote it
    Start a background run producing a tailored résumé, a cover letter, and an ATS score for one job. Preferred over calling the individual tools when the user wants more than one artifact: it returns immediately and cannot time out. Spends allowance across each requested feature. Returns an application_run_id to poll.
  • start_cv_uploadGet a short-lived URL to upload a PDF CV to.No findings

    Why it is in this group

    • The name "start_cv_upload" says "start": a word for a change.
    Description, as the server wrote it
    Get a short-lived URL to upload a PDF CV to. The file does NOT pass through this tool — you upload the bytes yourself with an HTTP PUT, then call finish_cv_upload. Requires a token with profile access, and a client that can read local files. If you cannot do that, send the user to their profile page instead of guessing.
  • tailor_resumeRewrite the user's résumé for a specific job.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Rewrite the user's résumé for a specific job. Uses one unit of the monthly résumé allowance. Takes 30–120 seconds. Returns the tailored résumé text — show it to the user and refine it with them in conversation rather than regenerating, since each call costs another unit. If you also want a cover letter and ATS score, call start_apply_with_ai instead: it runs in the background and cannot time out.
  • update_job_preferencesChange the preferences that drive job matching — desired roles, seniority, skills, salary range, locations, timezone flexibility.No findings

    Why it is in this group

    • The name "update_job_preferences" says "update": a word for a change.
    Description, as the server wrote it
    Change the preferences that drive job matching — desired roles, seniority, skills, salary range, locations, timezone flexibility. Only the fields you pass are changed. Requires a token with profile access. Read them with get_profile first and confirm the change with the user before writing.
  • update_profileChange the user's display name.No findings

    Why it is in this group

    • The name "update_profile" says "update": a word for a change.
    Description, as the server wrote it
    Change the user's display name. Requires a token with profile access. Only call this when the user explicitly asks — never to 'correct' a name you think looks wrong.
  • write_cover_letterWrite a cover letter for a specific job from the user's résumé.No findings

    Why it is in this group

    • The name "write_cover_letter" says "write": a word for a change.
    Description, as the server wrote it
    Write a cover letter for a specific job from the user's résumé. Uses one unit of the monthly cover-letter allowance. Takes 30–120 seconds. Returns the letter text — refine it with the user in conversation rather than regenerating. If one already exists for this job it is returned without spending allowance.
Only reads 9Show 9 read-only tools
  • get_application_run_statusPoll a run started by start_apply_with_ai.No findings

    Why it is in this group

    • The name "get_application_run_status" says "get": a word for reading.
    Description, as the server wrote it
    Poll a run started by start_apply_with_ai. Report per-stage state, not just the overall status — a run can finish 'completed' with one stage failed, and that is normal.
  • get_jobFetch one job posting in full, including its description.No findings

    Why it is in this group

    • The name "get_job" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one job posting in full, including its description. Accepts either the job's UUID or its URL slug. Free; no account needed.
  • get_job_ai_toolsFor one job, report which AI artifacts already exist (tailored résumé, cover letter, interview prep, ATS score).No findings

    Why it is in this group

    • The name "get_job_ai_tools" says "get": a word for reading.
    Description, as the server wrote it
    For one job, report which AI artifacts already exist (tailored résumé, cover letter, interview prep, ATS score). Costs nothing. Use it to avoid regenerating something the user already has, and to retrieve a result after a generation tool timed out.
  • get_profileRead the signed-in user's name, plan, and job-search preferences (desired roles, seniority, skills, salary, locations).No findings

    Why it is in this group

    • The name "get_profile" says "get": a word for reading.
    Description, as the server wrote it
    Read the signed-in user's name, plan, and job-search preferences (desired roles, seniority, skills, salary, locations). Use this before searching so results reflect what they actually want, and to explain why a posting does or does not match. No allowance is spent.
  • get_usageShow how much of this month's AI allowance is left, per feature.No findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.
    Description, as the server wrote it
    Show how much of this month's AI allowance is left, per feature. Call this before running several AI tools in a row, and to explain a limit error rather than retrying into it.
  • list_job_locationsList the regions and countries that can be passed to search_jobs `location`.No findings

    Why it is in this group

    • The name "list_job_locations" says "list": a word for reading.
    Description, as the server wrote it
    List the regions and countries that can be passed to search_jobs `location`. Call this before filtering by location rather than guessing values.
  • list_my_resumesList the user's stored résumés and their IDs.No findings

    Why it is in this group

    • The name "list_my_resumes" says "list": a word for reading.
    Description, as the server wrote it
    List the user's stored résumés and their IDs. Call this before start_apply_with_ai, which requires a resume_id. Does not return file contents or download links.
  • search_jobsSearch Navad's remote job listings by keyword, location, seniority, salary, and recency.No findings

    Why it is in this group

    • The name "search_jobs" says "search": a word for reading.
    Description, as the server wrote it
    Search Navad's remote job listings by keyword, location, seniority, salary, and recency. Returns summaries without full descriptions — call get_job for a specific posting's description. Free; no account needed. Always cite the returned `url` when telling the user about a job.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:18 UTC, unchanged since Nov 21, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.navad.ai/.well-known/oauth-protected-resource
Authorization servers
https://navad.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.navad.ai/mcp: tools/list returned 18 tools to an anonymous client, including tailor_resume (write), write_cover_letter (write), check_ats_score (write), prepare_interview (write), start_apply_with_ai (write) and 4 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http jobs https://mcp.navad.ai/mcp
claude mcp add --transport http jobs https://mcp.navad.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jobs__search_jobs",
      "mcp__jobs__get_job",
      "mcp__jobs__list_job_locations",
      "mcp__jobs__get_related_jobs",
      "mcp__jobs__get_usage",
      "mcp__jobs__list_my_resumes",
      "mcp__jobs__get_job_ai_tools",
      "mcp__jobs__get_application_run_status",
      "mcp__jobs__get_profile"
    ],
    "ask": [
      "mcp__jobs__tailor_resume",
      "mcp__jobs__write_cover_letter",
      "mcp__jobs__check_ats_score",
      "mcp__jobs__prepare_interview",
      "mcp__jobs__start_apply_with_ai",
      "mcp__jobs__update_profile",
      "mcp__jobs__update_job_preferences",
      "mcp__jobs__start_cv_upload",
      "mcp__jobs__finish_cv_upload"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jobs. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.navad/jobs/verify?hash=d2fcd0477aeb93333d8195284ac5b58fb0ff67ba3534bfeadd4f775bb4d5c26f" | jq -e '.changed == false'

Pinned hash d2fcd0477aeb, from Nov 21, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.navad/jobs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.navad/jobs
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.navad/jobs.svg)](https://radar.anlyon.com/servers/ai.navad/jobs)

Source: MCP Registry. Synced Nov 21, 2026, 12:17 UTC.

Navad MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Navad MCP server safe?

No scan can promise that. What its definitions show: 18 tools, 9 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Navad MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Navad MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Navad MCP server have?

18 tools: 9 write, 9 read. tailor_resume, write_cover_letter, check_ats_score, prepare_interview, start_apply_with_ai, update_profile, update_job_preferences, start_cv_upload and 10 more.

Does the Navad MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Navad MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Navad MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.