news.clstr/clstr
REMOTE · MCP.CLSTR.NEWS · SCANNED AUG 20
News for agents: 100k+ articles/day deduplicated into situations with timelines. Free, no key.
Available components
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 →
Endpoint Security63
- 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 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. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.clstr.news
claude mcp add --transport http news-clstr-clstr https://mcp.clstr.news/mcp
[mcp_servers.news-clstr-clstr] url = "https://mcp.clstr.news/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"news-clstr-clstr": {
"type": "remote",
"url": "https://mcp.clstr.news/mcp",
"enabled": true
}
}
} openclaw mcp add news-clstr-clstr --url https://mcp.clstr.news/mcp --transport streamable-http
mcp_servers:
news-clstr-clstr:
url: "https://mcp.clstr.news/mcp" {
"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.
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.
- 20 Aug 26 61
First indexed and scored.
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 20 Aug 2026 · Probed https://mcp.clstr.news/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=clstr.news | CN=WE1,O=Google Trust Services,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 33090dd6529ca76b138705637f620deb |
| SANs: clstr.news, mcp.clstr.news, *.mcp.clstr.news | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.clstr.news. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| news. | present | 39979 | 8 | Verified |
| clstr.news. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=2592000 |
| content-security-policy | default-src 'self'; base-uri 'self'; frame-ancestors 'none'; img-src 'self' data: https:; font-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' https://scripts.simpleanalyticscdn.com 'nonce-nCYaLIzmTJIpk5hVmfsLZQ'; connect-src 'self' https://scripts.simpleanalyticscdn.com https://queue.simpleanalyticscdn.com; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), ambient-light-sensor=(), autoplay=(), battery=(), camera=(), display-capture=(), document-domain=(), encrypted-media=(), execution-while-not-rendered=(), execution-while-out-of-viewport=(), fullscreen=(), gamepad=(), geolocation=(), gyroscope=(), hid=(), identity-credentials-get=(), idle-detection=(), interest-cohort=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), screen-wake-lock=(), serial=(), speaker-selection=(), usb=(), web-share=(), xr-spatial-tracking=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.clstr.news/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.clstr.news/mcp | HTTPS enforced | 301 | https://mcp.clstr.news/mcp |
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.
get_cluster Get a news event ~173
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)
| Name | Type | Req | Description |
|---|---|---|---|
| cluster_id | string | yes | Cluster id or slug (from timelines, search, or clstr.news URLs). |
No output schema declared.
No examples provided.
get_situation_timeline Get a situation timeline ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| situation_id | string | yes | 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 |
No output schema declared.
No examples provided.
get_top_situations Top developing situations ~239
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'. |
No output schema declared.
No examples provided.
search_situations Search news situations ~335
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)
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Topic, entity, company, country, or event to search for. |
No output schema declared.
No examples provided.