Remote MCP · Endpoint
Linof docs MCP server
No. Linof docs answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://linof.ai/api/apps/6a562086cd3bd1e44e0d4c3d/functions/docsMcp
The last check completed an MCP handshake.
- Registry name
- ai.linof/docs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 578 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- Linof turns family photos into a short film. Read Linof's docs and live prices. No sign-in.
- Website
- https://linof.ai/developers
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 578 ms |
| 4 days ago | Handshake completed | 1.10 s |
| 14 days ago | Handshake completed | 255 ms |
| 15 days ago | Handshake completed | 616 ms |
| 15 days ago | Handshake completed | 263 ms |
| 17 days ago | Handshake completed | 413 ms |
| 18 days ago | Handshake completed | 296 ms |
| 19 days ago | Handshake completed | 504 ms |
| 20 days ago | Handshake completed | 416 ms |
| 21 days ago | Handshake completed | 265 ms |
| 23 days ago | Handshake completed | 826 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 Linof docs and makes no claim about it beyond what these checks measured.