Remote MCP · Endpoint

DesiData MCP server

No. DesiData answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://lqcxdxjncdzzkwgveydz.supabase.co/functions/v1/mcp

The last check completed an MCP handshake.

Registry name
io.github.krishnakaushik195/desidata-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
601 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search India datasets; inspect sources, licences and previews; get notebook and Python examples.
Listing
From the official MCP registry (active).
Recent checks of DesiData
CheckedResultHandshake
1 hour agoHandshake completed601 ms
1 day agoHandshake completed596 ms
2 days agoHandshake completed721 ms
2 days agoHandshake completed687 ms
4 days agoHandshake completed853 ms
7 days agoHandshake completed665 ms
9 days agoHandshake completed613 ms
12 days agoHandshake completed729 ms
14 days agoHandshake completed630 ms
16 days agoHandshake completed651 ms
18 days agoHandshake completed881 ms
20 days agoHandshake completed796 ms
22 days agoHandshake completed579 ms
24 days agoHandshake completed738 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 DesiData and makes no claim about it beyond what these checks measured.