NessGate is an MCP server published by com.nessgate, hosted at nessgate.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 3 tools, including discover_domain, connect_domain, check_readiness.
Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.
Nothing else in the archive shares these values.
Inferred from the host name and headers: what a server runs on, not who runs it.
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 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.
| Parameter | Type | Description |
|---|---|---|
| domain * | string | Registrable domain, e.g. example.com |
{
"name": "discover_domain",
"title": "Resolve a domain's machine-readable resources",
"description": "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 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.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Registrable domain, e.g. example.com"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
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 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.
| Parameter | Type | Description |
|---|---|---|
| client | object | The calling client's capabilities. Omit a dimension to accept any. If client/supports is omitted entirely, a broad default (mcp, openapi, a2a) is assumed and the response carries clientAssumed:true. |
| domain * | string | Registrable domain, e.g. example.com |
{
"name": "connect_domain",
"title": "Get a connection plan for this client",
"description": "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 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.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"client": {
"type": "object",
"properties": {
"prefer": {
"type": "array",
"items": {
"type": "string"
},
"description": "Optional cross-protocol tie-break order."
},
"supports": {
"type": "array",
"items": {
"type": "object",
"required": [
"protocol"
],
"properties": {
"auth": {
"type": "array",
"items": {
"type": "string"
}
},
"protocol": {
"type": "string",
"description": "e.g. mcp, openapi, a2a"
},
"versions": {
"type": "array",
"items": {
"type": "string"
}
},
"transports": {
"type": "array",
"items": {
"type": "string"
}
}
}
},
"description": "Protocols the client speaks, each optionally narrowing versions/transports/auth."
}
},
"description": "The calling client's capabilities. Omit a dimension to accept any. If client/supports is omitted entirely, a broad default (mcp, openapi, a2a) is assumed and the response carries clientAssumed:true."
},
"domain": {
"type": "string",
"description": "Registrable domain, e.g. example.com"
}
}
}
}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.
| Parameter | Type | Description |
|---|---|---|
| domain * | string | Registrable domain, e.g. example.com |
{
"name": "check_readiness",
"title": "Check how ready a domain's endpoints are to connect to",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Registrable domain, e.g. example.com"
}
}
}
}Three read-only tools. discover_domain: what a domain publishes (the raw normalized list). connect_domain: given a domain AND your client's capabilities, HOW to connect — one outcome (ready | credentials-required | incomplete | broken | no-compatible-method) with a connection plan, or the exact missing field. check_readiness: per-endpoint readiness for a domain, client-agnostic. All read the domain live, store no discovered domain or resource data, make no ownership/safety claim; credentials stay with the caller.
Names, descriptions and schemas were written by the server and are shown as data.