Audiense Insights vs cogni-trends
cogni-trends is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑28.
Audiense Insights is an MCP server published by AudienseCo. Marketplaces we read that list it: 1 (Docker MCP Catalog). cogni-trends is a plugin bundle for AI coding tools published by Stephan de Haas. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-28. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:064623a07a6b Forks (GitHub): 11 Pulls (Docker Hub): 41 574 Stars (Docker Hub): 0 Stars (GitHub): 19 Not marked · First seen |
Not listed |
| Community marketplace cogni-work/insight-wave | Not listed | Removed on 2026-10-28 Version: 0.6.37 Forks (GitHub): 2 Stars (GitHub): 13 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Audiense Insights | cogni-trendsno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 19 | 13 |
| Pulls (Docker Hub) (differs) | 41 574 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/audiense-insights) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Parts of the bundle (differs) | Not a bundle | 21 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/audienseco/mcp-audiense-insights | github.com/cogni-work/insight-wave |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of cogni-trends
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Trend, stats & insight search across PSFK expert graphs with citable sources.
-
Evidence-backed AI content studio with 21 stable trend intelligence tools.
-
Use this agent when you need to identify market opportunities, analyze trending topics, research ...
-
Trending topics, trajectories, audience insights and recommendations from TrendsAGI. Read-only.
-
Topics gaining momentum before they peak. Trend volume and growth signals. Free key at trendsmcp.ai
-
Trendzeist – Google Trends for content ideation
Free Google Trends MCP: ranked breakout/rising/evergreen topics for content ideas. No API key.
What each says it does
Audiense Insights
Audiense Insights MCP Server is a server based on the Model Context Protocol (MCP) that allows Claude and other MCP-compatible clients to interact with your Audiense Insights account.
cogni-trends
Strategic trend scouting and TIPS reporting pipeline. Combines the Smarter Service Trendradar (4 dimensions) with TIPS (Trends, Implications, Possibilities, Solutions): trend-scout → value-modeler → trend-research → trend-synthesis and/or trend-booklet → verify-trend-report. Evidence-backed CxO reports and reusable industry catalogs across DE/FR/IT/PL/NL/ES + US/UK.
How to run each
Audiense Insights As a local MCP server: Docker image
claude mcp add --env "AUDIENSE_CLIENT_SECRET=<YOUR_AUDIENSE_CLIENT_SECRET>" --env "TWITTER_BEARER_TOKEN=<YOUR_TWITTER_BEARER_TOKEN>" --transport stdio audiense-insights -- docker run -i --rm -e AUDIENSE_CLIENT_SECRET -e TWITTER_BEARER_TOKEN mcp/audiense-insights
Requires: AUDIENSE_CLIENT_SECRET (secret), TWITTER_BEARER_TOKEN (secret)
cogni-trends
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of cogni-trends publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of cogni-trends publish no settings it asks for, so we do not compare settings.
What it can do: Audiense Insights · What it can do: cogni-trends · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.