Remote MCP · Endpoint

BountyHunte.rs MCP server

No. BountyHunte.rs answered an MCP handshake 1 hour ago.

Up · key neededLast checked 1 hour ago

Server URL

https://bountyhunte.rs/api/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
rs.bountyhunte/programs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
693 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search and monitor bug bounty programs and audit contests across ten platforms.
Listing
From the official MCP registry (active).
Recent checks of BountyHunte.rs
CheckedResultHandshake
1 hour agoHandshake completed693 ms
2 days agoHandshake completed106 ms
4 days agoHandshake completed124 ms
6 days agoHandshake completed115 ms
8 days agoHandshake completed149 ms
10 days agoHandshake completed89 ms
11 days agoHandshake completed105 ms
13 days agoHandshake completed96 ms
14 days agoHandshake completed582 ms
15 days agoHandshake completed97 ms
18 days agoHandshake completed77 ms
19 days agoHandshake completed86 ms
21 days agoHandshake completed72 ms
23 days agoHandshake completed96 ms
24 days agoHandshake completed87 ms

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