# NessGate

> NessGate, an MCP server by nessgate.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.

- Canonical: https://www.anchorterminal.com/tools/nessgate
- Markdown: https://www.anchorterminal.com/tools/nessgate.md (~700 tokens)
- Slim: https://www.anchorterminal.com/tools/nessgate.min.md (~630 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/nessgate.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

# NessGate

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by nessgate.com (https://nessgate.com)
- Listed because: It's published in the registry under nessgate.com, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: 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 (streamable HTTP)
- Source: https://github.com/NessGate/nessgate
- GitHub stars: 2
- Registry entry updated: 2026-10-03

## Tools

- Tools it lists (3, about 1,095 tokens of context, `tools/list` without credentials, checked 2026-10-04 22:23 UTC):
  - `discover_domain`: Given a domain, read whatever it publishes at the standard machine-discovery locations (llms.txt, /.well-known/ard.json, /.well-known/agent-card.json,…
  - `connect_domain`: Given a domain AND the calling client's capabilities, return HOW the client can connect: one outcome (ready | credentials-required | incomplete | broken |…
  - `check_readiness`: Given a domain, return each connectable resource it publishes with a readiness assessment (ready | credentials-required | incomplete | broken, with the exact…
- How its tools read to an agent (0 errors, 3 warnings, 1 note, about 1,095 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):
  - warn TC16 check_readiness: no readOnlyHint or destructiveHint
  - warn TC16 connect_domain: no readOnlyHint or destructiveHint
  - warn TC16 discover_domain: no readOnlyHint or destructiveHint
  - note TC24 server: 3 of 3 tools have no outputSchema

- JSON: https://www.anchorterminal.com/api/v1/tools/nessgate.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming