Remote MCP · Endpoint

Kraken MCP server

No. Kraken answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/kraken/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/kraken
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
105 ms
Tools exposed
53 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Kraken MCP (public endpoints).
Listing
From the official MCP registry (active).
Recent checks of Kraken
CheckedResultHandshake
1 hour agoHandshake completed105 ms
21 hours agoHandshake completed98 ms
2 days agoHandshake completed154 ms
3 days agoHandshake completed192 ms
4 days agoHandshake completed62 ms
5 days agoHandshake completed65 ms
6 days agoHandshake completed1.20 s
8 days agoHandshake completed112 ms
11 days agoHandshake completed80 ms
13 days agoHandshake completed105 ms
16 days agoHandshake completed245 ms
18 days agoHandshake completed73 ms
20 days agoHandshake completed121 ms
22 days agoHandshake completed56 ms
24 days agoHandshake completed50 ms
26 days agoHandshake completed502 ms
27 days agoHandshake completed59 ms
29 days agoHandshake completed43 ms

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

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