Remote MCP · Endpoint

BounceBan (Unofficial) MCP server

No. BounceBan (Unofficial) answered an MCP handshake 2 days ago.

UpLast checked 2 days 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
35 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Unofficial BounceBan MCP — wraps the BounceBan email-verification API (bounceban.com)
Listing
From the official MCP registry (active).
Recent checks of BounceBan (Unofficial)
CheckedResultHandshake
2 days agoHandshake completed35 ms
6 days agoHandshake completed608 ms
16 days agoHandshake completed163 ms
17 days agoHandshake completed90 ms
17 days agoHandshake completed120 ms
19 days agoHandshake completed125 ms
21 days agoHandshake completed114 ms
21 days agoHandshake completed61 ms
22 days agoHandshake completed243 ms
23 days agoHandshake completed113 ms
25 days agoHandshake completed120 ms
28 days agoHandshake completed74 ms

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

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