HeatPulse
REMOTE · HEATPULSE.CC · SCANNED SEP 29
AI-news gateway for agents: curated events, digests, live LLM leaderboards, intent router.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 471 tokens (~47/item across 10 items; 8 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 31% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the HeatPulse MCP server?
HeatPulse is a hosted endpoint at https://heatpulse.cc/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · heatpulse.cc
claude mcp add --transport http cc-heatpulse-heatpulse 'https://heatpulse.cc/mcp'
{
"mcpServers": {
"cc-heatpulse-heatpulse": {
"url": "https://heatpulse.cc/mcp"
}
}
} {
"servers": {
"cc-heatpulse-heatpulse": {
"type": "http",
"url": "https://heatpulse.cc/mcp"
}
}
} [mcp_servers.cc-heatpulse-heatpulse] url = "https://heatpulse.cc/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cc-heatpulse-heatpulse": {
"type": "remote",
"url": "https://heatpulse.cc/mcp",
"enabled": true
}
}
} openclaw mcp add cc-heatpulse-heatpulse --url 'https://heatpulse.cc/mcp' --transport streamable-http
mcp_servers:
cc-heatpulse-heatpulse:
url: "https://heatpulse.cc/mcp" {
"McpServers": {
"cc-heatpulse-heatpulse": {
"Transport": "http",
"Url": "https://heatpulse.cc/mcp"
}
}
} assistant mcp add cc-heatpulse-heatpulse -t streamable-http -u 'https://heatpulse.cc/mcp'
{
"mcpServers": {
"cc-heatpulse-heatpulse": {
"type": "http",
"url": "https://heatpulse.cc/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://heatpulse.cc/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=heatpulse.cc | CN=YE1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 65a54f552c129f39b4356d295e91627279c |
| SANs: *.heatpulse.cc, heatpulse.cc | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of heatpulse.cc. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cc. | present | 12593 | 13 | Verified |
| heatpulse.cc. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://heatpulse.cc/mcp | Verified | 200 | |
| http (plaintext) | http://heatpulse.cc/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
daily_digest ~49
The daily editorial digest for a date (YYYY-MM-DD) or the latest one: intro paragraph, stats, and the day's featured events.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD, default latest |
No output schema declared.
No examples provided.
get_event ~36
One AI-news event by slug: full editorial summary plus its outbound coverage list (links to original outlets).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_datasets ~35
Bulk JSONL dataset manifest (events corpus, entities, leaderboard history, digests) for RAG/fine-tune pulls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_topics ~32
Extracted entities (companies, models, people, themes) ranked by coverage count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
llm_leaderboard ~82
Live LLM arena leaderboards (text/code/agent/document/vision/search). Rows carry arena score+votes, rank delta vs the previous daily snapshot, OpenRouter context length and USD-per-1M-token pricing. Agent board: score = net-improvement %, votes = sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| board | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
related_stories ~34
Events most similar to a given event (centroid cosine KNN, max 5).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
route_intent ~52
Describe what knowledge you need in natural language; get back the right HeatPulse endpoint(s) and authoritative external sources, each with a "why".
| Name | Type | Req | Description |
|---|---|---|---|
| intent | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
search_news ~116
Search or list AI news events. Pass `query` for semantic search, or omit it for the heat-ranked feed. Returns editorial summaries (safe to quote) with canonical /event/{slug} URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug, one of: models, products, industry, papers, benchmarks, policy, tips |
| limit | integer | – | – |
| order | string | – | – |
| query | string | – | Natural-language search query |
| region | string | – | Region key, one of: europe, dach |
No output schema declared.
No examples provided.
What is the HeatPulse MCP server?
HeatPulse is an MCP server listed in the public MCP registry as cc.heatpulse/heatpulse. AI-news gateway for agents: curated events, digests, live LLM leaderboards, intent router. This page covers its hosted endpoint (https://heatpulse.cc/mcp).
Is the HeatPulse MCP server safe to use?
HeatPulse scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HeatPulse MCP server expose?
HeatPulse exposes 8 tools: search_news, get_event, related_stories, daily_digest, list_topics, and 3 more. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.
Does the HeatPulse MCP server require authentication?
No. We connected to HeatPulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HeatPulse MCP server still maintained?
HeatPulse is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.