# news.clstr/clstr (remote · mcp.clstr.news)

News for agents: 100k+ articles/day deduplicated into situations with timelines. Free, no key.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `mcp.clstr.news`: 61/100 (this document), [markdown](https://verifymcp.io/servers/news-clstr-clstr/mcp.md), [page](https://verifymcp.io/servers/news-clstr-clstr/mcp)

## Channel facts

- Endpoint: `https://mcp.clstr.news/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-08-20.

- **Endpoint Security**: 63/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 4 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 is enforced; there's no plaintext access path.
  - 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**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1385 tokens (~346/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http news-clstr-clstr https://mcp.clstr.news/mcp
```

### Codex

```toml
[mcp_servers.news-clstr-clstr]
url = "https://mcp.clstr.news/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add news-clstr-clstr --url https://mcp.clstr.news/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  news-clstr-clstr:
    url: "https://mcp.clstr.news/mcp"
```

### Other

```json
{
  "mcpServers": {
    "news-clstr-clstr": {
      "type": "http",
      "url": "https://mcp.clstr.news/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-08-20 (score 61)

First indexed and scored.

## MCP tools (4)

### `search_situations` (~335 tokens)

Search news situations

Search the news by topic to find matching situations and events. A situation is an ongoing storyline (story arc) that groups related events over time; an event, called a cluster, is one happening assembled from many outlets and deduplicated into a single item, so you get one event rather than 20 near-duplicate headlines. Results come back grouped under their situations, each with a one-line summary, a significance score (1 to 10, where 8 and above is exceptional), a source count (how many outlets are covering it), and a canonical clstr.news link. Use this to answer 'what is happening around X' for a topic, company, country, or event. Then open a result with get_situation_timeline for the full history, or get_cluster for one event's detail. Results are relevance ordered and bounded to the top matches: when there are more, the result ends with a cursor to pass back, and each page counts as one search against your cap. Cite the returned URLs. (Requires a free API key: https://clstr.news/developers)

Input parameters:

- `cursor` (string): From a previous result, to page further. Each page counts as one search against your cap.
- `days` (integer): How far back to search, in days. Default 7, maximum 30.
- `limit` (integer): Max events to return. Default 15. They are grouped under their situations in the result, so you may see fewer situation headings than this number.
- `query` (string, required): Topic, entity, company, country, or event to search for.

### `get_situation_timeline` (~246 tokens)

Get a situation timeline

Get the full chronological timeline of one situation. A situation is an ongoing storyline (story arc) that groups related news events over time; it carries a maintained summary plus every event in order, so you see not just what happened but how it developed. Each event is a cluster (one happening assembled from many outlets and deduplicated) with its date, a significance score (1 to 10, where 8 and above is exceptional), a source count, and a canonical clstr.news link. Use this to brief on a story's history or answer 'how did this develop'. Get a situation id from search_situations or get_top_situations, or from a clstr.news URL. Cite the returned URLs.

Input parameters:

- `situation_id` (string, required): Situation id or slug (from other tools or clstr.news URLs).
- `timeline_before` (string): Cursor: cluster id from a previous page to continue past.
- `timeline_limit` (integer): Timeline entries to return, newest first. Default 50, and 50 is also the maximum without an API key. A free key raises it to 500: https://clstr.news/developers

### `get_top_situations` (~239 tokens)

Top developing situations

List the situations developing right now, ranked by relevance: a blend of significance, how many outlets are covering it, and how recently it moved. So a lower significance score can rank above a higher one, and that ordering is intentional; do not re-sort. A situation is an ongoing storyline that groups related news events over time and carries a maintained summary and a source count (how many outlets are behind it). Optionally filter by category and by time window (24h, 7d, or 30d). Use this to answer 'what is going on in the world' or 'what is happening in <category>' when there is no specific topic yet, then open any result with get_situation_timeline. When there are more, the result ends with a cursor to page further. Cite the returned URLs.

Input parameters:

- `category` (string): Optional category filter.
- `cursor` (string): From a previous result, to page further. Pass the same window and category alongside it.
- `limit` (integer): Max situations to return. Default 15.
- `window` (string): Time window. Default '7d'.

### `get_cluster` (~173 tokens)

Get a news event

Get one news event in detail. A cluster is a single real-world event assembled from many outlets covering the same happening and deduplicated into one item, so you get one event rather than 20 near-duplicate headlines. Returns its summary, a significance score (1 to 10, where 8 and above is exceptional), a source count, the situation it belongs to if any, and every underlying source article with links. Use this when the user wants the specifics of one event. Get a cluster id from search_situations, get_situation_timeline, or a clstr.news URL. Cite the returned URLs. (Requires a free API key: https://clstr.news/developers)

Input parameters:

- `cluster_id` (string, required): Cluster id or slug (from timelines, search, or clstr.news URLs).

## Diagnostics

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

## Score history

- 2026-08-20: 61

## Links

- Remote endpoint: https://mcp.clstr.news/mcp
- Website: https://clstr.news/
- Changelog RSS feed: https://verifymcp.io/servers/news-clstr-clstr/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/news-clstr-clstr/mcp.json
- HTML version of this page: https://verifymcp.io/servers/news-clstr-clstr/mcp