Remote MCP · Endpoint
com.sendpageapp/sendpage MCP server
Yes, as of 2 hours ago: the hostname does not resolve.
DownLast checked 2 hours ago
Server URL
https://sendpageapp.com/mcp
The last check failed: the hostname does not resolve.
- Registry name
- com.sendpageapp/sendpage
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 5.6% from 18 checks
- Described by its publisher as
- Publish an HTML document as a link anyone can open in one tap, plus PDF, image and Word export.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Failed - the hostname does not resolve | — |
| 1 day ago | Failed - the hostname does not resolve | — |
| 2 days ago | Failed - the hostname does not resolve | — |
| 3 days ago | Failed - the hostname does not resolve | — |
| 4 days ago | Failed - the hostname does not resolve | — |
| 5 days ago | Failed - the hostname does not resolve | — |
| 7 days ago | Failed - the hostname does not resolve | — |
| 9 days ago | Failed - the hostname does not resolve | — |
| 12 days ago | Failed - the hostname does not resolve | — |
| 14 days ago | Failed - the hostname does not resolve | — |
| 16 days ago | Failed - the hostname does not resolve | — |
| 18 days ago | Failed - the hostname does not resolve | — |
| 20 days ago | Failed - the hostname does not resolve | — |
| 22 days ago | Failed - the hostname does not resolve | — |
| 24 days ago | Failed - the hostname does not resolve | — |
| 26 days ago | Failed - the hostname does not resolve | — |
| 27 days ago | Failed - the hostname does not resolve | — |
| 29 days ago | Handshake completed | 413 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 com.sendpageapp/sendpage and makes no claim about it beyond what these checks measured.