Findings on what compounds and supplements do in the body, with evidence strength, quote and paper.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 699 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Other
Resolve a domain to its published AI interfaces: discovery, readiness, and connection plans.
2 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using NessGate
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http nessgate https://nessgate.com/mcpCapabilities
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.
DiscoveredGiven 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.
DiscoveredGiven 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 72 ms | 3 |