mcp-registry/com.nessgate/nessgate · v1.22.2
As of 2026-10-23 06:52 UTC, the Nessgate MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Universal resolver for the agentic web: give a domain, get one normalized discovery answer.
Claude Code
claude mcp add --transport http nessgate-mcp-server https://nessgate.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"nessgate-mcp-server": {
"type": "http",
"url": "https://nessgate.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.nessgate%2Fnessgate/fixes
{
"name": "check_readiness",
"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"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Check how ready a domain's endpoints are to connect to"
}{
"name": "connect_domain",
"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 ",
"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"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get a connection plan for this client"
}{
"name": "discover_domain",
"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"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Resolve a domain's machine-readable resources"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.nessgate/nessgate"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.nessgate/nessgate"}) over MCP.
connect_domain ~410 tokensdiscover_domain ~180 tokenscheck_readiness ~137 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.nessgate%2Fnessgate?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.nessgate%2Fnessgate?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.nessgate%2Fnessgate.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.nessgate%2Fnessgate.svg :target: https://glimind.com/server/mcp-registry%2Fcom.nessgate%2Fnessgate?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1f84c26a9ff1aaee…, first seen 2026-10-17, included at leaf 6990 of 50,596. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable web servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 06:52 UTC, the Nessgate MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Nessgate MCP server advertises 3 tools, including check_readiness, connect_domain, discover_domain.
Point your MCP client at this streamable-http endpoint: https://nessgate.com/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.