Skip to content

Mixpanel MCP by usefulapi

io.usefulapi/mixpanelusefulapi.iostreamable-httpv1.40.4Scanned

Query Mixpanel events, funnels, retention, segmentation and insights (JQL).

7 tools: 2 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 2 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Mixpanel MCP by usefulapi can do

The Mixpanel MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: mixpanel_retention and mixpanel_jql), but cannot delete data. 5 tools only read.

1 tool brings in text other people can write (mixpanel_query_insights).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Last scanned Oct 25, 2026, version 1.40.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 2Claude Code: ask
  • mixpanel_jqlRun a custom JQL (JavaScript Query Language) script for arbitrary analysis.1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The input takes a statement or command to run (input.script), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "mixpanel_jql" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a custom JQL (JavaScript Query Language) script for arbitrary analysis. Power-user escape hatch. Script must define main(). Query API: POST /jql. (Upstream maintenance mode; 2-min timeout, 5GB/query limit.)

    Annotations the server declares

    • title: Run a JQL query
    • readOnlyHint: true
  • mixpanel_retentionCohort retention: of users who did `born_event`, how many came back and did `event` over subsequent intervals.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Cohort retention: of users who did `born_event`, how many came back and did `event` over subsequent intervals. Query API: GET /retention.

    Annotations the server declares

    • title: Retention report
    • readOnlyHint: true
Only reads 5Show 5 read-only tools
  • mixpanel_list_funnelsGet the funnel_id and name of every saved funnel in the project.No findings

    Why it is in this group

    • The name "mixpanel_list_funnels" says "list": a word for reading.
    Description, as the server wrote it
    Get the funnel_id and name of every saved funnel in the project. Query API: GET /funnels/list.

    Annotations the server declares

    • title: List saved funnels
    • readOnlyHint: true
  • mixpanel_query_funnelGet conversion data for a saved funnel (use mixpanel_list_funnels to find funnel_id).No findings

    Why it is in this group

    • The name "mixpanel_query_funnel" says "query": a word for reading.
    Description, as the server wrote it
    Get conversion data for a saved funnel (use mixpanel_list_funnels to find funnel_id). Query API: GET /funnels.

    Annotations the server declares

    • title: Query a saved funnel
    • readOnlyHint: true
  • mixpanel_query_insightsFetch the computed data behind a saved Insights report by bookmark_id (the report id in the board URL).Reads text others writeNo findings

    Why it is in this group

    • The name "mixpanel_query_insights" says "query": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Fetch the computed data behind a saved Insights report by bookmark_id (the report id in the board URL). Mixpanel's recommended, non-deprecated path for programmatic reporting. Query API: GET /insights.

    Annotations the server declares

    • title: Query a saved Insights report
    • readOnlyHint: true
  • mixpanel_segmentationCount/segment/filter a single event over a date range.No findings

    Why it is in this group

    • The description's first verb is "count": a word for reading.
    Description, as the server wrote it
    Count/segment/filter a single event over a date range. e.g. 'Signed up' by country last week. Params `on`/`where` use Mixpanel segmentation expressions like properties["$country_code"]. Query API: GET /segmentation. (Upstream maintenance mode — for saved reports prefer mixpanel_query_insights.)

    Annotations the server declares

    • title: Segment an event
    • readOnlyHint: true
  • mixpanel_top_eventsList today's top events with counts and % change vs yesterday.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List today's top events with counts and % change vs yesterday. Good first call to discover what events a project tracks. Query API: GET /events/top.

    Annotations the server declares

    • title: Top events (today)
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mixpanel.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://mixpanel.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "mixpanel_jql" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://mixpanel.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://mixpanel.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http mixpanel https://mixpanel.usefulapi.io/mcp
claude mcp add --transport http mixpanel https://mixpanel.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mixpanel__mixpanel_top_events",
      "mcp__mixpanel__mixpanel_segmentation",
      "mcp__mixpanel__mixpanel_list_funnels",
      "mcp__mixpanel__mixpanel_query_funnel",
      "mcp__mixpanel__mixpanel_query_insights"
    ],
    "ask": [
      "mcp__mixpanel__mixpanel_retention",
      "mcp__mixpanel__mixpanel_jql"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mixpanel. Review it before you use it.

Capability tags behind 1 rule
  • mcp__mixpanel__mixpanel_query_insights untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/mixpanel/verify?hash=0b0eb4c4b1d7c73d2961a841082e4ef9032bef9e1878499f7f294c013f6d4385" | jq -e '.changed == false'

Pinned hash 0b0eb4c4b1d7, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/mixpanel/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/mixpanel
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/mixpanel.svg)](https://radar.anlyon.com/servers/io.usefulapi/mixpanel)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Mixpanel MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Mixpanel MCP by usefulapi safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Mixpanel MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Mixpanel MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Mixpanel MCP by usefulapi have?

7 tools: 2 write, 5 read. mixpanel_retention, mixpanel_jql, mixpanel_top_events, mixpanel_segmentation, mixpanel_list_funnels, mixpanel_query_funnel and mixpanel_query_insights.

Does the Mixpanel MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Mixpanel MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Mixpanel MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.