Remote MCP · Endpoint

Schengen 90/180 Calculator MCP server

No. Schengen 90/180 Calculator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://schengen-mcp.alickzheng618.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.al157/schengen-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
157 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Schengen 90/180 rolling-window calculator MCP server: stay math, trip checks, rule explainer.
Listing
From the official MCP registry (active).
Recent checks of Schengen 90/180 Calculator
CheckedResultHandshake
1 hour agoHandshake completed157 ms
19 hours agoHandshake completed315 ms
1 day agoHandshake completed186 ms
2 days agoHandshake completed309 ms
4 days agoHandshake completed388 ms
7 days agoHandshake completed165 ms
9 days agoHandshake completed288 ms
12 days agoHandshake completed217 ms
14 days agoHandshake completed215 ms
16 days agoHandshake completed417 ms
18 days agoHandshake completed182 ms
20 days agoHandshake completed194 ms
22 days agoHandshake completed288 ms
23 days agoHandshake completed232 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 Schengen 90/180 Calculator and makes no claim about it beyond what these checks measured.