Claude can call news sentiment and news volume through Trends MCP. That is coverage polarity and mention volume, not a licensed newswire and not last-sale.
News sentiment data in Claude is public coverage through Trends MCP, not a Bloomberg terminal and not Google News HTML. After the connector is live, get_growth source news sentiment measures polarity where the pipeline supports it. Source news volume measures mention volume. get_top_trends type Google News Top News is a snapshot board. Those are three objects. Collapse them and the memo cannot be audited.
Source page: news sentiment data. Host: Trends MCP for Claude. Investing sibling: trend data for investment research in Claude. Wikipedia pairing: Wikipedia trends in Claude.
claude.ai: OAuth at https://www.trendsmcp.ai/mcp. Desktop and Claude Code: Bearer at https://api.trendsmcp.ai/mcp. Key: account.
Say “using TrendsMCP.” A ticker-plus-news question that never names the server becomes a Yahoo Finance recap.
get_growth(keyword="AAPL", source="news sentiment", percent_growth=["7D", "30D"])
get_growth(keyword="AAPL", source="news volume", percent_growth=["7D", "30D"])
get_top_trends(type="Google News Top News", limit=25)
get_growth(keyword="AAPL", source="google search, news volume", percent_growth=["7D"])
news sentiment is not news volume. Neither is type Google News Top News. Sending a board type as source is invalid_source. REST get_time_series for weekly history. Several windows ride in one growth call per source. Two sources in a comma list are two requests.
Do not treat a sentiment percent as “the street is bullish.” Do not treat Hot Posts or Google News rank 1 as a position. Do not treat AAPL on news volume as last-sale.
Do not freeze this morning’s Google News titles in a Project. Cite as_of_ts.
Low-volume names print 100 percent on a 1-to-2 index. Quote recent_value and baseline_value. Empty: not_found or data_unavailable. Do not coerce those to zero. Zero looks like “no coverage measured.”
A proving set that fits the free plan: one news-volume growth call, one news-sentiment growth call, one Google News board. Three requests. Adding google search is a fourth. A desk that pages four boards every hour will 429.
Projects can store the two source strings, the board type, and a cap. Projects should not store today’s headlines.
Compliance stacks that only allow licensed vendors should skip scrape-shaped news MCPs and should not treat this index as a wire. Label it.
Free 100 requests per month. Starter $19 / 1,000. Pro $49 / 5,000. Business $199 / 25,000. Pricing. Connecting is free. Calling is not.
401: host mixup. Claude is a weak cron. Nightly coverage pulls belong on REST.
If the next message is a 10-Q, stop using Trends MCP for that turn. EDGAR or a crawl MCP owns filings. If the next message is a quote, a market-data MCP owns last-sale. This connector stays whether anyone is writing.
Cite the tool. A useful paragraph says source news sentiment with both index values, then separately source news volume with both index values, then type Google News Top News with as_of_ts. A weak paragraph says “coverage is negative.” The second sentence is how invented polarity lands in a memo that later looks like a wire.
google news as a keyword source is Google News search-style demand. It is not type Google News Top News. It is not news volume. Three more strings to keep apart. Split calls when they collide.
A proving set that fits the free plan can stop at two growth calls if the ticket did not need the board. Adding google search after the print is the attention question the investing page already covers. This URL stays sentiment and volume in Claude.
Projects can store legal source strings and the “not a quote” rule. Projects should not store this morning’s headlines. Those ranks turn over.
Low-volume names are the usual trap. Print both values. Empty not_found is not “zero coverage.” Fail closed. Licensed vendors remain a procurement question. Label this index in the note so later readers do not treat it as a wire.
Claude is a weak cron. Nightly sentiment pulls belong on REST. Connecting is free. Looping every ticker in a universe is how the free 100-request month dies before the open. Cap the Project: two names, two sources, then stop. Licensed wires remain a procurement question. Market-data MCPs remain last-sale. EDGAR remains filings. Google News Top News remains a board. news volume remains counts. news sentiment remains polarity where the pipeline supports it. Write the object. Nightly pulls belong on REST. Connecting is free. Calling is not. Fail closed on invented polarity and coerced zeros. google news as a keyword source is still not type Google News Top News and still not news volume. Three strings. Split the note. A sentiment swing on tiny volume is not a wire. Print both index values. Licensed vendors remain procurement. This index remains labeled third-party demand. Nightly pulls belong on REST. Two names and two sources then stop is a desk rule that survives the open. Extra tickers are extra requests.
Claude Projects should pin three strings, not one “news” label. Type Google News Top News is a board. Source news volume is coverage history. Source news sentiment is polarity where the pipeline supports it. Sending the board type into get_growth is invalid_source. Sending google news as a source can miss. Recheck news sentiment data if a close label fails.
A desk that needs polarity plus volume pays two growth calls per name. That is the honest cost. One call that “should include both” does not exist. Print both index values when volume is thin. A 50 percent sentiment move on a 3-to-4.5 baseline is noise until volume confirms it.
Licensed wires still win full-text. Market-data MCPs still win last-sale. EDGAR still wins filings. This connector still wins labeled third-party demand next to Google Search. Four objects in one paragraph without names is how a Claude note invents a Bloomberg terminal. Name the object. Fail closed on invented polarity.
Nightly universe pulls belong on REST. Claude is a weak cron. Connecting is free. Calling is not. The free plan is 100 requests per month. Two names, two sources, one board is five requests. That proving set is enough. Looping a watchlist is how the month dies before the open.
FAQ