Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
CLSTR News Tracker
Claude
–

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

The two entities (cluster = single event, situation = storyline) are cleanly split: get_cluster is the only event-level detail tool, and the three situation tools split along browse-vs-search-vs-timeline axes. get_top_situations ('what's happening now, no topic') versus search_situations ('what's happening around X') is an unusually explicit boundary, and each description tells you which other tool to chain into.

Naming Consistency4/5

Consistent snake_case with a get_/search_ verb_noun pattern, and the resource nouns (cluster, situation) match the domain vocabulary used in the descriptions. The single search_ verb among three get_ verbs is a minor, defensible deviation rather than a convention break.

Tool Count4/5

Four tools is on the lean side but each maps to a distinct entry point (browse, search, timeline, event detail) with no filler. The deliberate omission of a standalone get_situation is handled by get_situation_timeline returning the summary, so nothing feels redundant.

Completeness4/5

Discovery (top/search) plus drill-down (timeline/cluster) covers the core read-only workflow, including pagination and merged-id handling. Minor gaps exist around category/country enumeration and source-level access, but agents can work around them via filters and the per-cluster source links.

Available Tools

4 tools
get_clusterGet a news eventA
Read-onlyIdempotent
Inspect

Get one news event in detail. A cluster is a single real-world event grouped from the outlets covering it 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 links to its source articles (outlet, headline, URL and date). It returns up to 100 of those links, one per outlet; 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. Results carry canonical clstr.news links. (Requires sign-in, or a free API key: https://clstr.news/developers)

Inputs: cluster_id (required), articles. Returns: data

get_situation_timelineGet a situation timelineA
Read-onlyIdempotent
Inspect

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 grouped from the outlets covering it 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. Results carry canonical clstr.news links.

Inputs: situation_id (required), timeline_limit, timeline_before. Returns: data

get_top_situationsTop developing situationsA
Read-onlyIdempotent
Inspect

List the situations developing 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 ' or 'what is happening in ' 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. Results carry canonical clstr.news links.

Inputs: sort, limit, cursor, window, +3 more. Returns: data, next_cursor, window_days, summary_mode

search_situationsSearch news situationsA
Read-onlyIdempotent
Inspect

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 grouped from the outlets covering it 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. Results carry canonical clstr.news links. (Requires sign-in, or a free API key: https://clstr.news/developers)

Inputs: query (required), days, limit, cursor, +1 more. Returns: data, query, next_cursor, summary_mode

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Real-time financial news for AI agents and trading bots — AI-enriched stories with per-ticker analysis, a 1–10 relevance score, SEC Form-4 insider transactions, plus trending and "actionable-now" feeds. Free tier, OAuth, no API key to paste.
      2
      11
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Real-time curated knowledge API for AI agents. Updated Mon/Wed/Fri from 31 sources covering AI/tech, startups, alternative markets, and emerging markets — no scraping or storage required.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides AI agents with global tech news from 500+ sources across regions, with translated titles, scoring, and clustering tools for real-time intelligence.
      8
      42 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources