Remote MCP · Endpoint

AI MAXX Public Passports MCP server

No. AI MAXX Public Passports answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.ai-maxx.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.ai-maxx.www/public-passports
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
614 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Instant Malta visit facts and AI consultation: activities, dining, venues, photos and routes.
Listing
From the official MCP registry (active).
Recent checks of AI MAXX Public Passports
CheckedResultHandshake
2 hours agoHandshake completed614 ms
2 days agoHandshake completed858 ms
4 days agoHandshake completed1.01 s
7 days agoHandshake completed732 ms
8 days agoHandshake completed339 ms
11 days agoHandshake completed1.61 s
13 days agoHandshake completed1.00 s
14 days agoHandshake completed1.35 s
16 days agoHandshake completed145 ms
17 days agoHandshake completed254 ms
18 days agoHandshake completed1.37 s
20 days agoHandshake completed1.18 s
22 days agoHandshake completed939 ms
24 days agoHandshake completed242 ms

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

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