Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mambabuilt/mcp-google-trends-scraper

NPM · @MAMBALABSDEV/MCP-GOOGLE-TRENDS-SCRAPER

Google Trends interest, regions, and related queries per term, with no Google login or key

+3 this week 75 Trust /100

Last scanned (15 hours ago)

Scores higher than 51% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • 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 Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 457 tokens (~457/item across 1 items; 1 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 Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +11
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
  • 11 Nov 26 −10
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.85 → unverified ▼ functional
    • Package version: 1.0.1 → 1.0.2 functional
  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1
    • Tool safety: pass → unverified ▼ security
    • Provenance: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.10 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.0.0 → 1.0.1 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/@mambalabsdev/mcp-google-trends-scraper@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~457 tokens

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 →

Tool Tokens
get_google_trends ~457

Read Google Trends for search terms: a summary per term (average, latest, and peak interest, recent change, top region, top and rising queries) plus flat rows for interest over time, by region, metro, or city, and related queries. Values are relative 0 to 100, not search counts. Compare up to 5 terms on one scale. No Google account or key.

NameTypeReqDescription
categorystring–Google Trends category number. 0 is all categories. The number is in the cat= part of a Trends URL.
compareboolean–true: terms are charted together in groups of 5, on one shared scale. false: each term gets its own chart. Each term is charged either way.
geostring–Empty for worldwide, or a Google geo code such as US, DE, or US-CA.
max_charge_usdstring–Optional. The run stops before a charge that would pass this amount. Summary rows are always returned.
outputsarray–Any of interest_over_time, interest_by_region, related_queries, related_topics. Default is the first three. See Limitations for related_topics.
propertystring–Which Google search to read: web, news, images, youtube, or shopping.
proxy_modestring–auto (default): requests go through the Apify proxy pool, and a request the pool cannot get through is retried on residential addresses. residential: every request uses residential addresses. A relia…
region_resolutionstring–auto: countries worldwide, regions inside a country. DMA is US metro areas. CITY needs a geo. COUNTRY needs an empty geo.
termsarray–Search terms, up to 200 per run. A Google topic ID such as /m/0j6n6s8 also works.
timeframestring–now 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m, today 12-m, today 5-y, all, or two dates as YYYY-MM-DD YYYY-MM-DD.

No output schema declared.

No examples provided.

Install

How do I install the com.mambabuilt/mcp-google-trends-scraper server?

com.mambabuilt/mcp-google-trends-scraper runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-google-trends-scraper. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @mambalabsdev/mcp-google-trends-scraper

# add to Claude Code
claude mcp add com-mambabuilt-mcp-google-trends-scraper -- npx -y @mambalabsdev/mcp-google-trends-scraper
Common questions

What is the com.mambabuilt/mcp-google-trends-scraper server?

com.mambabuilt/mcp-google-trends-scraper is listed in the public MCP registry as com.mambabuilt/mcp-google-trends-scraper. Google Trends interest, regions, and related queries per term, with no Google login or key. This page covers its npm package (@mambalabsdev/mcp-google-trends-scraper).

Is the com.mambabuilt/mcp-google-trends-scraper server safe to use?

com.mambabuilt/mcp-google-trends-scraper scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 com.mambabuilt/mcp-google-trends-scraper server expose?

com.mambabuilt/mcp-google-trends-scraper exposes 1 tool: get_google_trends. Their descriptions and schemas cost roughly 457 tokens of context every time the server is loaded.

Is the com.mambabuilt/mcp-google-trends-scraper server still maintained?

com.mambabuilt/mcp-google-trends-scraper is still listed as active in the MCP registry. We last reached this channel on 21 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 com.mambabuilt/mcp-google-trends-scraper server under?

com.mambabuilt/mcp-google-trends-scraper declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.mambabuilt/mcp-google-trends-scraper server?

VerifyMCP ran 16 checks on com.mambabuilt/mcp-google-trends-scraper, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.