Is the Nessgate MCP server down?

mcp-registry/com.nessgate/nessgate · v1.22.2

healthy
Last checked 2026-10-23 06:52 UTC · handshake 110ms

As of 2026-10-23 06:52 UTC, the Nessgate MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

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

Universal resolver for the agentic web: give a domain, get one normalized discovery answer.

Install Nessgate MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http nessgate-mcp-server https://nessgate.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "nessgate-mcp-server": {
      "type": "http",
      "url": "https://nessgate.com/mcp"
    }
  }
}

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

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 3 tool(s); ~727 tokens of tool definitions.
Scores higher than 47% of 15,579 MCP servers Glimind has audited.
Its tool list costs an agent ~727 tokens per session — lighter than 85% of servers.
85 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability96

What to fix (3)

3 of 3 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_readiness, connect_domain, discover_domain

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 →

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 3 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%2Fcom.nessgate%2Fnessgate/fixes

check_readiness 1 change
{
  "name": "check_readiness",
  "description": "Given a domain, return each connectable resource it publishes with a readiness assessment (ready | credentials-required | incomplete | broken, with the exact missing field) read from the service's own metadata. Client-agnostic; read-only. Use connect_domain when you know the client's capabilities.",
  "inputSchema": {
    "type": "object",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "description": "Registrable domain, e.g. example.com"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check how ready a domain's endpoints are to connect to"
}
connect_domain 1 change
{
  "name": "connect_domain",
  "description": "Given a domain AND the calling client's capabilities, return HOW the client can connect: one outcome (ready | credentials-required | incomplete | broken | no-compatible-method) with a connection plan (protocol, endpoint, transport, version, and the auth metadata the service published — e.g. the OAuth authorize/token endpoints and scopes), or the exact missing field when the service under-publishes. Deterministic matching, no scores. Read-only; credentials stay with the caller and are never sent ",
  "inputSchema": {
    "type": "object",
    "required": [
      "domain"
    ],
    "properties": {
      "client": {
        "type": "object",
        "properties": {
          "prefer": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Optional cross-protocol tie-break order."
          },
          "supports": {
            "type": "array",
            "items": {
              "type": "object",
              "required": [
                "protocol"
              ],
              "properties": {
                "auth": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                },
                "protocol": {
                  "type": "string",
                  "description": "e.g. mcp, openapi, a2a"
                },
                "versions": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                },
                "transports": {
                  "type": "array",
                  "items": {
                    "type": "string"
                  }
                }
              }
            },
            "description": "Protocols the client speaks, each optionally narrowing versions/transports/auth."
          }
        },
        "description": "The calling client's capabilities. Omit a dimension to accept any. If client/supports is omitted entirely, a broad default (mcp, openapi, a2a) is assumed and the response carries clientAssumed:true."
      },
      "domain": {
        "type": "string",
        "description": "Registrable domain, e.g. example.com"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Get a connection plan for this client"
}
discover_domain 1 change
{
  "name": "discover_domain",
  "description": "Given a domain, read whatever it publishes at the standard machine-discovery locations (llms.txt, /.well-known/ard.json, /.well-known/agent-card.json, /.well-known/api-catalog, ai-info.json, openapi.json, and more) and return one normalized answer. Each resource keeps a sourceUrl pointing back to the domain so the caller can verify. NessGate reads the domain live and stores no discovered domain or resource data; it makes no ownership or safety claim.",
  "inputSchema": {
    "type": "object",
    "required": [
      "domain"
    ],
    "properties": {
      "domain": {
        "type": "string",
        "description": "Registrable domain, e.g. example.com"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Resolve a domain's machine-readable resources"
}

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/com.nessgate/nessgate"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.nessgate/nessgate"}) 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%2Fcom.nessgate%2Fnessgate.svg)](https://glimind.com/server/mcp-registry%2Fcom.nessgate%2Fnessgate?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.nessgate%2Fnessgate?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.nessgate%2Fnessgate.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.nessgate%2Fnessgate.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.nessgate%2Fnessgate?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:1f84c26a9ff1aaee…, first seen 2026-10-17, included at leaf 6990 of 50,596. Version history · verify what your client received.

Tools (3)

Compare: most reliable knowledge servers · most reliable web 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 Nessgate MCP server down right now?

As of 2026-10-23 06:52 UTC, the Nessgate MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Nessgate MCP server provide?

Nessgate MCP server advertises 3 tools, including check_readiness, connect_domain, discover_domain.

How do I install Nessgate MCP server?

Point your MCP client at this streamable-http endpoint: https://nessgate.com/mcp

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

Glimind scanned all 3 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 Nessgate 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