Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.
Connect Remote server
claude mcp add --transport http nessgate https://nessgate.com/mcp
{
"mcpServers": {
"nessgate": {
"url": "https://nessgate.com/mcp"
}
}
}
{
"servers": {
"nessgate": {
"type": "http",
"url": "https://nessgate.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://nessgate.com/mcp
Tools 3 found in our last check
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 sourceUr…
connect_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 publ…
check_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 cli…
Details
| Endpoint | https://nessgate.com/mcp (Streamable HTTP) |
| First published | 4 Oct 2026 |
| Last updated | 4 Oct 2026 |
| Registry name | com.nessgate/nessgate |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
