Remote MCP · Endpoint

HeatPulse MCP server

No. HeatPulse answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://heatpulse.cc/mcp

The last check completed an MCP handshake.

Registry name
cc.heatpulse/heatpulse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
298 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI-news gateway for agents: curated events, digests, live LLM leaderboards, intent router.
Listing
From the official MCP registry (active).
Recent checks of HeatPulse
CheckedResultHandshake
1 day agoHandshake completed298 ms
3 days agoHandshake completed381 ms
5 days agoHandshake completed1.09 s
7 days agoHandshake completed1.06 s
9 days agoHandshake completed1.10 s
10 days agoHandshake completed1.12 s
12 days agoHandshake completed1.07 s
13 days agoHandshake completed1.13 s
15 days agoHandshake completed1.10 s
17 days agoHandshake completed1.05 s
19 days agoHandshake completed1.08 s
20 days agoHandshake completed1.10 s
21 days agoHandshake completed1.12 s
22 days agoHandshake completed1.47 s

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