Remote MCP · Endpoint

coldHat MCP server

No. coldHat answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://coldhat.f-keys.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.vince-gonzalez/coldhat
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
405 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Put on anyone's AI rules by GitHub username: fetches their hat.md and its hat code.
Listing
From the official MCP registry (active).
Recent checks of coldHat
CheckedResultHandshake
1 hour agoHandshake completed405 ms
1 day agoHandshake completed186 ms
2 days agoHandshake completed207 ms
3 days agoHandshake completed229 ms
4 days agoHandshake completed323 ms
5 days agoHandshake completed198 ms
6 days agoHandshake completed259 ms
9 days agoHandshake completed214 ms
12 days agoHandshake completed247 ms
14 days agoHandshake completed327 ms
16 days agoHandshake completed217 ms
18 days agoHandshake completed312 ms
20 days agoHandshake completed261 ms
22 days agoHandshake completed241 ms
24 days agoHandshake completed66 ms

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