Atlas / MCP servers / akzar1el / mcp-trendpulse

mcp-trendpulseCAUTION

mcp/akzar1el/mcp-trendpulse

Google News + Google Trends MCP server for keyword, market, SEO, and content research. Free OSS.

Verdict
CAUTION
Grade
B
Trust score
86 /100
Exposed tools
—
Transport
stdio · streamable-http
License
MIT
Stars
5
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://modelcontextprotocol.io) [](https://www.python.org/) [](LICENSE) [](https://glama.ai/mcp/servers/AKzar1el/mcp-trendpulse) [](https://mcpvault.io/servers/mcp-trendpulse/health?utmsource=externalbadge&utmmedium=referral&utmcampaign=mcphealthreport)

TrendPulse is a Python Model Context Protocol (MCP) server for researching current news and search-interest trends. It combines Google News discovery and article extraction with Google Trends analysis so MCP clients can inspect what is trending, compare keyword momentum, explore related demand, and add current-news context to research workflows.

The project currently ships as a community/self-hosted MCP server and also contains the implementation for a separate hosted TrendPulse by DigestSEO surface for remote MCP clients such as ChatGPT and Codex. The hosted layer uses a smaller, goal-oriented tool surface while the community server keeps the full low-level research toolkit available to developers.

Project status: the local/community server is usable today. The DigestSEO-hosted MCP and public OpenAI plugin are not released yet and should not be treated as available endpoints.

Engineering context: TrendPulse is part of the DigestSEO MCP ecosystem. It complements mcp-gsc for Google Search Console data, mcp-geo for AI visibility, and mcp-web-validator for technical web validation. The broader architecture is documented in the [DigestSEO MCP Suite engineering case study](https://

Read from source at commit e60fc7c9a619OBSERVED · 2026-10-11
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code (pypi)
claude mcp add mcp-trendpulse -- uvx mcp-trendpulse==0.2.37
03

Trust audit

CAUTIONgrade B · trust 86/100 Install with care. The audit found things worth knowing before you trust its output.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeWARN
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (1 observation(s))
Network
declared (2 observation(s))
Shell
none-observed
Dependencies
pinned
Secrets in source
found

Findings (9)

MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321
tests/test_observability.py:15
secret = "sensitive-keyword-that-must-not-be-logged"
MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321
tests/test_remote_asgi.py:120
secret = "do-not-log-this-keyword-or-token"
LOWNetwork egress · net.metadata_ip · CWE-200, CWE-319
tests/test_article_url_validation.py:108
"http://169.254.169.254/latest/meta-data",
Why it matters. cloud metadata endpoint: the classic SSRF credential grab
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
.github/workflows/container.yml:58
if curl --fail --silent http://127.0.0.1:18000/health >/dev/null; then
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
.github/workflows/container.yml:69
curl --fail --silent http://127.0.0.1:18000/health | grep '"status":"ok"'
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
.github/workflows/container.yml:70
curl --fail --silent http://127.0.0.1:18000/ready | grep '"status":"ready"'
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
.github/workflows/container.yml:71
curl --fail --silent http://127.0.0.1:18000/ready | grep '"auth":"disabled"'
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
.github/workflows/container.yml:103
http://127.0.0.1:18000/mcp \
LOWInventory / provenance · mcp.no_tools_extracted · CWE-1104
server.json
Why it matters. the tool list is enumerated at runtime by tools/list, not declared in source
Fix. the page says so rather than showing an empty table

Gates applied: no_behavioural_pass.

Audited 2026-10-11 · audit v0.4.1 · source sha e60fc7c9a619full audit observations/trust-audit/mcp-server/akzar1el__mcp-trendpulse.json · Report an issue / request a re-scan
04

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-11e60fc7c9a619CAUTIONB86first audit
05

Questions

What is the mcp-trendpulse MCP server?

Google News + Google Trends MCP server for keyword, market, SEO, and content research. Free OSS.

Is mcp-trendpulse safe to connect to an agent?

With care. The audit graded it B (86/100) and found 9 things worth knowing before you trust this server, listed below with the exact line each was found on.

What credentials does mcp-trendpulse need?

No credential environment variables were found in its source, so it appears to need none.

How does mcp-trendpulse run?

It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on PyPI as mcp-trendpulse.

How current is this page?

The grade is for one exact copy of the source (e60fc7c9a619), read on 2026-10-11. The repository is watched and re-audited when it changes.

Advertisement