NessGate MCP server

Which servers in the official MCP registry are NessGate's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to NessGate

Whose server it is

Registry namecom.nessgate/nessgateverified in the MCP registry

The registry name sits under nessgate.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools3
Server calls itselfnessgate
Server version1.22.2
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 16 ms.

Tools it offers3 tools · read 2026-10-14

discover_domain
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…
connect_domain
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…
check_readiness
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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

OpenAPI spec

4 paths, read 2026-10-14. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.