Remote MCP · Endpoint
io.github.spruikco/send16-mcp MCP server
No — it is up, but it requires credentials. io.github.spruikco/send16-mcp answered 2 hours ago with an authentication challenge rather than a session.
Auth requiredLast checked 2 hours ago
Server URL
https://mcp.send16.com/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- io.github.spruikco/send16-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 87 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Email for AI agents: send mail, manage contacts, automations & webhooks. Zero-DNS first send.
- Website
- https://send16.com/
- Repository
- https://github.com/spruikco/send16-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Credentials required | — |
| 1 day ago | Credentials required | — |
| 2 days ago | Credentials required | — |
| 3 days ago | Credentials required | — |
| 4 days ago | Credentials required | — |
| 5 days ago | Credentials required | — |
| 6 days ago | Credentials required | — |
| 9 days ago | Handshake completed | 334 ms |
| 11 days ago | Handshake completed | 304 ms |
| 14 days ago | Handshake completed | 298 ms |
| 16 days ago | Handshake completed | 298 ms |
| 18 days ago | Handshake completed | 304 ms |
| 20 days ago | Handshake completed | 313 ms |
| 22 days ago | Handshake completed | 339 ms |
| 24 days ago | Handshake completed | 305 ms |
| 26 days ago | Handshake completed | 311 ms |
| 27 days ago | Handshake completed | 326 ms |
| 29 days ago | Handshake completed | 321 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 io.github.spruikco/send16-mcp and makes no claim about it beyond what these checks measured.