Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HeatPulse

REMOTE · HEATPULSE.CC

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

Available components

0 this week 82 Trust /100

Last scanned (16 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category News and Social

Trust breakdown (7 categories)

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 Security66
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability83
  • 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 480 tokens (~48/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +58
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: 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. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 4 Nov 26 −58
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 +5
    • HTTPS: unverified → pass ▲ security
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Nov 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=YE2,O=Let's Encrypt,C=US 17 Nov 2026 15 Feb 2027 ECDSA 256 ECDSA-SHA384 626739071ed17c5b3607d2f4c665c72497e
SANs: *.heatpulse.cc, heatpulse.cc
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 secure

Validation of heatpulse.cc. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cc. DS published 12593 13 Verified
heatpulse.cc. DS published 2371 13 Verified
heatpulse.cc. Verified address RRset verified with the apex keys
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 HTTPS enforced 301 https://heatpulse.cc/mcp
MCP tools · 8 exposed · ~445 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
datestring–YYYY-MM-DD, default latest

No output schema declared.

No examples provided.

get_event ~45

One AI-news event by slug: full editorial summary plus its outbound coverage list (outlet name, link, language, time — no publisher headlines).

NameTypeReqDescription
slugstringyes–

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.

NameTypeReqDescription
limitinteger––

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.

NameTypeReqDescription
boardstring––
limitinteger––

No output schema declared.

No examples provided.

related_stories ~34

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

NameTypeReqDescription
slugstringyes–

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

NameTypeReqDescription
intentstringyes–
limitinteger––

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.

NameTypeReqDescription
categorystring–Category slug, one of: models, products, industry, papers, benchmarks, policy, tips
limitinteger––
orderstring––
querystring–Natural-language search query
regionstring–Region key, one of: europe, dach

No output schema declared.

No examples provided.

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.

remote · heatpulse.cc

# add to Claude Code
claude mcp add --transport http cc-heatpulse-heatpulse 'https://heatpulse.cc/mcp'
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 82 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 445 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the HeatPulse MCP server?

VerifyMCP ran 12 checks on HeatPulse, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about HeatPulse: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.