Remote MCP · Endpoint
emdly MCP server
No. emdly answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://emdly.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.emdly/emdly
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 531 ms
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Search, install and submit Markdown skills for AI agents; private Brain files when signed in.
- Website
- https://emdly.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 531 ms |
| 18 hours ago | Handshake completed | 288 ms |
| 2 days ago | Handshake completed | 688 ms |
| 3 days ago | Handshake completed | 270 ms |
| 4 days ago | Handshake completed | 523 ms |
| 5 days ago | Handshake completed | 525 ms |
| 6 days ago | Handshake completed | 564 ms |
| 7 days ago | Handshake completed | 522 ms |
| 10 days ago | Handshake completed | 498 ms |
| 13 days ago | Handshake completed | 972 ms |
| 15 days ago | Handshake completed | 510 ms |
| 17 days ago | Handshake completed | 599 ms |
| 19 days ago | Handshake completed | 520 ms |
| 21 days ago | Handshake completed | 497 ms |
| 23 days ago | Handshake completed | 520 ms |
| 25 days ago | Handshake completed | 499 ms |
| 27 days ago | Handshake completed | 490 ms |
| 28 days ago | Handshake completed | 512 ms |
| 29 days ago | Handshake completed | 597 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.
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 emdly and makes no claim about it beyond what these checks measured.