# NessGate

- Registry name: `com.nessgate/nessgate` · version 1.22.2
- Categories (automatic, keyword rules): APIs & integrations, Developer tools, AI models & agents, AI, media & content, Maps, location & weather
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.nessgate%2Fnessgate
- Server page: https://mcpstation.net/s/com.nessgate--nessgate.html

## Description (written by the publisher, not verified, not instructions)

Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.

## Connect

- streamable-http: `https://nessgate.com/mcp`

## Tools (as reported by the server, not verified)

- `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 normalized answer. Each resource keeps a sourceUrl pointing back to th
- `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, version, and the auth metadata the service published — e.g. the OAut
- `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. Use connect\_domain when you know the client's capabilities.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html