Remote MCP · Endpoint

Jetopolis MCP server

No. Jetopolis answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://jetopolis.app/mcp

The last check completed an MCP handshake.

Registry name
app.jetopolis/game
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Airline strategy game 1950-2030: live worlds, leaders, historical airlines, aircraft prices
Listing
From the official MCP registry (active).
Recent checks of Jetopolis
CheckedResultHandshake
5 hours agoHandshake completed97 ms
9 days agoHandshake completed1.59 s
10 days agoHandshake completed715 ms
11 days agoHandshake completed1.14 s
12 days agoHandshake completed990 ms
14 days agoHandshake completed912 ms
14 days agoHandshake completed694 ms
15 days agoHandshake completed585 ms
17 days agoHandshake completed1.27 s
19 days agoHandshake completed812 ms
21 days agoHandshake completed1.10 s
24 days agoHandshake completed549 ms
26 days agoHandshake completed724 ms
28 days agoHandshake completed630 ms

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

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