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
497 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search, install and submit Markdown skills for AI agents; private Brain files when signed in.
Listing
From the official MCP registry (active).
Recent checks of emdly
CheckedResultHandshake
1 hour agoHandshake completed497 ms
2 days agoHandshake completed520 ms
4 days agoHandshake completed499 ms
5 days agoHandshake completed490 ms
7 days agoHandshake completed512 ms
8 days agoHandshake completed597 ms
9 days agoHandshake completed476 ms
12 days agoHandshake completed532 ms
13 days agoHandshake completed554 ms
15 days agoHandshake completed578 ms
16 days agoHandshake completed494 ms
17 days agoHandshake completed545 ms
18 days agoHandshake completed717 ms
19 days agoHandshake completed497 ms
20 days agoHandshake completed497 ms
21 days agoHandshake completed560 ms
22 days agoHandshake completed605 ms

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

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.