Remote MCP · Endpoint

Paytm Travel MCP server

No. Paytm Travel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://travel.paytm.com/mcp/mcp

The last check completed an MCP handshake.

Registry name
com.paytm.travel/discovery
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
383 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Discover and compare live Paytm flights and buses by fare, schedule, operator, stops, and amenities.
Listing
From the official MCP registry (active).
Recent checks of Paytm Travel
CheckedResultHandshake
1 hour agoHandshake completed383 ms
6 hours agoHandshake completed318 ms
2 days agoHandshake completed355 ms
4 days agoHandshake completed1.47 s
7 days agoHandshake completed259 ms
9 days agoHandshake completed407 ms
11 days agoHandshake completed231 ms
13 days agoHandshake completed238 ms
15 days agoHandshake completed224 ms
17 days agoHandshake completed248 ms
19 days agoHandshake completed237 ms
21 days agoHandshake completed228 ms
23 days agoHandshake completed365 ms
24 days agoHandshake completed336 ms
25 days agoHandshake completed243 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 Paytm Travel and makes no claim about it beyond what these checks measured.