NessGate

Name: NessGate
Author: com.nessgate

MCP serverMCP

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

by com.nessgaterepository ↗v1.22.2

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"nessgate","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability97/97 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	15 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
11 h ago	mcp initialize	ok	200	19 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
17 h ago	mcp initialize	ok	200	76 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
23 h ago	mcp initialize	ok	200	33 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
30 h ago	mcp initialize	ok	200	29 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	35 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	14 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	11 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
2 d ago	mcp initialize	ok	200	19 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools
3 d ago	mcp initialize	ok	200	18 ms	server nessgate 1.22.2 · protocol 2025-06-18 · 3 tools

Tools observed via MCP handshake

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, /.well-kn
connect_domain — Given a domain AND the calling client's capabilities, return HOW the client can connect: one outcome (ready | credentials-required | incomplete | broken | no-co
check_readiness — Given a domain, return each connectable resource it publishes with a readiness assessment (ready | credentials-required | incomplete | broken, with the exact mi

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.nessgate/nessgate

first seen 26 d ago · fetched 20 h agoopen ↗

Field history (10 recent events)

4 d ago · declared · summary → "Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans."
4 d ago · declared · description → "Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans."
4 d ago · declared · version → "1.22.2"
24 d ago · declared · version → "1.6.0"
26 d ago · declared · version → "1.2.0"
26 d ago · declared · summary → "Universal resolver for the agentic web: give a domain, get one normalized discovery answer."
26 d ago · declared · protocols → ["mcp"]
26 d ago · declared · description → "Universal resolver for the agentic web: give a domain, get one normalized discovery answer."
26 d ago · declared · publisherName → "com.nessgate"
26 d ago · declared · repoUrl → "https://github.com/NessGate/nessgate"

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from