Remote MCP · Endpoint

Sendora MCP server

No. Sendora answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.sendora.se/docs

The last check completed an MCP handshake.

Registry name
se.sendora/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
334 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Sendora's docs and API for coding agents: send test mail, read the log, set up webhooks.
Listing
From the official MCP registry (active).
Recent checks of Sendora
CheckedResultHandshake
1 hour agoHandshake completed334 ms
1 day agoHandshake completed358 ms
2 days agoHandshake completed339 ms
3 days agoHandshake completed362 ms
4 days agoHandshake completed430 ms
5 days agoHandshake completed338 ms
7 days agoHandshake completed337 ms
10 days agoHandshake completed411 ms
12 days agoHandshake completed416 ms
14 days agoHandshake completed342 ms
17 days agoHandshake completed354 ms
19 days agoHandshake completed417 ms
21 days agoHandshake completed342 ms
23 days agoHandshake completed613 ms
25 days agoHandshake completed351 ms

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

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 Sendora and makes no claim about it beyond what these checks measured.