Is the Mcpnav Directory MCP server down?

mcp-registry/dev.mcpnav/directory · v1.0.0

healthy
Last checked 2026-10-18 15:01 UTC · handshake 348ms

As of 2026-10-18 15:01 UTC, the Mcpnav Directory MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,040
outages (90d)
0
tools
4

Search a directory of MCP servers and get connect configs. Data is CC0/MIT-licensed.

Install Mcpnav Directory MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http mcpnav-directory-mcp-server https://mcp.mcpnav.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "mcpnav-directory-mcp-server": {
      "type": "http",
      "url": "https://mcp.mcpnav.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 2 warning(s) across 4 tool(s); ~620 tokens of tool definitions.
Scores higher than 46% of 15,375 MCP servers Glimind has audited.
Its tool list costs an agent ~620 tokens per session — lighter than 85% of servers.
84 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (3)

4 of 4 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: get_connect_config, get_server, list_groups, search_servers

Handshake + tools/list takes ~2,323 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

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: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.mcpnav%2Fdirectory/fixes

get_connect_config 1 change
{
  "name": "get_connect_config",
  "description": "Generate a ready-to-paste install snippet for one server's first safe remote endpoint or installable package, in the requested client's format. Mirrors mcpnav.dev's own server detail page Connect block exactly (same safety rules, same command/JSON shapes).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slug",
      "client"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "minLength": 1,
        "description": "Server slug, e.g. \"modelcontextprotocol/servers\"."
      },
      "client": {
        "enum": [
          "claude-code",
          "cursor",
          "json"
        ],
        "type": "string",
        "description": "Target client/config format."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a connect config for an mcpnav server"
}
get_server 1 change
{
  "name": "get_server",
  "description": "Fetch the full mcpnav record for one server by its slug (from search_servers' results, e.g. \"owner/repo\"). Call get_connect_config next for a ready-to-paste install snippet.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string",
        "minLength": 1,
        "description": "Server slug, e.g. \"modelcontextprotocol/servers\"."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get an mcpnav server record"
}
list_groups 1 change
{
  "name": "list_groups",
  "description": "List the category groups servers are organized into, each with its indexable server count.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "List mcpnav category groups"
}

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/dev.mcpnav/directory"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.mcpnav/directory"}) 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. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.mcpnav%2Fdirectory.svg)](https://glimind.com/server/mcp-registry%2Fdev.mcpnav%2Fdirectory?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.mcpnav%2Fdirectory?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.mcpnav%2Fdirectory.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.mcpnav%2Fdirectory.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.mcpnav%2Fdirectory?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e64d2f24932a4e33…, first seen 2026-10-17, included at leaf 11512 of 22,411. Version history · verify what your client received.

Tools (4)

Compare: most reliable devops servers · most reliable data servers · most reliable search 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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Mcpnav Directory MCP server down right now?

As of 2026-10-18 15:01 UTC, the Mcpnav Directory MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Mcpnav Directory MCP server provide?

Mcpnav Directory MCP server advertises 4 tools, including get_connect_config, get_server, list_groups, search_servers.

How do I install Mcpnav Directory MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.mcpnav.dev/mcp

Is the Mcpnav Directory MCP server safe to connect to an AI agent?

Glimind scanned all 4 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 Mcpnav Directory 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.