Skip to content

NessGate

by nessgate.com · remote · no sign-in to list tools · v1.22.2 · published by com.nessgate

Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.

Changes · 3
CompareRegistry entry

3 tools: 3 change things.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http nessgate https://nessgate.com/mcp

Findings

Matches of fixed checks, with the text they matched.

2 info

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 3Claude Code: ask
  • check_readinessGiven a domain, return each connectable resource it publishes with a readiness assessment (ready | credentials-required | incomplete | broken, with the exact missing field) read fr…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...es with a readiness assessment (ready | credentials-required | incomplete | broken, with th..."

      What this check looks for
    Description, as the server wrote 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.
  • connect_domainGiven a domain AND the calling client's capabilities, return HOW the client can connect: one outcome (ready | credentials-required | incomplete | broken | no-compatible-method) wit…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...lient can connect: one outcome (ready | credentials-required | incomplete | broken | no-com..."

      What this check looks for
    Description, as the server wrote it
    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.
  • discover_domainGiven 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-…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote 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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.22.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http nessgate https://nessgate.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__nessgate__discover_domain",
      "mcp__nessgate__connect_domain",
      "mcp__nessgate__check_readiness"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as nessgate. Review it before you use it.