Is the Navad MCP server down?

mcp-registry/ai.navad/jobs · v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 16:09 UTC · handshake 434ms

As of 2026-11-22 16:09 UTC, the Navad MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
129
outages (90d)
0
tools
18

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

Point your MCP client at this streamable-http endpoint: https://mcp.navad.ai/mcp

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 3 warning(s) across 18 tool(s); ~3,499 tokens of tool definitions.
Scores higher than 19% of 27,649 MCP servers Glimind has audited.
Its tool list costs an agent ~3,499 tokens per session — more than 65% of servers.
77 → 77 since 2026-11-21
no tool-poisoning patterns
Descriptions78
Safety hints7
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (4)

18 of 18 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_ats_score, finish_cv_upload, get_application_run_status, get_job, get_job_ai_tools and 13 more

8 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: get_related_jobs, search_jobs, update_job_preferences

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: update_job_preferences, update_profile, write_cover_letter

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 16 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.navad%2Fjobs/fixes

check_ats_score 1 change
{
  "name": "check_ats_score",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "job_id"
    ],
    "properties": {
      "force": {
        "type": "boolean",
        "description": "Regenerate even if a result already exists, or if the match score is low. Spends allowance. Only set this when the user asks."
      },
      "job_id": {
        "type": "string",
        "format": "uuid",
        "description": "UUID of the job posting."
      },
      "resume_id": {
        "type": "string",
        "format": "uuid",
        "description": "Which stored résumé to use. Omit to use the default. Call list_my_resumes to see the options."
      },
      "generated_resume_id": {
        "type": "string",
        "format": "uuid",
        "description": "Score a tailored résumé produced by tailor_resume instead of a stored one."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Score a résumé against a job's ATS"
}
finish_cv_upload 1 change
{
  "name": "finish_cv_upload",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "storage_path",
      "file_size"
    ],
    "properties": {
      "label": {
        "type": "string",
        "default": "My CV",
        "maxLength": 100,
        "minLength": 1,
        "description": "A name for this CV, e.g. \"Backend CV\"."
      },
      "file_size": {
        "type": "integer",
        "description": "Size of the uploaded file in bytes.",
        "exclusiveMinimum": 0
      },
      "storage_path": {
        "type": "string",
        "minLength": 1,
        "description": "The storage_path returned by start_cv_upload."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Register an uploaded CV"
}
get_application_run_status 1 change
{
  "name": "get_application_run_status",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "application_run_id"
    ],
    "properties": {
      "application_run_id": {
        "type": "string",
        "format": "uuid",
        "description": "The id returned by start_apply_with_ai. Not a job posting id."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check an application kit run"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.navad/jobs"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.navad/jobs"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fai.navad%2Fjobs.svg)](https://glimind.com/server/mcp-registry%2Fai.navad%2Fjobs?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fai.navad%2Fjobs?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fai.navad%2Fjobs.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:533f7214edd9f45e…, first seen 2026-11-21, included at leaf 374801 of 384,562. Version history · verify what your client received.

Tools (18)

Compare: most reliable ml servers · most reliable files servers · most reliable devops servers · most reliable data servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Navad MCP server down right now?

As of 2026-11-22 16:09 UTC, the Navad MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Navad MCP server provide?

Navad MCP server advertises 18 tools, including check_ats_score, finish_cv_upload, get_application_run_status, get_job, get_job_ai_tools.

How do I install Navad MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.navad.ai/mcp

Is the Navad MCP server safe to connect to an AI agent?

Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Navad MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve