Remote MCP · Endpoint

Daski MCP server

No. Daski answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://daski.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.daski-io/daski
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Discover, purchase, and manage real-world services through Daski's curated marketplace.
Website
https://daski.io/
Listing
From the official MCP registry (active).
Recent checks of Daski
CheckedResultHandshake
1 hour agoHandshake completed160 ms
2 days agoHandshake completed159 ms
5 days agoHandshake completed627 ms
7 days agoHandshake completed167 ms
9 days agoHandshake completed201 ms
11 days agoHandshake completed155 ms
13 days agoHandshake completed165 ms
15 days agoHandshake completed154 ms
16 days agoHandshake completed146 ms
18 days agoHandshake completed153 ms
19 days agoHandshake completed521 ms
20 days agoHandshake completed154 ms
23 days agoHandshake completed137 ms
24 days agoHandshake completed224 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Daski and makes no claim about it beyond what these checks measured.