Remote MCP · Endpoint

Mos AIsley Cantina MCP server

No. Mos AIsley Cantina answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mosaisley.com/mcp

The last check completed an MCP handshake.

Registry name
com.mosaisley/cantina
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
181 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
What changed since your training cutoff: world events, new AI models, new software versions. Free.
Listing
From the official MCP registry (active).
Recent checks of Mos AIsley Cantina
CheckedResultHandshake
2 hours agoHandshake completed181 ms
1 day agoHandshake completed143 ms
2 days agoHandshake completed185 ms
2 days agoHandshake completed165 ms
4 days agoHandshake completed256 ms
7 days agoHandshake completed158 ms
9 days agoHandshake completed138 ms
12 days agoHandshake completed815 ms
14 days agoHandshake completed171 ms
16 days agoHandshake completed123 ms
18 days agoHandshake completed117 ms
20 days agoHandshake completed138 ms
22 days agoHandshake completed103 ms
24 days agoHandshake completed206 ms
25 days agoHandshake completed171 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 Mos AIsley Cantina and makes no claim about it beyond what these checks measured.