Remote MCP · Endpoint
Bug Bounty Programs MCP server
No. Bug Bounty Programs answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://gateway.pipeworx.io/bug-bounty-programs/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.pipeworx-io/bug-bounty-programs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 72 ms
- Tools exposed
- 47 tools
- Uptime, last 30 days
- 92.3% from 13 checks
- Described by its publisher as
- bug-bounty-programs
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 72 ms |
| 1 day ago | Handshake completed | 249 ms |
| 2 days ago | Handshake completed | 117 ms |
| 4 days ago | Handshake completed | 272 ms |
| 7 days ago | Handshake completed | 69 ms |
| 9 days ago | Handshake completed | 90 ms |
| 11 days ago | Handshake completed | 77 ms |
| 14 days ago | Handshake completed | 57 ms |
| 16 days ago | Handshake completed | 55 ms |
| 18 days ago | Handshake completed | 62 ms |
| 20 days ago | Failed - the request timed out | — |
| 22 days ago | Handshake completed | 61 ms |
| 23 days ago | Handshake completed | 1.78 s |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 Bug Bounty Programs and makes no claim about it beyond what these checks measured.