Remote MCP · Endpoint
Duskly MCP server
No. Duskly answered an MCP handshake 54 minutes ago.
UpLast checked 54 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
- 153 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- MLS compliance for edited listing photos: classify edits, write disclosures, verify provenance.
- Website
- https://duskly.ai/mcp-server
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 54 minutes ago | Handshake completed | 153 ms |
| 1 day ago | Handshake completed | 195 ms |
| 1 day ago | Handshake completed | 311 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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.