Audiense Insights vs Nevent MCP
Audiense Insights is an MCP server published by AudienseCo. Marketplaces we read that list it: 1 (Docker MCP Catalog). Nevent MCP is an MCP server published by nevent-dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Audiense Insights |  Nevent MCP |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:064623a07a6b Forks (GitHub): 11 Pulls (Docker Hub): 41 231 Stars (Docker Hub): 0 Stars (GitHub): 19 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.8.0 Downloads/month (npm): 456 Downloads/week (npm): 80 Forks (GitHub): 1 Stars (GitHub): 1 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 | Nevent MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 19 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 41 231 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/audiense-insights) | Remote server (mcp.nevent.ai) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/audienseco/mcp-audiense-insights | github.com/nevent-dev/mcp-nevent |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
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.
Nevent MCP
Talk to your live-events CRM (campaigns, analytics, paid ads, segments) in Claude and ChatGPT.
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-insightsRequires: AUDIENSE_CLIENT_SECRET (secret), TWITTER_BEARER_TOKEN (secret)
Nevent MCP As a remote MCP server
claude mcp add --transport http mcp-nevent https://mcp.nevent.ai/Requires: NEVENT_JWT_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Nevent MCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Nevent MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only Audiense Insights asks for
AUDIENSE_CLIENT_IDAUDIENSE_CLIENT_SECRET (secret)TWITTER_BEARER_TOKEN (secret)
Only Nevent MCP asks for
NEVENT_JWT_TOKEN (secret)NEVENT_OPERATION_MODE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Audiense Insights · What it can do: Nevent MCP · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.