NessGate
com.nessgate/nessgateVersion 1.22.2Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.
Status
Responds252 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:07 UTC
- Latency
- 252 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://nessgate.com/mcpResponds252 msNo sign-in
Claude Code
claude mcp add --transport http nessgate https://nessgate.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: nessgate
Remote MCP server URL: https://nessgate.com/mcpCursor
{
"mcpServers": {
"nessgate": {
"url": "https://nessgate.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"nessgate","type":"http","url":"https://nessgate.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
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 client's capabilities. | Not declared | Not declared | Not declared | Not declared |
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 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 to NessGate. | Not declared | Not declared | Not declared | Not declared |
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 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. | Not declared | Not declared | Not declared | Not declared |
Details
- Registry status
- Active
- Published
- Oct 4, 2026
- Updated
- Oct 4, 2026
- Website
- Not given
- Categories
- Uncategorized
- GDPR
- Not declared