Skip to main content
Glama
finance-pulse

finance-pulse

Finance Pulse: Python client and MCP server

Financial news as structured, sourced data. Finance Pulse gives you financial news as statements: one-sentence facts from each article, with sentiment, importance, tickers, sector, source, headline and publication time. Statements about the same development are grouped into topics; one company's topics that continue each other form a storyline; and topics belong to standing themes. fintopic.news is a front page built on the same API.

The same setup guide, with the other guides and the API reference, is on the docs site: Use Finance Pulse from Claude, Cursor or Python.

This package gives you two ways to use it:

  • a Python client for scripts, notebooks and pipelines;

  • an MCP server, so Claude, Cursor and other MCP clients can query the news directly.

You need a RapidAPI key that is subscribed to Finance Pulse. Create a RapidAPI account, open the plans page and subscribe to a plan: there is a free one to try everything below. Then copy your X-RapidAPI-Key from the API's page on RapidAPI (the endpoint playground shows it). A key that is not subscribed to a plan is answered with 403.

Use it from Claude or Cursor (MCP)

The server runs with uvx, which is part of uv: install uv first. The package itself needs no separate install.

Claude Code

claude mcp add --env RAPIDAPI_KEY=YOUR_RAPIDAPI_KEY --transport stdio finance-pulse -- uvx finance-pulse

Claude Desktop and Cursor

  • Claude Desktop: Settings > Developer > Edit Config opens claude_desktop_config.json (macOS ~/Library/Application Support/Claude/, Windows %APPDATA%\Claude\). Quit and restart Claude Desktop completely afterwards.

  • Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "finance-pulse": {
      "command": "uvx",
      "args": ["finance-pulse"],
      "env": { "RAPIDAPI_KEY": "YOUR_RAPIDAPI_KEY" }
    }
  }
}

If the server does not start in Claude Desktop, it usually cannot find uvx: put the full path (the output of which uvx, or where uvx on Windows) in "command".

uvx keeps the version it installed first. To move to a new release, use finance-pulse@latest in place of finance-pulse once, or run uv cache clean finance-pulse.

Then ask things like:

  • "What is going on with Nvidia? Give me the picture, then the key facts with sources."

  • "Which tickers are suddenly getting more coverage than yesterday?"

  • "What are the ongoing stories about Microsoft, and how did the biggest one unfold?"

  • "What are the top developing stories in Energy, and how did the biggest one grow?"

  • "Show me Tesla's daily news sentiment for the last two weeks."

Tools

Tool

What it does

get_symbol

Everything about one company or other entity in one call: counts and sentiment per period, largest topics, storylines, related entities, newest statements

find_symbol

A company's code from its name ("micron" finds MU)

search_statements

Statements by symbol, sector, theme, topic, storyline, sentiment, minimum importance and time range

trending

The developments most outlets are reporting right now, or the top of each recent time slot

find_topics

Developments for a symbol, sector, theme or storyline, by velocity, size or recency

get_topic

One development: counts, its mix of news, analysis and reddit statements, its storylines, newest statements with their outlets

storylines

One company's news grouped into continuing stories: an event, then its follow-ups and reactions

get_storyline

One storyline: its topics in order and its newest statements

sentiment_series

Daily or hourly news volume and sentiment for a symbol, sector, theme or topic

screen

Symbols (optionally only equities and ETFs) or sectors ranked by news attention and its change, for the last day, week or any interval

themes

The standing subjects with their volume and sentiment, optionally only those a symbol or sector appears in

reference

How far back your plan's history goes, counts, theme ids and accepted filter values

Each tool call is normally one API request. Results are trimmed and come in small pages.

Related MCP server: news-sentiment-mcp

Use it from Python

pip install finance-pulse
export RAPIDAPI_KEY=YOUR_RAPIDAPI_KEY

The MCP SDK is installed with the package even if you only use the client.

from datetime import datetime, timedelta, timezone

from finance_pulse import FinancePulse

fp = FinancePulse()          # or FinancePulse("YOUR_RAPIDAPI_KEY")

# The newest key facts about a ticker
for s in fp.statements(symbol="NVDA", importance_min="high", limit=5)["data"]:
    print(s["published_at"][:16], s["sentiment"], s["statement"], f"({s['source_domain']})")

# One company in one call: counts per period, largest topics, storylines, newest statements
nvda = fp.symbol("NVDA")["data"]
week = nvda["periods"].get("w")           # a period without mentions is left out
if week:
    print(nvda["name"], week["mentions"], "mentions this week, score", week["score"])

# A company's news as continuing stories
for line in fp.storylines(symbol="MSFT", min_topics=2, sort="mentions", limit=5)["data"]:
    print(line["topics"], "topics,", line["mentions"], "mentions:", line["name"])

# Which tickers are suddenly in the news (kind= leaves out rates, central banks, countries, ...)
for row in fp.symbols(period="d", sort="change", kind=["equity", "etf"], limit=10)["data"]:
    print(row["id"], row["mentions"], row["change"])

# Daily news volume and sentiment, last two weeks
since = (datetime.now(timezone.utc) - timedelta(days=14)).strftime("%Y-%m-%dT00:00:00Z")
for b in fp.series(symbol="TSLA", interval="day", since=since)["data"]["buckets"]:
    print(b["t"][:10], b["count"], b["score"])

# What most outlets are reporting right now
for t in fp.trending(kind="live")["data"][:10]:
    print(t["sources"], "sources:", t["name"])

Every method returns the API's JSON unchanged: {"data": ..., "next_cursor": ..., "snapshot": {...}} (iter_statements and poll_feed yield its rows one by one). The snapshot block carries the times the data refers to (window_start, anchor, lag_days), and every statement carries published_at and indexed_at.

Follow the news without missing anything

poll_feed yields every new statement in the order it entered the API and keeps its position in a file, so it survives restarts: after a crash nothing is skipped and only the statement you were working on is delivered again. The first run, with no saved position, starts at the feed's default starting point (a limited time back, not the beginning of the data), and the position is first stored once that first page has been handled. After a long pause the poller reads the whole backlog since its saved position, as far back as your plan's history reaches, at least one request per 100 statements; delete the cursor file to start afresh instead.

for s in fp.poll_feed(sector="Energy", importance_min="high", cursor_file="energy.cursor.json"):
    print(s["indexed_at"], s["statement"], s["source_url"])

The poller pauses 150 seconds between polls unless you pass interval=. Every poll is one request (and so is every retry), so at the default a poller that runs all month makes about 17,000 requests: set interval= to fit your plan's monthly quota (a month has about 2.6 million seconds; divide by the requests you want to spend on polling). Timeouts, server errors and a passing 429 (the plan's rate limit, or too many requests at once) are retried for as long as they last, with a pause that grows to 5 minutes, and each retry is logged as a warning on the finance_pulse logger. A used-up quota, or a 429 that asks to wait more than 5 minutes, is raised at once.

More than one page

rows = list(fp.iter_statements(symbol=["NVDA", "AMD"], importance_min="medium", max_items=1000))

Each page of 100 is one request (and each retry one more). Without max_items it stops after 500 rows; max_items=None reads to the end of the data.

Errors

from finance_pulse import FinancePulseError

try:
    fp.statements(symbol="S&P")
except FinancePulseError as e:
    print(e.status, e.title, e.detail, e.param)
    # 400 Invalid symbol 'S&P' is not a ticker symbol

A 429 means too many requests: the plan's quota is used up (e.quota_used_up is true), the plan's rate limit was reached, or too many requests are open at once; the last two usually pass on their own. Send requests one after another rather than many in parallel. Timeouts and network failures are raised as FinancePulseError too, with status 0; e.transient is true for those and for 5xx answers. e.retry_after says how long to wait when the API gives a time.

Single calls raise every error at once. iter_statements retries a page up to five times in a row after a temporary failure or a passing 429, with a growing pause; poll_feed keeps retrying those for as long as they last (see above). Both raise at once a used-up quota and a 429 that asks to wait more than 5 minutes.

Methods

Method

Endpoint

statements, iter_statements, statement

/v2/statements, /v2/statements/{id}

feed, poll_feed

/v2/feed

series

/v2/series

symbols, symbol, sectors

/v2/symbols, /v2/symbols/{code}, /v2/sectors

trending

/v2/trending

topics, topic

/v2/topics, /v2/topics/{id}

storylines, storyline

/v2/storylines, /v2/storylines/{id}

themes, theme

/v2/themes, /v2/themes/{id}

meta

/v2/meta

Parameters, response fields and limits are documented in the API reference, and the guides show complete worked examples. fp.get("/v2/...", **params) calls any endpoint the client has no method for yet.

What the data is, and is not

  • Symbols are canonical entity codes with a kind. Equities and ETFs appear under their ticker (NVDA, 0700.HK); indices, rates, currencies, crypto, commodities and organisations under short codes (SPX, USD, BTC, FED). Use kind=["equity", "etf"] for tradable tickers only, and symbols(q="name", period="window") to find a code.

  • Sentiment describes the statement, not a price forecast. A symbol's sentiment is the count of its statements' labels.

  • Topics and storylines are grouped automatically and can be wrong or incomplete: a reading aid, not a count of events.

  • How far back you can read depends on your plan. window_start in every response says where your history starts and meta() gives it in days (window_days); older statements are not returned.

See the docs for the full list of caveats.

Development

pip install -e ".[dev]"
pytest

The tests use canned responses and make no API requests.

Releasing

  1. Set the new version in src/finance_pulse/__init__.py and in server.json (two places).

  2. Build and upload to PyPI (uv build && uv publish). From GitHub Actions, use pypa/gh-action-pypi-publish v1.14.2 or newer: older versions reject the metadata version this build writes.

  3. Only then run mcp-publisher publish: the registry verifies the package on PyPI (it looks for the mcp-name line in its description), so the release must be there first.

Licence

MIT

Available Tools

12 tools
find_symbolFind a symbol's code by nameA
Read-onlyIdempotent

Look up the code of a company, index, currency, commodity or organisation by name: "micron" finds MU. The query is matched against codes and registered names, so use the company's own name rather than a brand (Alphabet, not Google). Returns the matches mentioned within the plan's history, most mentioned first, each with its code (id), name and kind; an empty list means nothing there matches, and a list as long as limit may have more matches behind it. Use the code as symbol or code in the other tools.

Inputs: query (required), limit.

find_topicsFind developmentsA
Read-onlyIdempotent

List developments for a symbol, sector, theme or storyline. sort=velocity: most statements in the last 24 hours; size: most statements; recent: latest statement first. symbol: comma-separate several (OR). Topics with fewer than 3 statements are left out unless you lower min_statements, so an empty list can mean "only small ones": retry with min_statements=1. With storyline_id every topic of the storyline is listed by default (sort="oldest" gives them in order).

Inputs: sort, limit, cursor, sector, +4 more.

get_storylineGet one storylineA
Read-onlyIdempotent

One storyline in full: its topics, oldest first (how the story unfolded), and its newest statements. If topics is larger than the members list, ask again with members at its maximum; for a storyline longer than that, page through all of them with find_topics(storyline_id=..., sort="oldest"). While the list is cut, top_topics names the storyline's largest topics. more_statements says whether it has more statements than shown. If you expect to need them, ask for statements at its maximum: only then is statements_cursor set, and search_statements(storyline_id=..., cursor=...) continues exactly after them (add symbol to keep only those naming the company). With fewer, the cursor is null and search_statements(storyline_id=...) starts again at the newest, repeating the ones shown here.

Inputs: storyline_id (required), members, statements.

get_symbolEverything about one symbolA
Read-onlyIdempotent

One company or other entity in a single call. Use first for "what is going on with X".

Returns who it is (name, kind, exchange); its mentions, topics, distinct sources, sentiment counts and score for the last 24 hours (d), the last 7 days (w) and all the history the plan includes, with the change against the period before and the counts over statements that name only this entity (mentions_single, score_single); the sectors of its statements; its largest topics; its storylines with the most mentions lately; the entities it shares topics with (related, empty for a rarely mentioned symbol); and its newest statements. A period without any mention is left out of periods. more_statements says whether the symbol has more statements than shown. If you expect to need them, ask for statements at its maximum: only then is statements_cursor set, and search_statements(symbol=..., cursor=...) continues exactly after them. With fewer, the cursor is null and search_statements(symbol=...) starts again at the newest, repeating the ones shown here. Do not guess a code: a wrong one costs a request. Look it up with find_symbol.

Inputs: code (required), topics, statements.

get_topicGet one developmentA
Read-onlyIdempotent

One development in full: its counts, how many of its statements come from news, speculative analysis and reddit (source_mix), the storylines it belongs to, and its newest statements, each with its outlet and headline. For older statements call search_statements with topic_id and the returned statements_cursor as cursor (null when there are no more).

Inputs: topic_id (required).

referenceHistory reach, counts and accepted valuesA
Read-onlyIdempotent

What the API holds right now: how far back the plan's history goes (window_days), counts of statements, topics, storylines and symbols, the themes with their ids, and the accepted sector, sentiment, importance, source-type and entity-kind values. One call per conversation is enough.

Inputs: no named parameters.

screenScreen symbols or sectors by news attentionA
Read-onlyIdempotent

Rank symbols (or the GICS sectors) by news attention. Use for "which tickers are suddenly in the news".

period: d = last 24 hours, w = last 7 days, window = all the history the plan includes; or pass since (and until) to count any interval. sort=change ranks by the rise in mentions against the period (or equally long interval) before. change is null when there is nothing before to compare with: for period=window, for an interval given only by until, and for an interval whose preceding interval reaches before the plan's history. Use sort=mentions then. Each row: mentions, topics, sources (distinct outlets), sentiment counts, score and change; symbol rows also carry name, kind and the counts over statements naming only that symbol (mentions_single, score_single). Only for rank=symbols: sector limits the screen to one sector; min_mentions drops rarely mentioned codes; entity_kinds narrows the kind of entity (reference lists the kinds). Without it the list mixes companies with rates, commodities and central banks; pass "equity,etf" for tradable tickers.

Inputs: rank, sort, limit, since, +5 more.

search_statementsSearch news statementsA
Read-onlyIdempotent

Search news statements, newest first. Use for "what is the news saying about X".

symbol: ticker or entity code, e.g. NVDA; comma-separate several (OR), no spaces inside a code. importance_min=high keeps only key facts. source_type=news leaves out speculative analysis and reddit. storyline_id: every statement of that storyline's topics; add symbol for only those naming its company. since/until: ISO-8601 times on the article's publication time, e.g. 2026-10-01T00:00:00Z. Each statement has its source, the article's headline and its topic. Pass next_cursor back as cursor for the next page (null means no more).

Inputs: limit, since, until, cursor, +8 more.

sentiment_seriesNews volume and sentiment over timeA
Read-onlyIdempotent

News volume and sentiment over time for exactly one of symbol, sector, theme_id or topic_id.

Each bucket: t (UTC start), count, bullish, bearish, neutral, sources (distinct outlets) and score = (bullish - bearish) / count. Buckets with no statements are omitted here. The last bucket is usually the current, still incomplete day or hour: do not read a low last bucket as a drop. interval=hour is for short ranges: pass since/until, and if the range is too long the error says the maximum.

Inputs: since, until, sector, symbol, +3 more.

storylinesOne symbol's storylinesA
Read-onlyIdempotent

One company's news grouped into continuing stories: an event, then its follow-ups, reactions and consequences. Use for "how did the X story unfold" or "what are the ongoing stories about X".

By default only storylines with two or more topics are listed: an empty list means "none with several topics", so pass min_topics=1 to see the single-topic ones. Each storyline has a name (one of its topics' names), first_seen and last_seen, its number of topics, statements and mentions (statements naming the symbol), distinct sources, sentiment counts of the mentions, top_topics (its largest topics; that is all of them when topics is no larger than the list) and related: storylines of other symbols that share topics with it. Storylines belong to one symbol, so news about two companies appears under each. The grouping is automatic and can be wrong or incomplete, and one real story can be split over several storylines: a reading aid, not a count of events. Call get_storyline when you need every topic in order or the statements.

Inputs: symbol (required), sort, limit, cursor, +1 more.

themesThemesA
Read-onlyIdempotent

The standing subjects the news is grouped into, each with its number of developments and statements, 24-hour volume, distinct sources and sentiment counts. With symbol or sector: only the themes that have statements about it; the counts are still those of the whole theme, so use search_statements with theme_id and symbol for the symbol's own statements. Use the returned id as theme_id in the other tools.

Inputs: sort, sector, symbol.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation4/5

    The set follows a clear list/detail and entity/aggregate split (find_topics vs get_topic, storylines vs get_storyline), and descriptions carefully delineate overlapping cases like trending vs find_topics(sort=velocity). The remaining ambiguity is in the three-tier conceptual hierarchy (themes vs topics vs storylines) and the get_symbol vs find_symbol pair, where naming alone doesn't signal 'profile' vs 'code lookup'.

    Naming Consistency3/5

    All snake_case and readable, but conventions are mixed: verb_noun forms (search_statements, get_symbol, find_symbol, get_topic, get_storyline) coexist with bare nouns (screen, trending, themes, storylines, reference). The find_/get_ prefix on the same resource (find_symbol vs get_symbol) is the least predictable part.

    Tool Count5/5

    12 tools is well within the ideal range, and each earns its place: discovery, search, per-entity profile, three aggregation views, and a topic/storyline navigation pair with detail counterparts. No redundant or filler tools are visible.

    Completeness4/5

    The surface covers the full read lifecycle for a news-analytics domain: reference/discovery, search with pagination and cursors, entity profiles, screening, time-series sentiment, themes, topics and storylines, all with detail drill-downs. Gaps are minor — no way to retrieve a full article/original statement body, and no cross-entity comparison tool beyond screen.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables querying scored and classified Russian and English news via MCP clients, offering filtered feeds, keyword search, breaking news, and coverage stats.
      5
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to discover supported news topics, read source-linked articles, and retrieve changes from a saved cursor. It exposes standard Streamable HTTP MCP tools alongside the news API endpoints for fresh news ingestion and reliable updates.
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to access aggregated multi-platform trending topics and RSS feeds, filter news by keywords, and perform natural-language analysis, sentiment insights, and trend prediction.
      GPL 3.0