Brave Search MCP Server: web results, images, videos, rich results, AI summaries, and more.
Nothing to run from here
Clstr is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
4
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
News for agents: 100k+ articles/day deduplicated into situations with timelines. Free, no key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http clstr-mcp https://mcp.clstr.news/mcp
# 2 — ask your agent for something these tools do
# search_situations, get_situation_timeline, get_top_situations and 1 more
Clstr costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CLAll 1 server
clstr1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http clstr-mcp https://mcp.clstr.news/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
4 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 summar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Topic, entity, company, country, or event to search for. |
| days | integer | no | How far back to search, in days. Default 7, maximum 30. |
| limit | integer | no | 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. |
| summary | string | no | 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_situati |
| cursor | string | no | From a previous result, to page further. Each page counts as one search against your cap. |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| situation_id | string | yes | Situation id or slug (from other tools or clstr.news URLs). |
| timeline_limit | integer | no | 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 |
| timeline_before | string | no | Cursor: cluster id (a UUID) from a previous page, to continue past it. |
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 ou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional category filter. |
| country | string | no | 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. |
| window | string | no | Time window. Default '7d'. |
| sort | string | no | Ordering. 'relevance' (the default) blends significance, source count and recency; 'recent' is newest activity first. |
| limit | integer | no | Max situations to return. Default 15. |
| summary | string | no | 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_situati |
| cursor | string | no | From a previous result, to page further. Pass the same filters alongside it: a cursor resumes only under the filter set that produced it. |
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 li
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cluster_id | string | yes | Cluster id or slug (from timelines, search, or clstr.news URLs). |
| articles | integer | no | 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. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Clstr or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Clstr can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.