Remote MCP · Endpoint

Flytel MCP server

No. Flytel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://flytel.fr/mcp

The last check completed an MCP handshake.

Registry name
fr.flytel/flytel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
489 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Forfaits mobiles Flytel pour les frontaliers France-Suisse : offres, appels, données, pays.
Listing
From the official MCP registry (active).
Recent checks of Flytel
CheckedResultHandshake
1 hour agoHandshake completed489 ms
1 day agoHandshake completed310 ms
2 days agoHandshake completed413 ms
3 days agoHandshake completed241 ms
4 days agoHandshake completed259 ms
5 days agoHandshake completed315 ms
7 days agoHandshake completed512 ms
10 days agoHandshake completed446 ms
12 days agoHandshake completed824 ms
14 days agoHandshake completed548 ms
17 days agoHandshake completed375 ms
19 days agoHandshake completed529 ms
21 days agoHandshake completed416 ms
23 days agoHandshake completed493 ms
25 days agoHandshake completed406 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 Flytel and makes no claim about it beyond what these checks measured.