news.clstr/clstr
REMOTE · MCP.CLSTR.NEWS
News for agents: 100k+ articles/day deduplicated into situations with timelines. Free, no key.
Available components
Last scanned (16 hours ago)
Scores higher than 90% of remote servers
Reachable. Last reached 16 Oct 2026.
Category News and Social
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1930 tokens (~482/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 28 Sept 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
- 25 Sept 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
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 0
- Tool “get_cluster” rewrote its description, which is the text the model reads security
- Tool “get_situation_timeline” rewrote its description, which is the text the model reads security
- Tool “get_top_situations” rewrote its description, which is the text the model reads security
- Tool “search_situations” rewrote its description, which is the text the model reads security
- Schema quality: 378 → 482 ▼ functional
- “get_cluster” added an optional parameter “articles” cosmetic
- “get_top_situations” added an optional parameter “summary” cosmetic
- “search_situations” added an optional parameter “summary” cosmetic
- 16 Sept 26 +8
- Authorization: unverified → partial ▲ security
- Tool “get_top_situations” rewrote its description, which is the text the model reads security
- Tool “get_cluster” now declares an output schema ▲ functional
- Tool “get_situation_timeline” now declares an output schema ▲ functional
- Tool “get_top_situations” now declares an output schema ▲ functional
- Tool “search_situations” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- “get_top_situations” added an optional parameter “country” cosmetic
- “get_top_situations” added an optional parameter “sort” cosmetic
- “get_situation_timeline” reworded the description of “timeline_before” cosmetic
- “get_top_situations” reworded the description of “cursor” cosmetic
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 0
- Tool “get_cluster” rewrote its description, which is the text the model reads security
- Tool “search_situations” rewrote its description, which is the text the model reads security
- 26 Aug 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
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 16 Oct 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 | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8bf5c9a85e217922138d4044a813c5ef |
| 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 |
Background: What to check on a remote MCP endpoint →
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-TxXwCg6pn8XvStwEadIFDA'; 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=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. 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 →
get_cluster Get a news event ~259
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 its underlying source articles with links. It returns up to 100 representative articles, one per source; `sources` and `articles_total` are the full count, and `articles_truncated` says whether the list was cut. 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 sign-in, or a free API key: https://clstr.news/developers)
| Name | Type | Req | Description |
|---|---|---|---|
| articles | integer | – | How many source articles to return, 1 to 100. Default 100. Lower it when you only need a few citations; the source count is reported separately and is unaffected. |
| cluster_id | string | yes | Cluster id or slug (from timelines, search, or clstr.news URLs). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
get_situation_timeline Get a situation timeline ~273
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. An id that was retired when two situations merged resolves to the successor, flagged with merged_into_shown. 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 (a UUID) from a previous page, to continue past it. |
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
No examples provided.
get_top_situations Top developing situations ~550
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, by country, and by time window (24h, 7d, or 30d), and switch the ordering to newest activity first with sort. Use this to answer 'what is going on in the world', 'what is happening in <category>' or 'what is happening in <country>' 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. Pass summary: "full" to get each situation's maintained summary in full, instead of a one-line preview, without a follow-up call per result; full summaries in a list are not enabled for every account, so read summary_mode in the result to see what you got, and use get_situation_timeline for one situation's summary in full. Cite the returned URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter. |
| country | string | – | Optional country filter: comma-separated ISO 3166-1 alpha-2 codes, for example "US,GB". Up to 10 at once. A situation matches if it is covered in any of them. |
| cursor | string | – | From a previous result, to page further. Pass the same filters alongside it: a cursor resumes only under the filter set that produced it. |
| limit | integer | – | Max situations to return. Default 15. |
| sort | string | – | Ordering. 'relevance' (the default) blends significance, source count and recency; 'recent' is newest activity first. |
| summary | string | – | How much summary text each row carries. 'preview' (the default) is a one-line preview; 'full' returns the maintained summary in full, so you do not need a follow-up call per result. On get_top_situat… |
| window | string | – | Time window. Default '7d'. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| next_cursor | string|null | yes | Pass back as cursor to page further. Null at the end. |
| summary_mode | string | yes | The summary mode this result was served in, which is not always the one requested. |
| window_days | integer | yes | The time window this result covers, in days, which is not always the one requested. |
No examples provided.
search_situations Search news situations ~456
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. Pass summary: "full" to read each match's summary untruncated instead of one line. Cite the returned URLs. (Requires sign-in, or 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. |
| summary | string | – | How much summary text each row carries. 'preview' (the default) is a one-line preview; 'full' returns the maintained summary in full, so you do not need a follow-up call per result. On get_top_situat… |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| next_cursor | string|null | yes | Pass back as cursor to page further. Each page is one search. |
| query | object | yes | The query as actually run: `days` is the EFFECTIVE window after tier and index clamps. |
| summary_mode | string | yes | The summary mode this result was served in, which is not always the one requested. |
No examples provided.
How do I install the news.clstr/clstr MCP server?
news.clstr/clstr is a hosted endpoint at https://mcp.clstr.news/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 · mcp.clstr.news
claude mcp add --transport http news-clstr-clstr 'https://mcp.clstr.news/mcp'
What is the news.clstr/clstr MCP server?
news.clstr/clstr is an MCP server listed in the public MCP registry as news.clstr/clstr. News for agents: 100k+ articles/day deduplicated into situations with timelines. Free, no key. This page covers its hosted endpoint (https://mcp.clstr.news/mcp).
Is the news.clstr/clstr MCP server safe to use?
news.clstr/clstr scores 83 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 news.clstr/clstr MCP server expose?
news.clstr/clstr exposes 4 tools: search_situations, get_situation_timeline, get_top_situations, get_cluster. Their descriptions and schemas cost roughly 1,538 tokens of context every time the server is loaded.
Does the news.clstr/clstr MCP server require authentication?
No. We connected to news.clstr/clstr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the news.clstr/clstr MCP server still maintained?
news.clstr/clstr is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.