Remote MCP · Endpoint

BountyHunte.rs MCP server

No. BountyHunte.rs answered an MCP handshake 18 minutes ago.

Up · key neededLast checked 18 minutes 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
214 ms
Tools exposed
Behind credentials
Uptime, last 30 days
100% from 14 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
18 minutes agoHandshake completed214 ms
9 days agoHandshake completed206 ms
9 days agoHandshake completed93 ms
11 days agoHandshake completed136 ms
12 days agoHandshake completed215 ms
13 days agoHandshake completed105 ms
14 days agoHandshake completed102 ms
14 days agoHandshake completed143 ms
16 days agoHandshake completed103 ms
19 days agoHandshake completed226 ms
21 days agoHandshake completed106 ms
24 days agoHandshake completed693 ms
26 days agoHandshake completed106 ms
28 days agoHandshake completed124 ms

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

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.