Remote MCP · Endpoint

com.spocont/reservoprix MCP server

No. com.spocont/reservoprix answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.reservoprix.com/

The last check completed an MCP handshake.

Registry name
com.spocont/reservoprix
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
254 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Sell to the best offer: a sealed-offer link and button for any listing, with a hidden reserve price.
Listing
From the official MCP registry (active).
Recent checks of com.spocont/reservoprix
CheckedResultHandshake
1 hour agoHandshake completed254 ms
2 days agoHandshake completed255 ms
5 days agoHandshake completed256 ms
7 days agoHandshake completed263 ms
9 days agoHandshake completed283 ms
11 days agoHandshake completed249 ms
13 days agoHandshake completed258 ms
15 days agoHandshake completed315 ms
17 days agoHandshake completed244 ms
18 days agoHandshake completed260 ms
20 days agoHandshake completed256 ms
21 days agoHandshake completed250 ms
23 days agoHandshake completed246 ms
25 days agoHandshake completed256 ms

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

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 com.spocont/reservoprix and makes no claim about it beyond what these checks measured.