Remote MCP · Endpoint

Bounceban MCP server

No. Bounceban answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/bounceban/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/bounceban
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
61 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
BounceBan MCP — wraps the BounceBan email-verification API (bounceban.com)
Listing
From the official MCP registry (active).
Recent checks of Bounceban
CheckedResultHandshake
1 hour agoHandshake completed61 ms
1 day agoHandshake completed243 ms
2 days agoHandshake completed113 ms
4 days agoHandshake completed120 ms
7 days agoHandshake completed74 ms
9 days agoHandshake completed81 ms
11 days agoHandshake completed3.85 s
14 days agoHandshake completed77 ms
16 days agoHandshake completed84 ms
18 days agoHandshake completed65 ms
20 days agoHandshake completed57 ms
22 days agoHandshake completed62 ms
23 days agoHandshake completed2.03 s

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

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