Open the server as AgentStatus.
A residential node opens this server as AgentStatus and writes one record covering transport, auth, negotiate, list, and call. That is not a named-host walk.
One Connection run
AgentStatus- 01
Transport
ReachedHome internet opened the production URL.
- 02
Negotiate
ModernModern path first. Legacy only if required.
- 03
Call
FailedSession opened. tools/call did not finish.
Named hosts live on Host Compatibility.
The URL is the start. The session is the test.
Grey never changes the grade. Our time cap is our fault. Named-host rows live on Host Compatibility.
The probe path
A residential node opens this server as AgentStatus. One run writes one record.
Transport
A home internet node opens the real endpoint. This is not a cloud ping.
Authorization
Connection uses the credential configured for this server. Host Compatibility separately tests each host's auth method.
Negotiate, then list
Modern path first, older session path if required. Then tools, resources, and prompts the server advertises.
How a run is graded
Healthy, degraded, or down. Grey never changes the grade.
The grades
Healthy: every applicable step passed. Degraded: the server answered but the check could not finish. Down: no MCP session opened.
Tool checks on this run
Completes the call, returns requested data, matches the published output schema. No output schema is neutral.
What does not count against the server
Our own time cap. Empty lists the tool is allowed to return. A login mode mismatch we caused.
Outside the grade
Grey never changes the grade. A listed tool you never called does not lower Connection.
Not applicable stays grey
This server does not expose that step. Grey never changes the grade.
Listed is not called
A tool that was listed but never called does not lower Connection.
Write tools stay off
Write tools stay off unless you pin them. One run still writes one record.
FAQ
Common questions
| Question | Answer |
|---|---|
| Is Connection a named-host walk? | No. Connection opens the server as AgentStatus. Host Compatibility is the named-host walk. One Connection run writes one record. |
| Does a listed tool lower the grade if you never called it? | No. A tool that was listed but never called does not lower Connection. Write tools stay off unless you pin them. |
| What if an earlier step failed? | Not reached. We stopped. That is not a pass, and later steps stay untested. |
A 200 on the address is not a session.Keep the record of the path.
Paste the MCP URL. We open it from home internet and write one Connection record per run.
Cover your blind spots