# HeatPulse (remote · heatpulse.cc)

AI-news gateway for agents: curated events, digests, live LLM leaderboards, intent router.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `heatpulse.cc`: 62/100 (this document), [markdown](https://verifymcp.io/servers/cc-heatpulse-heatpulse/heatpulse.md), [page](https://verifymcp.io/servers/cc-heatpulse-heatpulse/heatpulse)

## Channel facts

- Endpoint: `https://heatpulse.cc/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 471 tokens (~47/item across 10 items; 8 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 77/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 31% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http cc-heatpulse-heatpulse 'https://heatpulse.cc/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "cc-heatpulse-heatpulse": {
      "url": "https://heatpulse.cc/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cc-heatpulse-heatpulse": {
      "type": "http",
      "url": "https://heatpulse.cc/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.cc-heatpulse-heatpulse]
url = "https://heatpulse.cc/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cc-heatpulse-heatpulse": {
      "type": "remote",
      "url": "https://heatpulse.cc/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cc-heatpulse-heatpulse --url 'https://heatpulse.cc/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cc-heatpulse-heatpulse:
    url: "https://heatpulse.cc/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cc-heatpulse-heatpulse": {
      "Transport": "http",
      "Url": "https://heatpulse.cc/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cc-heatpulse-heatpulse -t streamable-http -u 'https://heatpulse.cc/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 62, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 61)

First indexed and scored.

## MCP tools (8)

### `search_news` (~116 tokens)

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.

Input parameters:

- `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

### `get_event` (~36 tokens)

One AI-news event by slug: full editorial summary plus its outbound coverage list (links to original outlets).

Input parameters:

- `slug` (string, required)

### `related_stories` (~34 tokens)

Events most similar to a given event (centroid cosine KNN, max 5).

Input parameters:

- `slug` (string, required)

### `daily_digest` (~49 tokens)

The daily editorial digest for a date (YYYY-MM-DD) or the latest one: intro paragraph, stats, and the day's featured events.

Input parameters:

- `date` (string): YYYY-MM-DD, default latest

### `list_topics` (~32 tokens)

Extracted entities (companies, models, people, themes) ranked by coverage count.

Input parameters:

- `limit` (integer)

### `llm_leaderboard` (~82 tokens)

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.

Input parameters:

- `board` (string)
- `limit` (integer)

### `route_intent` (~52 tokens)

Describe what knowledge you need in natural language; get back the right HeatPulse endpoint(s) and authoritative external sources, each with a "why".

Input parameters:

- `intent` (string, required)
- `limit` (integer)

### `list_datasets` (~35 tokens)

Bulk JSONL dataset manifest (events corpus, entities, leaderboard history, digests) for RAG/fine-tune pulls.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cc-heatpulse-heatpulse/heatpulse#diagnostics

## Score history

- 2026-09-29: 62
- 2026-09-28: 62
- 2026-09-27: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://heatpulse.cc/mcp
- Repository: https://github.com/hungtrungthinh/heatpulse
- Website: https://heatpulse.cc/
- Changelog RSS feed: https://verifymcp.io/servers/cc-heatpulse-heatpulse/heatpulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/cc-heatpulse-heatpulse/heatpulse.json
- HTML version of this page: https://verifymcp.io/servers/cc-heatpulse-heatpulse/heatpulse