Remote MCP · Endpoint

Duskly MCP server

No. Duskly answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes 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
105 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 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
16 minutes agoHandshake completed105 ms
8 days agoHandshake completed428 ms
9 days agoHandshake completed241 ms
11 days agoHandshake completed296 ms
12 days agoHandshake completed451 ms
13 days agoHandshake completed319 ms
14 days agoHandshake completed378 ms
14 days agoHandshake completed257 ms
16 days agoHandshake completed84 ms
19 days agoHandshake completed528 ms
21 days agoHandshake completed337 ms
24 days agoHandshake completed392 ms
26 days agoHandshake completed211 ms
28 days agoHandshake completed359 ms

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

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.