Remote MCP · Endpoint

PriceBee MCP server

No. PriceBee answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://pricebee.lt/mcp/pricebee

The last check completed an MCP handshake.

Registry name
lt.pricebee/pricebee
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
248 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Compare prices of products in online shops and of mobile plans in Lithuania, Latvia and Estonia.
Listing
From the official MCP registry (active).
Recent checks of PriceBee
CheckedResultHandshake
2 hours agoHandshake completed248 ms
1 day agoHandshake completed442 ms
2 days agoHandshake completed438 ms
2 days agoHandshake completed303 ms
4 days agoHandshake completed460 ms
7 days agoHandshake completed451 ms
9 days agoHandshake completed649 ms
12 days agoHandshake completed1.12 s
14 days agoHandshake completed263 ms
16 days agoHandshake completed223 ms
18 days agoHandshake completed469 ms
20 days agoHandshake completed270 ms
22 days agoHandshake completed201 ms
24 days agoHandshake completed460 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 PriceBee and makes no claim about it beyond what these checks measured.