Remote MCP · Endpoint

io.inboxguard/email-deliverability MCP server

No. io.inboxguard/email-deliverability answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.inboxguard.io/mcp

The last check completed an MCP handshake.

Registry name
io.inboxguard/email-deliverability
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Scan and fix a domain's email deliverability (SPF, DKIM, DMARC, MTA-STS, BIMI, DNS blocklists).
Listing
From the official MCP registry (active).
Recent checks of io.inboxguard/email-deliverability
CheckedResultHandshake
1 hour agoHandshake completed56 ms
9 days agoHandshake completed58 ms
10 days agoHandshake completed57 ms
11 days agoHandshake completed44 ms
12 days agoHandshake completed40 ms
14 days agoHandshake completed58 ms
14 days agoHandshake completed69 ms
15 days agoHandshake completed57 ms
17 days agoHandshake completed58 ms
19 days agoHandshake completed53 ms
21 days agoHandshake completed47 ms
24 days agoHandshake completed57 ms
26 days agoHandshake completed47 ms
28 days agoHandshake completed53 ms

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

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