Remote MCP · Endpoint

SendGuard MCP server

No. SendGuard answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://api.sendguard.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.sendguard/preflight
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
322 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check an email before your AI agent sends it: allow, review or block with reasons.
Listing
From the official MCP registry (active).
Recent checks of SendGuard
CheckedResultHandshake
20 minutes agoHandshake completed322 ms
9 days agoHandshake completed274 ms
9 days agoHandshake completed255 ms
11 days agoHandshake completed260 ms
12 days agoHandshake completed358 ms
13 days agoHandshake completed284 ms
14 days agoHandshake completed546 ms
15 days agoHandshake completed282 ms
16 days agoHandshake completed415 ms
19 days agoHandshake completed321 ms
21 days agoHandshake completed390 ms
24 days agoHandshake completed359 ms
26 days agoHandshake completed309 ms
28 days agoHandshake completed272 ms

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