Remote MCP · Endpoint

GPT-6 Astra MCP server

No. GPT-6 Astra answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
com.llmotions.farm/gpt-6-astra
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
42 ms
Tools exposed
5 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Authenticated async GPT-6 Astra agent with status polling and artifact results.
Listing
From the official MCP registry (active).
Recent checks of GPT-6 Astra
CheckedResultHandshake
19 minutes agoHandshake completed42 ms
9 days agoHandshake completed69 ms
9 days agoHandshake completed44 ms
11 days agoHandshake completed53 ms
12 days agoHandshake completed44 ms
13 days agoHandshake completed46 ms
14 days agoHandshake completed44 ms
14 days agoHandshake completed47 ms
16 days agoHandshake completed51 ms
19 days agoHandshake completed43 ms
21 days agoHandshake completed59 ms
24 days agoFailed - the check failed for an unclassified reason—
26 days agoHandshake completed49 ms
28 days agoHandshake completed47 ms

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

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