Remote MCP · Endpoint

Daski MCP server

No. Daski answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes 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
479 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.
Listing
From the official MCP registry (active).
Recent checks of Daski
CheckedResultHandshake
43 minutes agoHandshake completed479 ms
3 days agoHandshake completed352 ms
12 days agoHandshake completed183 ms
12 days agoHandshake completed152 ms
14 days agoHandshake completed177 ms
15 days agoHandshake completed221 ms
16 days agoHandshake completed155 ms
17 days agoHandshake completed164 ms
18 days agoHandshake completed183 ms
19 days agoHandshake completed184 ms
22 days agoHandshake completed160 ms
25 days agoHandshake completed159 ms
27 days agoHandshake completed627 ms
29 days agoHandshake completed167 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 24 responding of 24.

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 Daski and makes no claim about it beyond what these checks measured.