Remote MCP · Endpoint
smoothsend MCP server
Yes, as of 35 minutes ago: the server returned an HTTP error.
DownLast checked 35 minutes ago
Server URL
https://www.doc2mcp.site/api/mcp/206c5de4-cd25-461b-8eb8-0010d1c8e0b0/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.doc2mcp/smoothsend
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- Not measured yet
- Uptime, last 30 days
- 85.7% from 14 checks
- Described by its publisher as
- MCP server for smoothsend documentation, generated by doc2mcp.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 35 minutes ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Failed - the server returned an HTTP error | — |
| 13 days ago | Handshake completed | 748 ms |
| 14 days ago | Handshake completed | 350 ms |
| 15 days ago | Handshake completed | 297 ms |
| 16 days ago | Handshake completed | 301 ms |
| 17 days ago | Handshake completed | 279 ms |
| 18 days ago | Handshake completed | 260 ms |
| 19 days ago | Handshake completed | 299 ms |
| 20 days ago | Handshake completed | 1.12 s |
| 22 days ago | Handshake completed | 273 ms |
| 25 days ago | Handshake completed | 1.15 s |
| 27 days ago | Handshake completed | 293 ms |
| 29 days ago | Handshake completed | 323 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 21 responding of 23.
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 smoothsend and makes no claim about it beyond what these checks measured.