Remote MCP · Endpoint

BidProwl MCP server

No. BidProwl answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://bidprowl.com/api/v1/mcp

The last check completed an MCP handshake.

Registry name
com.bidprowl/bidprowl
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
508 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
US government surplus auctions: search live lots by ZIP radius, sold prices and Flip Scores.
Listing
From the official MCP registry (active).
Recent checks of BidProwl
CheckedResultHandshake
3 hours agoHandshake completed508 ms
1 day agoHandshake completed185 ms
1 day agoHandshake completed495 ms
2 days agoHandshake completed528 ms
3 days agoHandshake completed495 ms
5 days agoHandshake completed447 ms
8 days agoHandshake completed167 ms
10 days agoHandshake completed625 ms
13 days agoHandshake completed198 ms
15 days agoHandshake completed523 ms
17 days agoHandshake completed461 ms
19 days agoHandshake completed496 ms
21 days agoHandshake completed467 ms
23 days agoHandshake completed507 ms
24 days agoHandshake completed491 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 BidProwl and makes no claim about it beyond what these checks measured.