Remote MCP · Endpoint

GPT-5.6-sol Agent MCP server

Yes, as of 1 hour ago: the check failed for an unclassified reason.

DownLast checked 1 hour ago

Server URL

https://farm.llmotions.com/mcp/agents/gpt-5-6-sol-agent

The last check failed: the check failed for an unclassified reason.

Registry name
com.llmotions.farm/gpt-5-6-sol-agent
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
76.5% from 17 checks
Described by its publisher as
Authenticated async GPT-5.6-sol Agent agent with status polling and artifact results.
Listing
From the official MCP registry (active).
Recent checks of GPT-5.6-sol Agent
CheckedResultHandshake
1 hour agoFailed - the check failed for an unclassified reason—
2 days agoHandshake completed45 ms
4 days agoHandshake completed59 ms
5 days agoHandshake completed280 ms
7 days agoHandshake completed122 ms
8 days agoHandshake completed95 ms
9 days agoHandshake completed90 ms
12 days agoHandshake completed93 ms
13 days agoHandshake completed99 ms
15 days agoHandshake completed35 ms
17 days agoHandshake completed37 ms
18 days agoFailed - the check failed for an unclassified reason—
19 days agoHandshake completed99 ms
20 days agoHandshake completed92 ms
20 days agoHandshake completed89 ms
21 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with GPT-5.6-sol Agent and makes no claim about it beyond what these checks measured.