HeatPulse MCP server
cc.heatpulse/heatpulseheatpulse.ccstreamable-httpv1.0.0Scanned
AI-news gateway for agents: curated events, digests, live LLM leaderboards, intent router.
8 tools: 3 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the HeatPulse MCP server can do
The HeatPulse MCP server is published by heatpulse.cc, a domain the MCP Registry verified. It has 8 tools. It can create or change data (3 tools: related_stories, daily_digest and llm_leaderboard), but cannot delete data. 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 3Claude Code: ask
daily_digestThe daily editorial digest for a date (YYYY-MM-DD) or the latest one: intro paragraph, stats, and the day's featured events.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it The daily editorial digest for a date (YYYY-MM-DD) or the latest one: intro paragraph, stats, and the day's featured events.
llm_leaderboardLive LLM arena leaderboards (text/code/agent/document/vision/search).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 5Show 5 read-only tools
get_eventOne AI-news event by slug: full editorial summary plus its outbound coverage list (outlet name, link, language, time — no publisher headlines).No findings
Why it is in this group
- The name "get_event" says "get": a word for reading.
Description, as the server wrote it One AI-news event by slug: full editorial summary plus its outbound coverage list (outlet name, link, language, time — no publisher headlines).
list_datasetsBulk JSONL dataset manifest (events corpus, entities, leaderboard history, digests) for RAG/fine-tune pulls.No findings
Why it is in this group
- The name "list_datasets" says "list": a word for reading.
Description, as the server wrote it Bulk JSONL dataset manifest (events corpus, entities, leaderboard history, digests) for RAG/fine-tune pulls.
list_topicsExtracted entities (companies, models, people, themes) ranked by coverage count.No findings
Why it is in this group
- The name "list_topics" says "list": a word for reading.
Description, as the server wrote it Extracted entities (companies, models, people, themes) ranked by coverage count.
route_intentDescribe what knowledge you need in natural language; get back the right HeatPulse endpoint(s) and authoritative external sources, each with a "why".No findings
Why it is in this group
- The description's first verb is "describe": a word for reading.
Description, as the server wrote it Describe what knowledge you need in natural language; get back the right HeatPulse endpoint(s) and authoritative external sources, each with a "why".
search_newsSearch or list AI news events.No findings
Why it is in this group
- The name "search_news" says "search": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://heatpulse.cc/mcp: tools/list returned 8 tools to an anonymous client, including related_stories (write), daily_digest (write), llm_leaderboard (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http heatpulse https://heatpulse.cc/mcpclaude mcp add --transport http heatpulse https://heatpulse.cc/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__heatpulse__search_news",
"mcp__heatpulse__get_event",
"mcp__heatpulse__list_topics",
"mcp__heatpulse__route_intent",
"mcp__heatpulse__list_datasets"
],
"ask": [
"mcp__heatpulse__related_stories",
"mcp__heatpulse__daily_digest",
"mcp__heatpulse__llm_leaderboard"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as heatpulse. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/cc.heatpulse/heatpulse/verify?hash=e35765d6e5694f7b3d268b7eca435b2af5905998e06a23e238129a9cc49dbb21" | jq -e '.changed == false'Pinned hash e35765d6e569, from Nov 10, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/cc.heatpulse/heatpulse/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/cc.heatpulse/heatpulse)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:46 UTC.
HeatPulse MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the HeatPulse MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the HeatPulse MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the HeatPulse MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the HeatPulse MCP server have?
- 8 tools: 3 write, 5 read. related_stories, daily_digest, llm_leaderboard, search_news, get_event, list_topics, route_intent and list_datasets.
Does the HeatPulse MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the HeatPulse MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the HeatPulse MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.