Trend Pulse MCP Server
trend-pulse
PyPI
v2.0.0
Published by claude-world — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Global open-source Agentic Trend Intelligence Platform — 35+ sources, plugin system, vector search, trend clustering, lifecycle prediction, 6-agent content factory, web dashboard, and 23-tool MCP server.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Hardcoded Google API key in server code MTC-SRC-008 | exfiltration |
2. Client adoption risk — 99 − 7 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
critical Completed toxic-flow trifecta across toolsMTC-FLOW-002
This server (without client built-ins) exposes a complete data-exfiltration chain: take_snapshot → export_data → send_notification. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.
Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.
Location: flow take_snapshot → export_data → send_notification
low Hardcoded Google API key in server code (src/trend_pulse/plugins/sources/youtube_trending.py)MTC-SRC-008
A hardcoded Google API key (a client API key (restricted by referrer/quota, not a private secret)) appears in `src/trend_pulse/plugins/sources/youtube_trending.py:29`. Verify whether this is a real credential; if so, remove and rotate it.
Evidence: Google API key: AIza…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server src/trend_pulse/plugins/sources/youtube_trending.py
Tools 29
Each tool and what it can reach — statically extracted from the published source.
export_datareads sensitive datasend_notificationnetwork egresstake_snapshotingests untrusted inputadapt_contentno sensitive capabilityanalyze_viral_factorsno sensitive capabilitybatch_score_contentno sensitive capabilitycompare_trendsno sensitive capabilitygenerate_hashtagsno sensitive capabilityget_ab_variantsno sensitive capabilityget_campaign_calendarno sensitive capability
Show 19 more tools ↓
get_content_briefno sensitive capabilityget_lifecycle_predictionno sensitive capabilityget_platform_specsno sensitive capabilityget_reel_guideno sensitive capabilityget_review_checklistno sensitive capabilityget_scoring_guideno sensitive capabilityget_source_statusno sensitive capabilityget_trend_clustersno sensitive capabilityget_trend_historyno sensitive capabilityget_trend_reportno sensitive capabilityget_trend_velocityno sensitive capabilityget_trendingno sensitive capabilitylist_sourcesno sensitive capabilitylist_sources_extendedno sensitive capabilityrender_pageno sensitive capabilityrun_content_workflowno sensitive capabilityscore_content_hybridno sensitive capabilitysearch_semanticno sensitive capabilitysearch_trendsno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (29 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.0.0 latest |
A 92/100 | 2 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan trend-pulse --online --registry pypiMore in Data Science & ML
MCP server for 2s.io — 575+ pay-per-call tools for AI agents — ground-truth data, AI gateway, and agent infra (storage, locks, queues, watchers). x402 USDC on Base/Solana, no API keys, upto usage billing, free trials.
ArXiv preprints + Google Scholar papers, with citation counts in one query.
Add MCP servers to your favorite coding agents with a single command.
Help agents automatically write and test stories for your UI components
Model Context Protocol server for AI-Archive platform - enables AI agents to discover, submit, and review research papers
MCP server for Semantic Scholar research workflows with stdio and Streamable HTTP transports.