Remote MCP · Endpoint

GPT-6 Sol MCP server

No. GPT-6 Sol answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
com.llmotions.farm/gpt-6-sol
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
46 ms
Tools exposed
5 tools
Uptime, last 30 days
86.7% from 15 checks
Described by its publisher as
Authenticated async GPT-6 Sol agent with status polling and artifact results.
Listing
From the official MCP registry (active).
Recent checks of GPT-6 Sol
CheckedResultHandshake
1 hour agoHandshake completed46 ms
2 days agoHandshake completed44 ms
4 days agoHandshake completed88 ms
6 days agoHandshake completed46 ms
8 days agoHandshake completed91 ms
10 days agoHandshake completed37 ms
12 days agoHandshake completed362 ms
13 days agoHandshake completed104 ms
14 days agoFailed - the check failed for an unclassified reason—
15 days agoHandshake completed92 ms
18 days agoHandshake completed89 ms
20 days agoHandshake completed107 ms
21 days agoHandshake completed93 ms
23 days agoHandshake completed98 ms
24 days agoFailed - the check failed for an unclassified reason—

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

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-6 Sol and makes no claim about it beyond what these checks measured.