NessGate
mcp remote · streamable-http · v1.6.0 · source: crawl
https://nessgate.com/mcp
https://github.com/NessGate/nessgate
Universal resolver for the agentic web: give a domain, get one normalized discovery answer.
Works
100
Verified Oct 31, 2026 · p50 416 ms · p95 466 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'nessgate' |
| tools_listed | 15 | pass | 3 tools |
| schema_complete | 15 | pass | 3 of 3 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 416 ms |
| latency_p95 | 5 | pass | p95 466 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (3)
| Name | Description | Schema |
|---|---|---|
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-known/api-catalog, ai-info.json, openapi.j | typed |
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-compatible-method) with a connection plan | typed |
check_readiness | 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 | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/com-nessgate-nessgate)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.