Remote MCP · Endpoint

Send Out MCP server

No. Send Out answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://sendout.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/send-out
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
331 ms
Tools exposed
9 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Turn assistant output into ready-to-send action links and files, with no sign-in.
Listing
From the official MCP registry (active).
Recent checks of Send Out
CheckedResultHandshake
44 minutes agoHandshake completed331 ms
3 days agoHandshake completed144 ms
13 days agoHandshake completed198 ms
13 days agoHandshake completed226 ms
15 days agoHandshake completed187 ms
15 days agoHandshake completed143 ms
17 days agoHandshake completed2.85 s
18 days agoHandshake completed141 ms
18 days agoHandshake completed334 ms
20 days agoHandshake completed181 ms
22 days agoFailed - the server returned an HTTP error—
25 days agoHandshake completed155 ms
27 days agoHandshake completed178 ms
29 days agoHandshake completed140 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 22 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 Send Out and makes no claim about it beyond what these checks measured.

Send Out MCP server - status, uptime and latency - Glide