protogrid

Search / com.nessgate/nessgate

NessGate

R0· no sign-in

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

v1.22.2 · active · repository · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust97of 100
Uptime, 30 days98%
Latency p50158 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "nessgate": {
      "type": "http",
      "url": "https://nessgate.com/mcp"
    }
  }
}
claude mcp add --transport http nessgate https://nessgate.com/mcp
[mcp_servers.nessgate]
url = "https://nessgate.com/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nessgate": {
      "type": "remote",
      "url": "https://nessgate.com/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "nessgate": {
      "type": "http",
      "url": "https://nessgate.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=nessgate&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbmVzc2dhdGUuY29tL21jcCJ9"
}
{
  "servers": {
    "nessgate": {
      "type": "http",
      "url": "https://nessgate.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "nessgate": {
      "httpUrl": "https://nessgate.com/mcp"
    }
  }
}
extensions:
  "nessgate":
    enabled: true
    name: "nessgate"
    type: streamable_http
    uri: "https://nessgate.com/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: discover_domain (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); connect_domain (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); check_readiness (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 627 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changes5 tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 627 tokens to load them all · tool set 19963ef365eb · tools last changed 2026-10-04 · checked 2026-10-19 10:52 UTC

Tool changes

  • discover_domainchangeddescription
    before

    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 nothing; it makes no ownership or safety claim.

    after · 95% of words in common

    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.

  • check_readinesschangeddescription
    before

    Given a domain, return each connectable resource it publishes with a readiness assessment (ready | credentials-required | incomplete, 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.

    after · 97% of words in common

    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_domainchangeddescription
    before

    Given a domain AND the calling client's capabilities, return HOW the client can connect: one outcome (ready | credentials-required | incomplete | 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.

    after · 98% of words in common

    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.

  • check_readinessadded

    Given a domain, return each connectable resource it publishes with a readiness assessment (ready | credentials-required | incomplete, 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_domainadded

    Given a domain AND the calling client's capabilities, return HOW the client can connect: one outcome (ready | credentials-required | incomplete | 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.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 97 / 100

provenance90
liveness99
freshness100
hygiene100

+repository +namespace-matches-repo +dns-namespace +reachable +uptime-98% +updated-15d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://nessgate.com/mcp streamable-httpnoneyes98%158 ms2025-11-25, 2025-06-18, 2025-03-262026-10-19

Tools (3)

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 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) 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-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.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.nessgate/nessgate",
  "title": "NessGate",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://nessgate.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.22.2",
  "repository": {
    "url": "https://github.com/NessGate/nessgate",
    "source": "github"
  },
  "description": "Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans."
}