Google News & Trends MCP
PYPI · MCP-TRENDPULSE
Query Google News RSS feeds and search interest over time via Google Trends.
Available components
Last scanned (3 hours ago)
Scores higher than 97% of PyPI servers
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 6 of 68 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to AKzar1el/mcp-trendpulse). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2507 tokens (~156/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +59
- Malware scan: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Schema quality: 138 → 156 ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: excellent → good functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Schema quality: 138 → 156 ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: excellent → good functional
- Package version: 0.2.43 → 0.2.46 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/mcp-trendpulse@0.2.46
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | AKzar1el/mcp-trendpulse |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/AKzar1el/mcp-trendpulse/.github/workflows/publish.yml@refs/tags/v0.2.46 |
| Rekor log index | 3486013041 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:75ff399fc4a282e419bd6b330063f744d09a9dd3fac9dd2c6fd6d068559cf122 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 68 packages
| Packages resolved | 68 |
|---|---|
| Stale | 5 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_article_content ~122
Download and parse one specific news article when you already have an article URL. Use it to retrieve article text or metadata or summarize that URL; do not use it for discovery - use the news search tools instead.
| Name | Type | Req | Description |
|---|---|---|---|
| full_data | boolean | – | Return full data for the article. If False a summary should be created by setting the summarize flag |
| summarize | boolean | – | Generate a summary of the article, will first try LLM Sampling but if unavailable will use nlp |
| url | string | yes | The URL of the news article to download and parse. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_categories ~96
Return a bounded page of Google Trends category IDs and names for use in the cat parameter of trend tools. Use query to find categories by name and offset/limit to page through broader results; do not guess category IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum categories to return in this page. |
| offset | integer | – | Zero-based offset into the filtered category list. |
| query | – | – | Optional case-insensitive substring to match against category names. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_growth ~112
Estimate momentum for one or more known keywords across requested growth windows. Use this when percentage growth is the goal; use get_trends when the user needs the underlying historical time series.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Geographic region code (e.g. 'US'). |
| keyword | – | yes | Search keyword(s) to analyze; comparison lists support 1-5 keywords. |
| percent_growth | – | – | Timeframes to calculate growth (e.g. ['3M', '1Y']). |
| source | string | – | Search source. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_interest_by_region ~157
Return geographic Google Trends interest for one or more known keywords at country, region, city, or DMA resolution. Use this to compare where demand is strongest; use get_trends for interest over time instead.
| Name | Type | Req | Description |
|---|---|---|---|
| cat | integer | – | Category ID (default: 0 for all). |
| geo | string | – | Geographic region code (e.g. 'US' or empty '' for worldwide). |
| gprop | string | – | Google property filter. |
| inc_low_vol | boolean | – | Include regions with low search volume. |
| keywords | – | yes | Search keyword(s) to analyze. |
| resolution | string | – | Geographic resolution. |
| timeframe | string | – | Timeframe for search volume analysis (e.g., 'today 12-m'). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_news_by_keyword ~201
Find recent Google News articles for a free-form keyword or phrase. Use this for ad-hoc subject searches; use get_news_by_topic for a predefined topic category or get_news_by_site for one publisher.
| Name | Type | Req | Description |
|---|---|---|---|
| full_data | boolean | – | Return full data for each article. If False a summary should be created by setting the summarize flag |
| headlines_only | boolean | – | Return only dated Google News RSS title, publisher, and link metadata. No original publisher URL, full article text, or summary is fetched or inferred. The url field is a Google News RSS link; meta_d… |
| keyword | string | yes | Search term to find articles. |
| max_results | integer | – | Maximum number of results to return. |
| period | integer | – | Number of days to look back for articles. |
| summarize | boolean | – | Generate a summary of the article, will first try LLM Sampling but if unavailable will use nlp |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_news_by_location ~189
Find recent Google News articles about a place-focused location such as a city, state, or country. Use this when geography is the primary filter; use get_news_by_keyword for general subject searches.
| Name | Type | Req | Description |
|---|---|---|---|
| full_data | boolean | – | Return full data for each article. If False a summary should be created by setting the summarize flag |
| headlines_only | boolean | – | Return dated Google News RSS location headlines and publisher/link metadata only. No article body, original publisher URL, or summary is fetched or inferred. meta_data marks the limited RSS evidence… |
| location | string | yes | Name of city/state/country. |
| max_results | integer | – | Maximum number of results to return. |
| period | integer | – | Number of days to look back for articles. |
| summarize | boolean | – | Generate a summary of the article, will first try LLM Sampling but if unavailable will use nlp |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_news_by_site ~189
Find recent Google News articles from one publisher domain. Use this when the user wants source-specific coverage; use get_news_by_keyword for cross-publisher subject search.
| Name | Type | Req | Description |
|---|---|---|---|
| full_data | boolean | – | Return full data for each article. If False a summary should be created by setting the summarize flag |
| headlines_only | boolean | – | Return dated Google News RSS publisher-site headlines and publisher/link metadata only. No article body, original publisher URL, or summary is fetched or inferred. meta_data marks the limited RSS evi… |
| max_results | integer | – | Maximum number of results to return. |
| period | integer | – | Number of days to look back for articles. |
| site | string | yes | Domain of the news site, e.g. 'cnn.com'. |
| summarize | boolean | – | Generate a summary of the article, will first try LLM Sampling but if unavailable will use nlp |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_news_by_topic ~189
Find recent Google News articles from a predefined Google News topic category. Use this for topic category browsing such as BUSINESS, TECHNOLOGY, or SPORTS; use get_news_by_keyword for a free-form query.
| Name | Type | Req | Description |
|---|---|---|---|
| full_data | boolean | – | Return full data for each article. If False a summary should be created by setting the summarize flag |
| headlines_only | boolean | – | Return dated Google News RSS topic headlines and publisher/link metadata only. No article body, original publisher URL, or summary is fetched or inferred. meta_data identifies the limited RSS evidenc… |
| max_results | integer | – | Maximum number of results to return. |
| period | integer | – | Number of days to look back for articles. |
| summarize | boolean | – | Generate a summary of the article, will first try LLM Sampling but if unavailable will use nlp |
| topic | string | yes | Topic to search for articles. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_ranked_trends ~99
Return currently trending keywords ranked by week-over-week growth or volume. Use this when explicit ranked order matters; use get_top_trends for a simpler current feed and get_trends for historical series.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Geographic region code (e.g. 'US'). |
| limit | integer | – | Maximum number of trends to return. |
| sort | string | – | Field to sort by. |
| source | string | – | Search source. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_related_queries ~119
Return top and rising literal search queries related to one seed keyword. Use this for query expansion; use get_related_topics for topic entities or get_suggestions for autocomplete candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| cat | integer | – | Category ID (default: 0 for all). |
| geo | string | – | Geographic region code (e.g. 'US'). |
| gprop | string | – | Google property filter. |
| keyword | string | yes | Search keyword to analyze. |
| timeframe | string | – | Timeframe for search volume analysis (e.g., 'today 12-m'). |
Structured output declared, but exposes no named fields.
No examples provided.
get_related_topics ~116
Return top and rising Google Trends topic entities related to one seed keyword. Use this for entity or topic expansion; use get_related_queries for literal search queries.
| Name | Type | Req | Description |
|---|---|---|---|
| cat | integer | – | Category ID (default: 0 for all). |
| geo | string | – | Geographic region code (e.g. 'US'). |
| gprop | string | – | Google property filter. |
| keyword | string | yes | Search keyword to analyze. |
| timeframe | string | – | Timeframe for search volume analysis (e.g., 'today 12-m'). |
Structured output declared, but exposes no named fields.
No examples provided.
get_suggestions ~65
Return Google Trends autocomplete suggestions for a seed keyword. Use this for lightweight autocomplete or entity candidates; use get_related_queries when you need top or rising demand signals.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Query string to autocomplete. |
| language | – | – | Language code, e.g. 'en'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_top_news ~182
Return general headline and top-news stories from Google News without a keyword or topic seed. Use this for a broad news snapshot; use the keyword, location, topic, or site tools when the user gives a filter.
| Name | Type | Req | Description |
|---|---|---|---|
| full_data | boolean | – | Return full data for each article. If False a summary should be created by setting the summarize flag |
| headlines_only | boolean | – | Return dated Google News RSS top-story headline, publisher and link metadata only. No article body, original publisher URL, or summary is fetched or inferred. meta_data identifies the limited RSS evi… |
| max_results | integer | – | Maximum number of results to return. |
| period | integer | – | Number of days to look back for top articles. |
| summarize | boolean | – | Generate a summary of the article, will first try LLM Sampling but if unavailable will use nlp |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_top_trends ~92
Return a bounded current topic discovery feed from Google Trends RSS, including related news where available. Use this for current top or daily trends; use get_ranked_trends when explicit ranking by growth or volume matters.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Geographic region code (e.g. 'US'). |
| limit | integer | – | Maximum number of trends to return. |
| type | string | – | Type of trends feed. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_trending_terms ~199
Return terms that are trending now for a geography, optionally with related news metadata. Use this for current trend discovery; use get_trends when the user wants historical interest over time for known keywords.
| Name | Type | Req | Description |
|---|---|---|---|
| full_data | boolean | – | Return full data for each trend including related news stories. |
| geo | string | – | Geographic target for trending terms. Supports four levels of granularity: - Worldwide: empty string '' - Country: ISO 3166-1 alpha-2 code, e.g. 'US', 'GB', 'CA' - Subdivision (state/province/region)… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_trends ~187
Return historical Google Trends interest-over-time points for one or more known keywords. Use this for trajectory and comparisons across a timeframe; values are normalized 0-100 interest scores, not absolute search volume. Use get_trending_terms for what is trending now.
| Name | Type | Req | Description |
|---|---|---|---|
| cat | integer | – | Google Trends category ID; use 0 for all categories or a value from get_categories. |
| data_mode | string | – | Legacy resolution hint used only when timeframe is omitted. |
| geo | string | – | Geographic region code (e.g. 'US'). |
| keyword | – | yes | Search keyword(s) to analyze; comparison lists support 1-5 keywords. |
| source | string | – | Search source. |
| timeframe | – | – | Explicit TrendsPy range, for example 'today 12-m', 'today 90-d', 'all', or 'YYYY-MM-DD YYYY-MM-DD'. Overrides data_mode when supplied. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the Google News & Trends MCP server?
Google News & Trends MCP runs locally as a PyPI package, launched with uvx mcp-trendpulse. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-trendpulse
claude mcp add akzar1el-mcp-trendpulse -- uvx mcp-trendpulse
What is the Google News & Trends MCP server?
Google News & Trends MCP is listed in the public MCP registry as io.github.AKzar1el/mcp-trendpulse. Query Google News RSS feeds and search interest over time via Google Trends. This page covers its PyPI package (mcp-trendpulse).
Is the Google News & Trends MCP server safe to use?
Google News & Trends MCP scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Google News & Trends MCP server expose?
Google News & Trends MCP exposes 16 tools: get_news_by_keyword, get_news_by_location, get_news_by_topic, get_top_news, get_trending_terms, and 11 more. Their descriptions and schemas cost roughly 2,314 tokens of context every time the server is loaded.
Is the Google News & Trends MCP server still maintained?
Google News & Trends MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Google News & Trends MCP server under?
Google News & Trends MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.