Remote MCP · Endpoint

Coolant MCP server

No. Coolant answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://coolant.run/mcp

The last check completed an MCP handshake.

Registry name
run.coolant/coolant
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
203 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Instruments for what a model cannot know on its own: time, randomness, DNS, hashes, receipts.
Listing
From the official MCP registry (active).
Recent checks of Coolant
CheckedResultHandshake
5 hours agoHandshake completed203 ms
2 days agoHandshake completed194 ms
4 days agoHandshake completed161 ms
5 days agoHandshake completed197 ms
7 days agoHandshake completed202 ms
8 days agoHandshake completed154 ms
9 days agoHandshake completed180 ms
12 days agoHandshake completed2.16 s
13 days agoHandshake completed143 ms
15 days agoHandshake completed224 ms
16 days agoHandshake completed211 ms
17 days agoHandshake completed161 ms
18 days agoHandshake completed170 ms
19 days agoHandshake completed144 ms
20 days agoHandshake completed196 ms
21 days agoHandshake completed221 ms
22 days agoHandshake completed170 ms

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

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