Remote MCP · Endpoint
Link Preview Cache API MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://link-preview-cache-api.onrender.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.cmondillo/link-preview-cache-api
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 38.9% from 18 checks
- Described by its publisher as
- Same link preview data as link-preview-api, ~1/3 the price via a shared cache.
- Repository
- https://github.com/cmondillo/tools
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Handshake completed | 233 ms |
| 7 days ago | Handshake completed | 379 ms |
| 9 days ago | Handshake completed | 256 ms |
| 10 days ago | Handshake completed | 259 ms |
| 11 days ago | Handshake completed | 283 ms |
| 14 days ago | Handshake completed | 437 ms |
| 15 days ago | Handshake completed | 396 ms |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 22 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Failed - the server returned an HTTP error | — |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 7 responding of 18.
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 Link Preview Cache API and makes no claim about it beyond what these checks measured.