Remote MCP · Endpoint
md.install/try MCP server
No. md.install/try answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://install.md/mcp/try
The last check completed an MCP handshake.
- Registry name
- md.install/try
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 304 ms
- Tools exposed
- 13 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Create guides as MCP servers to instruct coding agents to use your software (library, API, etc).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 304 ms |
| 1 day ago | Handshake completed | 344 ms |
| 2 days ago | Handshake completed | 93 ms |
| 3 days ago | Handshake completed | 288 ms |
| 4 days ago | Handshake completed | 297 ms |
| 5 days ago | Handshake completed | 262 ms |
| 6 days ago | Handshake completed | 530 ms |
| 8 days ago | Handshake completed | 341 ms |
| 11 days ago | Handshake completed | 300 ms |
| 13 days ago | Handshake completed | 442 ms |
| 15 days ago | Handshake completed | 396 ms |
| 18 days ago | Handshake completed | 333 ms |
| 20 days ago | Handshake completed | 317 ms |
| 22 days ago | Handshake completed | 417 ms |
| 24 days ago | Handshake completed | 385 ms |
| 26 days ago | Handshake completed | 285 ms |
| 27 days ago | Handshake completed | 278 ms |
| 28 days ago | Handshake completed | 322 ms |
| 29 days ago | Handshake completed | 587 ms |
The last 19 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 md.install/try and makes no claim about it beyond what these checks measured.