IR and comms teams can pair news volume, sentiment, and search demand in the same AI workspace where talking points are drafted, with exports that audit teams can replay.
Investor relations is not hunting viral spikes for entertainment. The job is to see whether public attention, media tone, and retail curiosity are aligned with the story management wants to tell. Trends MCP gives IR and comms staff the same three operations analysts use elsewhere: Get Trends for a full series, Get Growth for windows such as YTD and 12M, and Get Top Trends when the team needs the current Google News cluster board or X trending snapshot.
Splitting sentiment and mention volume across two dashboards makes it easy to miss divergence, for example rising volume with flat sentiment right after a lawsuit headline. Pulling both inside an MCP aware assistant keeps the evidence in one transcript the disclosure committee can read. The source strings are literal: news sentiment and news volume, which reduces ambiguity when counsel asks what a chart measures.
google search is still where millions of people phrase confusion in their own words. When IR drafts answers for "Why is gross margin down?" it helps to know whether those exact phrases are spiking relative to the prior quarter. That is a demand signal, not a verdict on truth. Pair it with news volume so the team sees whether journalists are moving in the same direction as the crowd.
Assign an owner for keyword hygiene. Ticker symbols alone often miss retail phrasing, while full legal names pick up noise from unrelated homonyms. Document the chosen keyword list in the same place as press release approvals. When an external agency rotates, they inherit the list instead of inventing a new one.
POST https://api.trendsmcp.ai/api accepts the same shapes described in https://www.trendsmcp.ai/llms.txt. Bearer auth is required. For assistants, the HTTP MCP endpoint is https://api.trendsmcp.ai/mcp with the Authorization header set to the workspace key. Security reviewers usually prefer that pattern over ad hoc scraping because the contract is small and the error codes are enumerated.
Earnings adjacent research lives at https://www.trendsmcp.ai/earnings-research-alternative-data. Crisis adjacent monitoring is spelled out at https://www.trendsmcp.ai/pr-crisis-trend-monitoring. For analysts who sit next to IR, the broader investment framing is at https://www.trendsmcp.ai/investment-research. Raw field documentation for sentiment and volume sits at https://www.trendsmcp.ai/news-sentiment-data and https://www.trendsmcp.ai/news-volume-data.
Instruct the model with the shipped prefixes: "Using TrendsMCP, plot news sentiment for [issuer] over the last six months" and "Via TrendsMCP, compare news volume for [issuer] and [peer] for YTD." Those phrases appear in the product prompt appendix so routing stays predictable across Claude, Cursor, and ChatGPT connectors.
Normalized scores are comparable within a pipeline, not a substitute for GAAP figures. Growth percentages come from stated baselines on the response object; quote those dates in footnotes. When the API returns data_unavailable, pause the narrative rather than improvising. That restraint tends to impress risk teams more than an over smooth story.
The public overview still lists roughly one hundred requests per month on the free tier without a card, which is enough for a careful pilot on a single issuer if the team batches growth windows. Production monitoring across a dozen names belongs on a paid plan so monthly caps are predictable in the communications budget.
FAQ