Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
Registrable domain, e.g. example.com
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
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.
| Argument | Type | Description |
|---|---|---|
| domain* | string | Registrable domain, e.g. example.com |
{
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Registrable domain, e.g. example.com"
}
}
}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.
| Argument | 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 |
{
"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, 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.
| Argument | Type | Description |
|---|---|---|
| domain* | string | Registrable domain, e.g. example.com |
{
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Registrable domain, e.g. example.com"
}
}
}