NewsMCP

Search already-synthesized news events — pre-built story digests — or fetch one by id. Each story comes with a generated headline, one-liner, abstract, key actors, and industry/event-type labels. Use it for a quick digest of what happened, for deal/incident-type or industry filtering, and for corroboration ranking. Nothing is required: a bare call returns the most-corroborated stories of the last 24 hours. Limits — keyless: 7-day `from_` lookback, 20 calls/hour, 20 stories per call, over-limit narrowed with a notice. With a key: per-plan ceilings (free tier today 14 days, 50 calls/hour, 50 stories), over-limit rejected rather than narrowed. Call `check_limits` for the live numbers; it is free and never spends the budget it reports on. Filters combine with AND; `event_type`, `content_type`, and `sector` each accept several comma-separated values combined with OR.

Expand one story: full summary, classification, actors, and source links. Use this after any search, when the user wants more than the digest line for a particular story. It is the only tool that can return a story's complete source list.

Judge how widely and how independently a claim has been reported. Answers "is this real?" rather than returning a list. Reports the number of INDEPENDENT newsrooms — outlets that reported it themselves — separately from the number of domains that carried it, which includes syndication. A story on 200 domains from 3 newsrooms is one story reprinted, not 200 confirmations. Because upstream clustering splits a story across languages, this totals the likely variants of the same story and presents that total as an upper bound, listing what was combined so the caller can check it is really one story.

Report what this caller may do right now — and never spend any of it to find out. Answers the questions the `news` tool descriptions cannot: how many searches are left this hour, how far back this plan reaches, the largest `limit` it allows, how many searches may run at once, and how long to wait if the budget is spent. These ceilings are per-plan and change without a release, so trust this over any number written into a description. Checking is free: the endpoint is exempt from every metering stage, so calling it does not consume an hourly call, a concurrency slot, or a credit. Reach for it before planning a batch of calls, and after any plan-limit or rate-limit error instead of guessing the ceiling that was hit.

Check whether the NewsMCP REST API is reachable and healthy. Does not require an API token. Use when diagnosing connectivity, not for searching news. For allowances and remaining budget use `check_limits` instead. Returns: str: Health status reported by the API.

Takes no parameters.