Remote MCP · Endpoint
Fursat MCP server
No. Fursat answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://www.fursat.fun/api/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.fursatdev-tech/fursat
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 285 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- AI-bookable curated vacation homes in Northeast India and the Himalayas. Book on WhatsApp.
- Website
- https://www.fursat.fun/
- Repository
- https://github.com/fursatdev-tech/fursat
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 285 ms |
| 2 days ago | Handshake completed | 917 ms |
| 4 days ago | Handshake completed | 274 ms |
| 6 days ago | Handshake completed | 367 ms |
| 7 days ago | Handshake completed | 317 ms |
| 9 days ago | Handshake completed | 278 ms |
| 10 days ago | Handshake completed | 371 ms |
| 11 days ago | Handshake completed | 431 ms |
| 14 days ago | Handshake completed | 275 ms |
| 15 days ago | Handshake completed | 251 ms |
| 17 days ago | Handshake completed | 952 ms |
| 18 days ago | Handshake completed | 256 ms |
| 19 days ago | Handshake completed | 261 ms |
| 20 days ago | Handshake completed | 258 ms |
| 21 days ago | Handshake completed | 251 ms |
| 22 days ago | Handshake completed | 368 ms |
| 23 days ago | Handshake completed | 269 ms |
| 24 days ago | Handshake completed | 654 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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 Fursat and makes no claim about it beyond what these checks measured.