Remote MCP · Endpoint
HeatPulse MCP server
No — it is up, but it requires credentials. HeatPulse answered 1 hour ago with an authentication challenge rather than a session.
Auth requiredLast checked 1 hour ago
Server URL
https://heatpulse.cc/mcp
The endpoint is answering and asked us for credentials. That is a working server, not an outage.
- Registry name
- cc.heatpulse/heatpulse
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- 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.
- Website
- https://heatpulse.cc/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Credentials required | — |
| 9 days ago | Credentials required | — |
| 10 days ago | Credentials required | — |
| 11 days ago | Credentials required | — |
| 12 days ago | Credentials required | — |
| 14 days ago | Credentials required | — |
| 14 days ago | Handshake completed | 316 ms |
| 15 days ago | Handshake completed | 789 ms |
| 17 days ago | Handshake completed | 8.98 s |
| 19 days ago | Handshake completed | 307 ms |
| 21 days ago | Handshake completed | 812 ms |
| 24 days ago | Handshake completed | 833 ms |
| 26 days ago | Handshake completed | 303 ms |
| 28 days ago | Handshake completed | 298 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 27.
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.