Remote MCP · Endpoint
mkdshare.DEV MCP server
No. mkdshare.DEV answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mkdshare.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.PhilipAnd/mkdshare
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 235 ms
- Tools exposed
- 11 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Publish and share access-controlled Markdown documents from any MCP-enabled AI tool.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 235 ms |
| 1 day ago | Handshake completed | 159 ms |
| 2 days ago | Handshake completed | 143 ms |
| 3 days ago | Handshake completed | 166 ms |
| 4 days ago | Handshake completed | 141 ms |
| 5 days ago | Handshake completed | 155 ms |
| 6 days ago | Handshake completed | 186 ms |
| 9 days ago | Handshake completed | 157 ms |
| 11 days ago | Handshake completed | 320 ms |
| 14 days ago | Handshake completed | 309 ms |
| 16 days ago | Handshake completed | 184 ms |
| 18 days ago | Handshake completed | 144 ms |
| 20 days ago | Handshake completed | 153 ms |
| 22 days ago | Handshake completed | 159 ms |
| 24 days ago | Handshake completed | 198 ms |
| 26 days ago | Handshake completed | 127 ms |
| 28 days ago | Handshake completed | 176 ms |
| 29 days ago | Handshake completed | 192 ms |
The last 18 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 mkdshare.DEV and makes no claim about it beyond what these checks measured.