com.mcparmory/mixpanel
PYPI · MCPARMORY-MIXPANEL · 2 COMPONENTS · SCANNED SEP 20
Analyze user behavior with funnels, retention, cohorts, and event segmentation
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3656 tokens (~192/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_jql_script" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/mixpanel MCP server?
com.mcparmory/mixpanel runs locally as a PyPI package, launched with uvx mcparmory-mixpanel. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-mixpanel
claude mcp add com-mcparmory-mixpanel -- uvx mcparmory-mixpanel
{
"mcpServers": {
"com-mcparmory-mixpanel": {
"command": "uvx",
"args": [
"mcparmory-mixpanel"
]
}
}
} {
"servers": {
"com-mcparmory-mixpanel": {
"command": "uvx",
"args": [
"mcparmory-mixpanel"
]
}
}
} codex mcp add com-mcparmory-mixpanel -- uvx mcparmory-mixpanel
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-mixpanel": {
"type": "local",
"command": [
"uvx",
"mcparmory-mixpanel"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-mixpanel --command uvx --arg mcparmory-mixpanel
mcp_servers:
com-mcparmory-mixpanel:
command: "uvx"
args: ["mcparmory-mixpanel"] {
"McpServers": {
"com-mcparmory-mixpanel": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-mixpanel"
]
}
}
} assistant mcp add com-mcparmory-mixpanel -t stdio -c uvx -a mcparmory-mixpanel
{
"mcpServers": {
"com-mcparmory-mixpanel": {
"command": "uvx",
"args": [
"mcparmory-mixpanel"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −2
- Stability: pass → 0.80 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.77 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcparmory-mixpanel@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
execute_jql_script Execute JQL Script ~155
Execute a custom JQL script against a Mixpanel project to query and aggregate event data. The script receives optional parameters and returns results based on the defined aggregation logic.
| Name | Type | Req | Description |
|---|---|---|---|
| params | string | – | A JSON object containing custom variables and configuration values made available to the script as the global params variable. Allows parameterization of script logic without modifying the script its… |
| project_id | integer | yes | The numeric identifier for the Mixpanel project where the script will execute. |
| script | string | yes | A JavaScript function that processes events using the Mixpanel JQL API. The function receives a params object and must return aggregated event data. Typically groups events by specified dimensions an… |
No output schema declared.
No examples provided.
get_activity_stream_for_users Get Activity Stream for Users ~146
Retrieve the activity feed for specified users within a date range. Subject to a rate limit of 60 queries per hour with a maximum of 5 concurrent queries.
| Name | Type | Req | Description |
|---|---|---|---|
| distinct_ids | string | yes | A JSON array (as a string) of distinct user IDs for which to return activity feeds. Each ID should be a valid distinct_id from your Mixpanel project. |
| from_date | string | yes | The start date for the activity query in YYYY-MM-DD format (inclusive). |
| project_id | integer | yes | The Mixpanel project ID that identifies which project to query. |
| to_date | string | yes | The end date for the activity query in YYYY-MM-DD format (inclusive). |
No output schema declared.
No examples provided.
get_event_aggregates Get Event Aggregates ~264
Retrieve aggregated event data (counts, unique users, or averages) for specified events over a time period. Results can be broken down by minute, hour, day, week, or month granularity.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | One or more event names to analyze, provided as a JSON array of strings (e.g., ["play song", "log in"]). |
| format | string | – | The response format: 'json' (default) or 'csv'. Subject to rate limits of 60 queries per hour and 5 concurrent queries. |
| from_date | string | yes | The start date for the query range in YYYY-MM-DD format (inclusive). |
| project_id | integer | yes | The Mixpanel project ID to query. |
| to_date | string | yes | The end date for the query range in YYYY-MM-DD format (inclusive). |
| type | string | yes | The type of aggregation to perform: 'general' for total event counts, 'unique' for distinct user counts, or 'average' for mean values per time unit. |
| unit | string | yes | The time granularity for bucketing results: 'minute', 'hour', 'day', 'week', or 'month'. Note that hourly granularity is not available for unique user counts. |
No output schema declared.
No examples provided.
get_event_average Get Event Average ~180
Calculate the average value of a numeric expression across events within a specified date range. Results are aggregated per unit time for trend analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | The name of the event to analyze. Provide a single event name, not multiple events. |
| from_date | string | yes | The start date for the query range in YYYY-MM-DD format (inclusive). |
| on | string | yes | A numeric expression to average per unit time. Non-numeric expression results are treated as 0.0. Refer to the expressions documentation for valid syntax. |
| project_id | integer | yes | The Mixpanel project ID to query. |
| to_date | string | yes | The end date for the query range in YYYY-MM-DD format (inclusive). |
| where | string | – | Optional filter expression to narrow events by specific criteria. Refer to the expressions documentation for valid syntax. |
No output schema declared.
No examples provided.
get_event_property_aggregates Get Event Property Aggregates ~314
Retrieve aggregated metrics for a specific event property over a time period, supporting analysis types like total counts, unique values, or averages at various time granularities (minute through month).
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | The name of the event to analyze. Provide a single event name, not multiple events. |
| format | string | – | The response format: 'json' (default) or 'csv'. |
| from_date | string | yes | The start date for the analysis period in YYYY-MM-DD format (inclusive). |
| limit | integer | – | Maximum number of property values to return in results. Defaults to 255 if not specified. |
| name | string | yes | The property name within the event whose values you want to aggregate. |
| project_id | integer | yes | The Mixpanel project ID to query. |
| to_date | string | yes | The end date for the analysis period in YYYY-MM-DD format (inclusive). |
| type | string | yes | The type of aggregation to perform: 'general' for total event counts, 'unique' for distinct value counts, or 'average' for mean values. |
| unit | string | yes | The time bucket granularity for results: 'minute', 'hour', 'day', 'week', or 'month'. Note that hourly granularity is not available for unique analysis. |
| values | array | – | Optional filter to analyze only specific property values. Provide as a JSON array of strings (e.g., ["value1", "value2"]). If omitted, all values are included. |
No output schema declared.
No examples provided.
get_event_segmentation_by_numeric_buckets Get Event Segmentation by Numeric Buckets ~178
Retrieve event data segmented into numeric buckets based on a numeric property value. Results are filtered by the specified date range and optional event properties.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | The name of the event to analyze. Specify a single event name, not multiple events. |
| from_date | string | yes | The start date for the query range in YYYY-MM-DD format (inclusive). |
| on | string | yes | A numeric property expression to segment the event data into buckets. The property must contain numeric values. |
| project_id | integer | yes | The Mixpanel project ID to query. |
| to_date | string | yes | The end date for the query range in YYYY-MM-DD format (inclusive). |
| where | string | – | An optional property expression to filter which events are included in the results. Only events matching this filter will be segmented. |
No output schema declared.
No examples provided.
get_event_sum_by_time Get Event Sum by Time ~191
Calculate the sum of a numeric expression for a specified event aggregated over time. Results are broken down by unit time periods within the requested date range.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | The name of the event to analyze. Provide a single event name, not multiple events. |
| from_date | string | yes | The start date for the query in YYYY-MM-DD format (inclusive). |
| on | string | yes | A numeric expression to sum for each time unit. Non-numeric expression results are treated as 0.0. Use Mixpanel expression syntax to reference event properties and perform calculations. |
| project_id | integer | yes | The Mixpanel project ID to query. |
| to_date | string | yes | The end date for the query in YYYY-MM-DD format (inclusive). |
| where | string | – | Optional filter expression to narrow results to specific events. Use Mixpanel expression syntax to define conditions on event properties. |
No output schema declared.
No examples provided.
get_funnel_data Get Funnel Data ~321
Retrieve funnel conversion data for a specified date range and funnel. Results can be segmented by user properties and filtered by event criteria. Subject to a rate limit of 60 queries per hour with a maximum of 5 concurrent queries.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | yes | The start date for the query in YYYY-MM-DD format (inclusive). |
| funnel_id | integer | yes | The ID of the funnel to retrieve data for. |
| length | integer | – | The time window for users to complete the funnel from when they trigger the first step. Maximum allowed is 90 days. If not specified, uses the value saved in the UI for this funnel. |
| length_unit | string | – | The unit of time for the length parameter: day, hour, minute, or second. If not specified, uses the value saved in the UI for this funnel. |
| limit | integer | – | The maximum number of top property values to return when segmenting. Defaults to 255 if not specified; maximum allowed is 10,000. This parameter has no effect if the 'on' parameter is not used. |
| on | string | – | A property expression to segment funnel results by. When specified, results are grouped by the values of this property. |
| project_id | integer | yes | The Mixpanel project ID that contains the funnel. |
| to_date | string | yes | The end date for the query in YYYY-MM-DD format (inclusive). |
| where | string | – | An expression to filter which events are included in the funnel analysis. Only events matching this filter are considered. |
No output schema declared.
No examples provided.
get_insights_report Get Insights Report ~93
Retrieve data from a saved Insights report in your Mixpanel project. Subject to a rate limit of 60 queries per hour with a maximum of 5 concurrent queries.
| Name | Type | Req | Description |
|---|---|---|---|
| bookmark_id | integer | yes | The unique identifier of your Insights report, found in the Mixpanel URL path after 'report-' in the editor-card-id parameter. |
| project_id | integer | yes | The Mixpanel project ID associated with your account. |
No output schema declared.
No examples provided.
get_retention_frequency_report Get Retention Frequency Report ~269
Retrieve a frequency report analyzing user retention and addiction patterns over a specified date range. Returns the distribution of returning user actions segmented by time unit and optional properties.
| Name | Type | Req | Description |
|---|---|---|---|
| addiction_unit | string | yes | The granularity at which to measure action frequency: hour or day. |
| event | string | – | The specific event name to analyze for returning user counts. If omitted, analyzes all events. |
| from_date | string | yes | Start date for the analysis period in YYYY-MM-DD format (inclusive). |
| limit | integer | – | Maximum number of segmentation values to return when segmenting by the 'on' property. Has no effect if 'on' is not specified. |
| on | string | – | A property expression to segment results by. When specified, the report breaks down metrics by distinct values of this property. Supports nested properties as documented in segmentation expressions. |
| project_id | integer | yes | The Mixpanel project ID to query against. |
| to_date | string | yes | End date for the analysis period in YYYY-MM-DD format (inclusive). |
| unit | string | yes | The time period granularity for the overall report: day, week, or month. |
| where | string | – | A filter expression to narrow the returning events analyzed. Supports property-based conditions and logical operators as documented in segmentation expressions. |
No output schema declared.
No examples provided.
get_retention_report Get Retention Report ~389
Retrieve a retention analysis report for a Mixpanel project, measuring how users return to your product over time. Supports both first-time user retention (birth) and recurring user retention (compounded) with optional event and property filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | – | Optional event name to analyze retention for (e.g., 'Viewed report'). If omitted, retention is calculated across all events. |
| from_date | string | yes | Start date for the retention analysis period in YYYY-MM-DD format (e.g., 2024-01-15). |
| interval_count | integer | – | Number of time intervals to return in the retention analysis; defaults to 1. The report includes a '0th' interval for events occurring within the first interval period. |
| limit | integer | – | Maximum number of segmentation values to return in results. Only used when the 'on' parameter is specified for property-based segmentation. |
| on | string | – | Optional property expression to segment the returning event by (e.g., properties["plan_type"]). Only applies when segmenting retention results. |
| project_id | integer | yes | The Mixpanel project ID to query retention data for. |
| retention_type | string | – | Retention measurement type: 'birth' tracks first-time user retention, while 'compounded' tracks recurring retention. Defaults to 'birth' if not specified. |
| to_date | string | yes | End date for the retention analysis period in YYYY-MM-DD format (e.g., 2024-01-31). |
| unbounded_retention | boolean | – | When enabled, retention values accumulate from right to left, so each interval includes users retained on that day and all subsequent days. Defaults to false for standard interval-by-interval countin… |
| where | string | – | Optional filter expression to segment the initial cohort by user properties (e.g., properties["$os"]=="Linux"). Uses Mixpanel expression syntax. |
No output schema declared.
No examples provided.
get_segmented_event_data Get Segmented Event Data ~234
Retrieve event data segmented and filtered by properties from your Mixpanel project. Results can be broken down by a specific property dimension and filtered by event criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | The name of the event to query. Specify a single event name, not multiple events. |
| format | string | – | Optional output format. Set to 'csv' for comma-separated values; omit for default JSON format. |
| from_date | string | yes | Query start date in YYYY-MM-DD format (inclusive). |
| limit | integer | – | Maximum number of top property values to return (defaults to 60, maximum 10,000). Only applies when segmenting with the 'on' parameter. |
| on | string | – | Optional property expression to segment results by. Omit to get aggregate counts without segmentation. See segmentation expressions documentation for syntax. |
| project_id | integer | yes | Your Mixpanel project identifier (numeric ID). |
| to_date | string | yes | Query end date in YYYY-MM-DD format (inclusive). |
| where | string | – | Optional filter expression to narrow events by property values. See segmentation expressions documentation for syntax. |
No output schema declared.
No examples provided.
list_cohorts List Cohorts ~76
Retrieve all saved cohorts in a Mixpanel project, including metadata such as name, ID, user count, description, creation date, and visibility settings. Use the /engage endpoint with filter_by_cohort to retrieve the actual users within a cohort.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | The numeric identifier for your Mixpanel project. |
No output schema declared.
No examples provided.
list_event_property_top_values List Event Property Top Values ~133
Retrieve the most frequently occurring values for a specific event property in Mixpanel. Useful for understanding the distribution and cardinality of property values within an event.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | The name of the event to analyze. Provide a single event name (not multiple events). |
| limit | integer | – | The maximum number of top values to return in the response. Defaults to 255 if not specified. |
| name | string | yes | The property name within the event whose top values you want to retrieve. |
| project_id | integer | yes | The Mixpanel project ID that contains the event data you want to query. |
No output schema declared.
No examples provided.
list_saved_funnels List Saved Funnels ~52
Retrieve a list of all saved funnels in your Mixpanel project, including their names and unique funnel identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | The Mixpanel project ID associated with the funnels you want to retrieve. |
No output schema declared.
No examples provided.
list_top_event_names List Top Event Names ~133
Retrieve the most frequently occurring events from the past 31 days, analyzed by the specified metric type. Useful for understanding user behavior patterns and identifying key interactions in your product.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of top events to return in the results, up to 255. Defaults to 255 if not specified. |
| project_id | integer | yes | The Mixpanel project ID that identifies which project's event data to query. |
| type | string | yes | The type of event analysis to perform: 'general' for event frequency, 'unique' for distinct user counts, or 'average' for per-user averages. |
No output schema declared.
No examples provided.
list_top_event_properties List Top Event Properties ~114
Retrieve the most frequently used property names for a specified event in your Mixpanel project. Useful for understanding which properties are most relevant to an event's analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | yes | The name of the event to retrieve properties for. Provide a single event name, not multiple events. |
| limit | integer | – | The maximum number of top properties to return in the results. Defaults to 10 if not specified. |
| project_id | integer | yes | The Mixpanel project ID that contains the event you want to analyze. |
No output schema declared.
No examples provided.
list_top_events List Top Events ~107
Retrieve today's top events ranked by frequency, including event counts and normalized percent change compared to yesterday.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of events to return in the results. Defaults to 100 if not specified. |
| project_id | integer | yes | The Mixpanel project ID to query events for. |
| type | string | yes | The type of event analysis to perform: 'general' for event frequency, 'unique' for unique user counts, or 'average' for average event values. |
No output schema declared.
No examples provided.
query_profiles Query Profiles ~307
Query user or group profiles from a Mixpanel project with optional filtering, property selection, and cohort-based retrieval to retrieve detailed profile data.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_timestamp | integer | – | A Unix timestamp specifying the point-in-time snapshot for profile data. Required when exporting more than 1,000 profiles with behavior filters to avoid caching errors. |
| data_group_id | string | – | The group key ID for querying group profiles instead of user profiles. Required when analyzing group-level analytics data rather than individual users. |
| distinct_ids | string | – | A JSON array of distinct IDs to retrieve profiles for. When provided, limits results to only these specific user or group identifiers. |
| filter_by_cohort | string | – | A JSON object with an `id` key containing a cohort ID to filter profiles by cohort membership. Mutually exclusive with behavior-based filtering. |
| include_all_users | boolean | – | When using cohort filtering, set to `true` (default) to include all distinct IDs even without profiles, or `false` to return only IDs with existing profiles. |
| output_properties | array | – | A JSON array of property names to include in the response. Restricting to needed properties significantly reduces data transfer and improves query performance. |
| project_id | integer | yes | The Mixpanel project ID to query profiles from. Required to identify which project's data to access. |
| where | string | – | A filter expression to narrow results by profile properties or attributes. Supports complex conditions to target specific user or group segments. |
No output schema declared.
No examples provided.
What is the com.mcparmory/mixpanel MCP server?
com.mcparmory/mixpanel is an MCP server listed in the public MCP registry as com.mcparmory/mixpanel. Analyze user behavior with funnels, retention, cohorts, and event segmentation. This page covers its PyPI package (mcparmory-mixpanel).
Is the com.mcparmory/mixpanel MCP server safe to use?
com.mcparmory/mixpanel scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/mixpanel MCP server expose?
com.mcparmory/mixpanel exposes 19 tools: get_insights_report, get_funnel_data, list_saved_funnels, get_retention_report, get_retention_frequency_report, and 14 more. Their descriptions and schemas cost roughly 3,656 tokens of context every time the server is loaded.
Is the com.mcparmory/mixpanel MCP server still maintained?
com.mcparmory/mixpanel is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.