Remote MCP · Endpoint

TravelCharika MCP server

No. TravelCharika answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://travelcharika.com/mcp

The last check completed an MCP handshake.

Registry name
com.travelcharika/travelcharika
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
632 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
When to go and where to book: 87 places scored month by month from measured weather.
Listing
From the official MCP registry (active).
Recent checks of TravelCharika
CheckedResultHandshake
1 hour agoHandshake completed632 ms
2 days agoHandshake completed612 ms
5 days agoHandshake completed572 ms
7 days agoHandshake completed791 ms
9 days agoHandshake completed623 ms
11 days agoHandshake completed922 ms
13 days agoHandshake completed627 ms
16 days agoHandshake completed957 ms
18 days agoHandshake completed651 ms
19 days agoHandshake completed657 ms
21 days agoHandshake completed702 ms
22 days agoHandshake completed753 ms
23 days agoHandshake completed576 ms
26 days agoHandshake completed676 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 TravelCharika and makes no claim about it beyond what these checks measured.