Remote MCP · Endpoint

PEWES ENERGY catalogue MCP server

No. PEWES ENERGY catalogue answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pewesenergy.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.pewesenergy/catalogue
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
904 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Search the PEWES ENERGY drinks catalogue, read one drink, the price list and any store page.
Listing
From the official MCP registry (active).
Recent checks of PEWES ENERGY catalogue
CheckedResultHandshake
1 hour agoHandshake completed904 ms
1 day agoHandshake completed972 ms
2 days agoHandshake completed886 ms
3 days agoHandshake completed993 ms
4 days agoHandshake completed905 ms
5 days agoHandshake completed880 ms
6 days agoHandshake completed436 ms
9 days agoHandshake completed1.06 s
11 days agoHandshake completed912 ms
14 days agoHandshake completed929 ms
16 days agoHandshake completed895 ms
18 days agoHandshake completed1.14 s
20 days agoHandshake completed1.17 s
22 days agoHandshake completed1.15 s
24 days agoHandshake completed1.15 s

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 PEWES ENERGY catalogue and makes no claim about it beyond what these checks measured.