All servers · APIs & integrations · AI models & agents · Maps, location & weather
NessGate
com.nessgate/nessgate · v1.22.2
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.
Connect
streamable-http · https://nessgate.com/mcp
claude mcp add --transport http nessgate https://nessgate.com/mcp{
"mcpServers": {
"nessgate": {
"url": "https://nessgate.com/mcp"
}
}
}Tools as reported by the server
discover_domainGiven 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 thconnect_domainGiven 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 OAutcheck_readinessGiven 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.
Repository · JSON · Text for agents · Registry updated 2026-10-04