Remote MCP · Endpoint

Duskly MCP server

No. Duskly answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://duskly.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.duskly/duskly
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
359 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
MLS compliance for edited listing photos: classify edits, write disclosures, verify provenance.
Listing
From the official MCP registry (active).
Recent checks of Duskly
CheckedResultHandshake
1 hour agoHandshake completed359 ms
2 days agoHandshake completed192 ms
4 days agoHandshake completed178 ms
6 days agoHandshake completed155 ms
7 days agoHandshake completed205 ms
9 days agoHandshake completed187 ms
10 days agoHandshake completed319 ms
11 days agoHandshake completed52 ms
14 days agoHandshake completed168 ms
15 days agoHandshake completed347 ms
17 days agoHandshake completed192 ms
18 days agoHandshake completed245 ms
19 days agoHandshake completed142 ms
21 days agoHandshake completed153 ms
22 days agoHandshake completed195 ms
22 days agoHandshake completed311 ms

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

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