Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.
Facts
- MCP registry
com.nessgate/nessgate· 1.22.0- Endpoint
https://nessgate.com/mcp- GitHub stars
- 2
- Registry entry
- updated 3 Oct 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under nessgate.com, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 3 · about 1,087 tokens of context · checked 23 hours ago
| Tool | What it does | Hint |
|---|---|---|
discover_domainResolve a domain's machine-readable resources | 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… | |
connect_domainGet a connection plan for this client | 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,… | |
check_readinessCheck how ready a domain's endpoints are to connect to | 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.… |
What https://nessgate.com/mcp answered to tools/list, asked without credentials. answered without the initialize handshake. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 3 warnings · 1 note
- warnTC16check_readinessno readOnlyHint or destructiveHint
- warnTC16connect_domainno readOnlyHint or destructiveHint
- warnTC16discover_domainno readOnlyHint or destructiveHint
- noteTC24server3 of 3 tools have no outputSchema
The checks from /check and anchor check, run each day on the list above: about 1,087 tokens of definitions. Not part of the score yet. Check your own server.