Remote MCP · Endpoint

smoothsend MCP server

No. smoothsend answered an MCP handshake 1 hour ago.

Up · key neededLast checked 1 hour ago

Server URL

https://www.doc2mcp.site/api/mcp/206c5de4-cd25-461b-8eb8-0010d1c8e0b0/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
io.github.doc2mcp/smoothsend
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
MCP server for smoothsend documentation, generated by doc2mcp.
Listing
From the official MCP registry (active).
Recent checks of smoothsend
CheckedResultHandshake
1 hour agoHandshake completed273 ms
2 days agoHandshake completed1.15 s
5 days agoHandshake completed293 ms
7 days agoHandshake completed323 ms
9 days agoHandshake completed305 ms
11 days agoHandshake completed295 ms
13 days agoHandshake completed279 ms
15 days agoHandshake completed316 ms
17 days agoHandshake completed252 ms
18 days agoHandshake completed304 ms
20 days agoHandshake completed323 ms
21 days agoHandshake completed357 ms
23 days agoHandshake completed293 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

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.