Remote MCP · Endpoint

Schengen Counter MCP server

No. Schengen Counter answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.schengencounter.com/mcp

The last check completed an MCP handshake.

Registry name
com.schengencounter/schengen-counter
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
104 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Schengen 90/180-day calculator, earliest re-entry date and ETIAS check. Stateless, no data stored.
Listing
From the official MCP registry (active).
Recent checks of Schengen Counter
CheckedResultHandshake
1 hour agoHandshake completed104 ms
2 days agoHandshake completed71 ms
4 days agoHandshake completed62 ms
7 days agoHandshake completed77 ms
9 days agoHandshake completed78 ms
11 days agoHandshake completed54 ms
13 days agoHandshake completed49 ms
15 days agoHandshake completed66 ms
17 days agoHandshake completed49 ms
19 days agoHandshake completed57 ms
20 days agoHandshake completed378 ms
22 days agoHandshake completed66 ms
23 days agoHandshake completed533 ms

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

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