> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nordicfinancialnews.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> New features, improvements, and bug fixes across the Nordic Financial News API, MCP server, and CLI.

<Note>
  Looking for feature announcements and product news? Those live on [Product Updates](https://nordicfinancialnews.com/updates).
</Note>

<Update
  label="August 21, 2026"
  description="MCP list_watchlist no longer repeats companies"
  tags={["MCP"]}
  rss={{
title: "MCP list_watchlist no longer repeats companies across watchlists",
description: "Calling the MCP list_watchlist tool without a watchlist_id returned a company once per watchlist it was on. Each followed company is now listed once."
}}
>
  ## MCP `list_watchlist` no longer repeats companies

  Calling the MCP [`list_watchlist`](/model-context-protocol/tools#list_watchlist) tool without a `watchlist_id` lists every company you follow across all of your watchlists. A company you follow on more than one watchlist appeared once per watchlist it belonged to. Each followed company is now listed once, regardless of how many of your watchlists it is on.

  This affects the combined view only. Passing a `watchlist_id` to scope the call to a single list was never affected, and the companies it returns are unchanged.
</Update>

<Update
  label="August 7, 2026"
  description="Stories on the free plan"
  tags={["API", "MCP"]}
  rss={{
title: "Stories now follow the same plan model as articles",
description: "Story access is no longer a hardcoded pair of stories. Your plan applies a time window, then each endpoint applies its own count cap, and paid plans stay unlimited. The MCP story tools now return capped results instead of refusing."
}}
>
  ## Stories follow the same plan model as articles

  On the free plan you previously saw the same two stories across the whole API: the most important one and the most recent one. Stories now work the way articles already did. Your plan applies a time window, then each endpoint applies its own count cap. Paid plans stay unlimited.

  The current free-plan window and caps are listed on the [pricing page](https://nordicfinancialnews.com/pricing). See [List stories](/api-reference/stories/list-stories) for the parameters each endpoint accepts.

  ### MCP story tools return results instead of refusing

  `search_stories` and `get_story` previously answered with a "not available on your current plan" refusal. They now return capped results, marked with `plan_limited`.

  Story search also applies the same window and cap as the list endpoints, which it did not do before.

  ### Telling a capped response apart

  Any response your plan restricted carries `plan_limited: true`, so you can tell a partial result from a complete one. The field is absent when your plan applies no restriction.

  ```json Story list response on a capped plan theme={"dark"}
  {
    "stories": [],
    "pagination": { "has_more": false },
    "plan_limited": true
  }
  ```

  ### The caps are volume limits, not access control

  A story outside the cap still opens by ID, as long as it falls inside your plan's age window. So a shared link keeps working even once that story has dropped out of your list results.
</Update>