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.

Trendzeist – Google Trends for content ideation

PYPI · TRENDZEIST-MCP · SCANNED SEP 28

Free Google Trends MCP: ranked breakout/rising/evergreen topics for content ideas. No API key.

Available components

+31 this week 88 Trust /100
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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 2 of 40 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to phalkmin/trendzeist-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 11 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 826 tokens (~91/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Trendzeist – Google Trends for content ideation MCP server?

Trendzeist – Google Trends for content ideation runs locally as a PyPI package, launched with uvx trendzeist-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · trendzeist-mcp

# add to Claude Code
claude mcp add phalkmin-trendzeist-mcp -- uvx trendzeist-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "phalkmin-trendzeist-mcp": {
      "command": "uvx",
      "args": [
        "trendzeist-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "phalkmin-trendzeist-mcp": {
      "command": "uvx",
      "args": [
        "trendzeist-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add phalkmin-trendzeist-mcp -- uvx trendzeist-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "phalkmin-trendzeist-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "trendzeist-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add phalkmin-trendzeist-mcp --command uvx --arg trendzeist-mcp
# ~/.hermes/config.yaml
mcp_servers:
  phalkmin-trendzeist-mcp:
    command: "uvx"
    args: ["trendzeist-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "phalkmin-trendzeist-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "trendzeist-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add phalkmin-trendzeist-mcp -t stdio -c uvx -a trendzeist-mcp
// mcp.json
{
  "mcpServers": {
    "phalkmin-trendzeist-mcp": {
      "command": "uvx",
      "args": [
        "trendzeist-mcp"
      ]
    }
  }
}
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.

  • 28 Sept 26 +10
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

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

  • 25 Sept 26 +18
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −14
    • Malware scan: pass → unverified ▼ security
  • 22 Sept 26 +16
    • Malware scan: unverified → pass ▲ security
  • 21 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Sept 26 +16
    • Malware scan: unverified → pass ▲ security
  • 18 Sept 26 +1

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

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 28 Sept 2026 · Analysed pypi/trendzeist-mcp@0.2.1

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 phalkmin/trendzeist-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/phalkmin/trendzeist-mcp/.github/workflows/publish.yml@refs/tags/v0.2.1
Rekor log index 2772593462
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:6d59b75333a192df853f0acd5fbee85bf55eb9693a077558f8aeddf628d28591

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 40 packages
Packages resolved 40
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~712 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
compare_keywords ~74

Compare 2-5 keywords head-to-head: relative share, leader and trend direction for each. Use to pick the strongest angle among alternatives.

NameTypeReqDescription
categoryinteger––
geostring––
gpropstring––
keywordsarrayyes–
timeframestring––

Structured output declared, but exposes no named fields.

No examples provided.

discover_topics ~113

One-shot topic discovery for blog ideation. For 1-5 seed keywords, pulls trend direction plus rising/top related queries, de-duplicates and ranks candidates as breakout > rising > evergreen. Partial failures are reported per seed in `errors` instead of failing the call.

NameTypeReqDescription
categoryinteger––
geostring––
gpropstring––
max_per_seedinteger––
seed_keywordsarrayyes–
timeframestring––

Structured output declared, but exposes no named fields.

No examples provided.

interest_by_region ~90

Where a keyword is searched most. resolution: COUNTRY (worldwide), REGION (states/provinces within geo), CITY, DMA (US metro areas).

NameTypeReqDescription
categoryinteger––
geostring––
gpropstring––
keywordsarrayyes–
limitinteger––
resolutionstring––
timeframestring––

Structured output declared, but exposes no named fields.

No examples provided.

interest_over_time ~114

Search-interest time series (0-100) for 1-5 keywords, with per-keyword summary (mean, latest, peak, direction: rising/stable/falling). Long series are downsampled to ~60 points. gprop: '' (web), 'news', 'youtube', 'images', 'froogle'.

NameTypeReqDescription
categoryinteger––
geostring––
gpropstring––
keywordsarrayyes–
timeframestring––

Structured output declared, but exposes no named fields.

No examples provided.

list_categories ~58

Browse/search Google Trends category ids (e.g. 'coffee' -> Food & Drink > Coffee & Tea). Pass the id as `category` to other tools to narrow results.

NameTypeReqDescription
limitinteger––
searchstring––

Structured output declared, but exposes no named fields.

No examples provided.

related_queries ~85

Top and rising search queries related to a keyword. 'rising' includes % growth and is_breakout (>5000%); best single source of fresh blog angles.

NameTypeReqDescription
categoryinteger––
geostring––
gpropstring––
keywordstringyes–
limitinteger––
timeframestring––

Structured output declared, but exposes no named fields.

No examples provided.

related_topics ~79

Top and rising Knowledge-Graph topics related to a keyword. Google often returns nothing here; if available=false fall back to related_queries.

NameTypeReqDescription
categoryinteger––
geostring––
gpropstring––
keywordstringyes–
limitinteger––
timeframestring––

Structured output declared, but exposes no named fields.

No examples provided.

suggest_keywords ~43

Google's entity suggestions for a keyword (title, type, mid). Use to disambiguate ambiguous terms or find the canonical topic id.

NameTypeReqDescription
keywordstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

trending_now ~56

Real-time trending searches (last ~24h) for a country or US state, with approximate traffic and linked news headlines. Good for newsjacking.

NameTypeReqDescription
geostring––
max_articlesinteger––

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Trendzeist – Google Trends for content ideation MCP server?

Trendzeist – Google Trends for content ideation is an MCP server listed in the public MCP registry as io.github.phalkmin/trendzeist-mcp. Free Google Trends MCP: ranked breakout/rising/evergreen topics for content ideas. No API key. This page covers its PyPI package (trendzeist-mcp).

Is the Trendzeist – Google Trends for content ideation MCP server safe to use?

Trendzeist – Google Trends for content ideation scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 28 September 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 Trendzeist – Google Trends for content ideation MCP server expose?

Trendzeist – Google Trends for content ideation exposes 9 tools: interest_over_time, compare_keywords, related_queries, related_topics, interest_by_region, and 4 more. Their descriptions and schemas cost roughly 712 tokens of context every time the server is loaded.

Is the Trendzeist – Google Trends for content ideation MCP server still maintained?

Trendzeist – Google Trends for content ideation is still listed as active in the MCP registry. We last reached this channel on 28 September 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 Trendzeist – Google Trends for content ideation MCP server under?

Trendzeist – Google Trends for content ideation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.