AI & Machine Learning

heatpulse.cc

Provides tools for searching, retrieving, and analyzing AI news events, topics, and daily digests from editorial coverage.

1 endpoint8 known tools

ENDPOINT 1

https://heatpulse.cc/mcp

No auth detected

MCP server metadata

Name: heatpulse
Version: 1.0.0

Capabilities

tools.listChangedresources.listChangedprompts.listChanged

Known tools 8

search_news

Search or list AI news events.

Inferred read-only

get_event

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

Inferred read-only

related_stories

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

Inferred read-only

daily_digest

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

Inferred read-only

list_topics

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

Inferred read-only

llm_leaderboard

Live LLM arena leaderboards (text/code/agent/document/vision/search).

Inferred read-only

route_intent

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

Inferred read-only

list_datasets

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.heatpulse]
url = "https://heatpulse.cc/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "heatpulse": {
      "type": "http",
      "url": "https://heatpulse.cc/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: heatpulse
Remote MCP URL: https://heatpulse.cc/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "heatpulse",
  "transport": "streamable-http",
  "url": "https://heatpulse.cc/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.