Docs

NewsMCP changelog

Client-facing changes only — new tools, new or removed parameters, changed defaults, and limits. Internal refactors, logging, and deployment changes are not listed here.

← Back to docs

0.6.1 — August 21, 2026

  • Fixed 429 errors now reliably distinguish a spent hourly call budget (carries retry_after_seconds — wait that long) from a concurrency conflict (no wait quoted — only one request may be in flight at a time). Earlier releases sometimes reported one as the other for news.

0.6.0 — August 21, 2026

  • Removed offset is gone from news — there's no paging past limit any more; the underlying index dropped support for it.
  • Removed Six more parameters dropped from news (order, to_, enriched_only, min_articles, min_sources, min_confidence), taking it from 19 parameters to 13. Sorting is always most-recent/best-match first, “up to now” is the implicit upper bound, and min_newsrooms is the one corroboration floor worth setting.
  • Added subject parameter on news — pass a company, person, or place name and it's quoted automatically (matches as a phrase, not ANDed words) and widens the default search window to 30 days.
  • Added get_story tool — expand one story by id, with include_sources for the complete source-link list.
  • Added check_coverage tool — judges how widely and independently a claim has been reported, separating independent newsrooms from reprints, and totals the clustered variants of one story across languages.
  • Changed sort is now optional and correctly defaults to relevance when a query is given and newsrooms when it isn't — previously every search was silently forced to newsrooms, ranking by story size instead of match quality.

0.5.0 — August 20, 2026

  • Added check_limits tool — reports the caller's access level, remaining hourly searches, lookback ceiling, and largest allowed limit, at no cost to the caller's own quota.
  • Changed news's limit ceiling lowered to 50 (previously 500), matching the API's page-size cap.
  • Changed The environment variable for providing a key when self-hosting is now NEWSMCP_API_KEY (NEWSMCP_API_TOKEN is a deprecated alias, still read).

0.4.0 — August 20, 2026

  • Fixed Requests exceeding a keyed plan's ceiling (e.g. an oversized limit) previously failed with no explanation; the error now names the field and its maximum so the caller can clamp and retry.
  • Fixed A 404 from news/get_story no longer always claims the story id doesn't exist — it now distinguishes a genuinely unresolved id from a server misconfiguration.

0.3.0 — August 19, 2026

  • Added news — the current search tool, wrapping GET /v0/news / GET /v0/news/{event_id}: query plus event_type/content_type/sector filters, corroboration floors, a story-start window, sorting, paging, verbosity, fetch-by-id, and response_format (markdown/text/json, markdown by default).
  • Removed Breaking. the search_news tool is gone; news is the only search surface. Anything calling search_news by name must switch to news.
  • Removed Breaking. the x-api-token header is no longer accepted; use x-api-key.
  • Fixed Keyed calls were silently being served as keyless due to the server sending the wrong upstream auth header — keys now work correctly and get the full keyed page size.
  • Added news rejects sort="relevance" without a q, with a message pointing at trending or the default instead of letting the call fail upstream.
  • Added Keyless narrowing notices are now shown in markdown/text replies, not just json — previously a narrowed keyless response looked identical to a full one outside of JSON mode.