Remote MCP · Endpoint

VTC AEROPORT PARIS MCP server

No. VTC AEROPORT PARIS answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://vtc-aeroport.fr/wp-json/sivtc/v1/mcp

The last check completed an MCP handshake.

Registry name
fr.vtc-aeroport/reservation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.62 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Chauffeur privé et transferts aéroport à Paris (CDG, Orly, Beauvais) : prix fixes et réservation.
Listing
From the official MCP registry (active).
Recent checks of VTC AEROPORT PARIS
CheckedResultHandshake
56 minutes agoHandshake completed2.62 s
1 day agoHandshake completed924 ms
2 days agoHandshake completed859 ms
5 days agoHandshake completed815 ms
8 days agoHandshake completed820 ms
10 days agoHandshake completed3.51 s
12 days agoHandshake completed1.03 s
14 days agoHandshake completed746 ms
16 days agoHandshake completed746 ms
18 days agoHandshake completed767 ms
20 days agoHandshake completed707 ms
22 days agoHandshake completed683 ms
23 days agoHandshake completed827 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 VTC AEROPORT PARIS and makes no claim about it beyond what these checks measured.