# Bitmovin Observability MCP (remote · analytics.mcp.bitmovin.com) Query and analyse your data from Bitmovin Observability - Trust score: 74/100 (medium) - Change this week: +5 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-15 ## Components - remote · `analytics.mcp.bitmovin.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-bitmovin-mcp-analytics-analytics-mcp/analytics.md), [page](https://verifymcp.io/servers/com-bitmovin-mcp-analytics-analytics-mcp/analytics) ## Channel facts - Endpoint: `https://analytics.mcp.bitmovin.com` - Transports: `streamable-http, sse` - Auth: `none` - Version: `0.0.1` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-15. - **Endpoint Security**: 74/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 75/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 7996 tokens (~470/item across 17 items; 11 tools + 6 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. - Supports UI / widget rendering. ## Install ### Claude ```bash claude mcp add --transport http com-bitmovin-mcp-analytics-analytics-mcp https://analytics.mcp.bitmovin.com/ ``` ### Codex ```toml [mcp_servers.com-bitmovin-mcp-analytics-analytics-mcp] url = "https://analytics.mcp.bitmovin.com/" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-bitmovin-mcp-analytics-analytics-mcp": { "type": "remote", "url": "https://analytics.mcp.bitmovin.com/", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-bitmovin-mcp-analytics-analytics-mcp --url https://analytics.mcp.bitmovin.com/ --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-bitmovin-mcp-analytics-analytics-mcp: url: "https://analytics.mcp.bitmovin.com/" ``` ### Other ```json { "mcpServers": { "com-bitmovin-mcp-analytics-analytics-mcp": { "type": "http", "url": "https://analytics.mcp.bitmovin.com/" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-15 (score 74, +1) No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-13 (score 73, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-11 (score 72, +2) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-08-09 (score 70, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-08-08 (score 69, 0) - [functional improvement] Stability: unverified → 0.03 ### 2026-08-07 (score 69) First indexed and scored. ## MCP tools (11) ### `query` (~1097 tokens) Query timeseries metric Query a metric over a time range (start/end) for a license as a TIME SERIES — always renders a chart. Use this for trends and license-wide analytics over a period (e.g. 'last week', 'last 30 days', 'yesterday'). Bucket size is chosen automatically from start/end; there is no interval field to set. For a single aggregated number (one total/average over the whole period, NO chart), use the separate `queryTotal` tool instead. IMPORTANT: Before using this tool, you must: 1) Resolve the correct metric keyword - commonly used names may be mapped differently in the API (e.g., 'plays' is actually 'impression_id'). Prefer the 'searchMetrics' tool to find the right keyword cheaply; use 'getAvailableMetrics' only when you need the full catalog. 2) Ensure you have a licenseKey. If the user hasn't specified one use `peekAllLicenses`. AD ANALYTICS: ad metrics use 'ad_'-prefixed keywords and are queried against a separate ads dataset. The ad completion funnel is: 'ad_quartile_1' (first quartile / 25%) -> 'ad_midpoint' (50%) -> 'ad_quartile_3' (third quartile / 75%) -> 'ad_completions'. Other ad metrics: 'ad_impressions', 'ad_starts', 'ad_clicks', 'ad_skips', 'ad_startup_time', 'ad_error_percentage', 'ad_error_sessions', 'ad_time_played', 'ad_play_percentage', 'ad_unique_users'. For ad questions, if the user has NOT specified a license, call `peekAllLicenses` — its output shows which licenses have ad data. If EXACTLY ONE license has ad data, use it automatically (state which one you picked); if SEVERAL do, present those and ASK the user to choose ONE; if NONE do, tell the user no ad data is available. Do NOT query multiple licenses; reuse the chosen license for the rest of the conversation. With an ad metric, filters and groupBy must use the AD-specific attributes from 'searchFilters' / 'getAvailableFilters' (e.g. 'AD_SYSTEM', 'AD_POSITION', 'ADVERTISER_NAME') — playback attributes and ad attributes are NOT interchangeable. OPTIONAL 3) Use the 'searchFilters' tool to find filter a… Input parameters: - `aggregation` (string): aggregation method: 'average', 'median', or 'percentile'. If not specified, uses the metric's default aggregation method - `end` (string, required): end date/time in ISO 8601 format (e.g., '2025-10-02T00:00:00') - `filters` (array): optional filters to apply to the query - `licenseKey` (string, required): license key (uuid) to query - `metric` (string, required): the metric to query. before setting a value, resolve the keyword with the `searchMetrics` tool - `percentile` (number): percentile value (0-100) - required when aggregation is 'percentile' - `start` (string, required): start date/time in ISO 8601 format (e.g., '2025-10-01T00:00:00') - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `queryGroupBy` (~1275 tokens) Query metric grouped by categories query metric grouped by categories. IMPORTANT: Before using this tool, you must: 1) Resolve the correct metric keyword - commonly used names may be mapped differently in the API (e.g., 'plays' is actually 'impression_id'). Prefer the 'searchMetrics' tool to find the right keyword cheaply; use 'getAvailableMetrics' only when you need the full catalog. 2) Ensure you have a licenseKey. If the user hasn't specified one use `peekAllLicenses`. AD ANALYTICS: ad metrics use 'ad_'-prefixed keywords and are queried against a separate ads dataset. The ad completion funnel is: 'ad_quartile_1' (first quartile / 25%) -> 'ad_midpoint' (50%) -> 'ad_quartile_3' (third quartile / 75%) -> 'ad_completions'. Other ad metrics: 'ad_impressions', 'ad_starts', 'ad_clicks', 'ad_skips', 'ad_startup_time', 'ad_error_percentage', 'ad_error_sessions', 'ad_time_played', 'ad_play_percentage', 'ad_unique_users'. For ad questions, if the user has NOT specified a license, call `peekAllLicenses` — its output shows which licenses have ad data. If EXACTLY ONE license has ad data, use it automatically (state which one you picked); if SEVERAL do, present those and ASK the user to choose ONE; if NONE do, tell the user no ad data is available. Do NOT query multiple licenses; reuse the chosen license for the rest of the conversation. With an ad metric, filters and groupBy must use the AD-specific attributes from 'searchFilters' / 'getAvailableFilters' (e.g. 'AD_SYSTEM', 'AD_POSITION', 'ADVERTISER_NAME') — playback attributes and ad attributes are NOT interchangeable. 3) REQUIRED: Resolve the exact groupBy attribute name BEFORE calling this tool — do NOT guess. Prefer the 'searchFilters' tool to find the right attribute; use 'getAvailableFilters' only when you need the full catalog. Common naming guesses are often wrong (e.g., 'OPERATING_SYSTEM' is invalid; the correct attribute is 'OPERATINGSYSTEM'). Calling this tool with an unknown attribute will fail with a validation error. 4) MANDATORY when grouping by… Input parameters: - `aggregation` (string): aggregation method: 'average', 'median', or 'percentile'. If not specified, uses the metric's default aggregation method - `end` (string, required): end date/time in ISO 8601 format (e.g., '2025-10-02T00:00:00') - `filters` (array): optional filters to apply to the query - `groupBy` (required): category (or array of categories) to group results by — e.g. Case-insensitive: ['BROWSER', 'COUNTRY'] or just 'BROWSER'. Prefer an array even for a single value. Use the `searchFilters` tool (pass th… - `licenseKey` (string, required): license key (uuid) to query - `metric` (string, required): the metric to query. before setting a value, resolve the keyword with the `searchMetrics` tool - `percentile` (number): percentile value (0-100) - required when aggregation is 'percentile' - `start` (string, required): start date/time in ISO 8601 format (e.g., '2025-10-01T00:00:00') - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `queryTotal` (~1192 tokens) Get an aggregated metric value (one or more metrics) Get an aggregated value (one number) for a metric over a time range — no chart, no time bucketing. Can fetch SEVERAL metrics in one call: pass an array to `metric` to get one value per metric (e.g. the ad completion funnel), instead of calling this tool repeatedly. Use ONLY when the user asks for totals/averages/median/p95 over a whole period (e.g. 'total plays last month', 'average startup time yesterday', 'p95 rebuffer last week', 'the ad funnel counts last week'). For trends or any 'how did X change over time' / 'show last week' question, use the `query` tool instead — it always renders a chart. IMPORTANT: Before using this tool, you must: 1) Resolve the correct metric keyword - commonly used names may be mapped differently in the API (e.g., 'plays' is actually 'impression_id'). Prefer the 'searchMetrics' tool to find the right keyword cheaply; use 'getAvailableMetrics' only when you need the full catalog. 2) Ensure you have a licenseKey. If the user hasn't specified one use `peekAllLicenses`. AD ANALYTICS: ad metrics use 'ad_'-prefixed keywords and are queried against a separate ads dataset. The ad completion funnel is: 'ad_quartile_1' (first quartile / 25%) -> 'ad_midpoint' (50%) -> 'ad_quartile_3' (third quartile / 75%) -> 'ad_completions'. Other ad metrics: 'ad_impressions', 'ad_starts', 'ad_clicks', 'ad_skips', 'ad_startup_time', 'ad_error_percentage', 'ad_error_sessions', 'ad_time_played', 'ad_play_percentage', 'ad_unique_users'. For ad questions, if the user has NOT specified a license, call `peekAllLicenses` — its output shows which licenses have ad data. If EXACTLY ONE license has ad data, use it automatically (state which one you picked); if SEVERAL do, present those and ASK the user to choose ONE; if NONE do, tell the user no ad data is available. Do NOT query multiple licenses; reuse the chosen license for the rest of the conversation. With an ad metric, filters and groupBy must use the AD-specific attributes from 'searchFilters' / 'getAvailableFilte… Input parameters: - `aggregation` (string): aggregation method: 'average', 'median', or 'percentile'. If not specified, uses the metric's default aggregation method - `end` (string, required): end date/time in ISO 8601 format (e.g., '2025-10-02T00:00:00') - `filters` (array): optional filters to apply to the query - `licenseKey` (string, required): license key (uuid) to query - `metric` (required): the metric to query — a single keyword, or an ARRAY of keywords to fetch together in ONE call (returns one value per metric). Prefer the array for multi-metric asks like the ad completion funnel: ['a… - `percentile` (number): percentile value (0-100) - required when aggregation is 'percentile' - `start` (string, required): start date/time in ISO 8601 format (e.g., '2025-10-01T00:00:00') - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `peekAllLicenses` (~482 tokens) Peek all licenses View a summary of all available licenses with their recent play counts and percentage distribution. Use this to understand what licenses exist and their relative usage. When a user asks about licenses by ranking (e.g., 'biggest', 'most active', 'first'), use this to identify which license matches that criteria before querying. Input parameters: - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `getImpressionOverview` (~549 tokens) Get impression overview Inspect a SINGLE playback session identified by a specific impressionId. Returns that one session's static properties (device, location, player) and its aggregated metrics (total played time, buffering, video quality). REQUIRES an impressionId. Do NOT use this for license-wide metrics, totals, trends, or any time-range ('last week', start/end) analysis — this tool does not accept start/end. For metrics over a time period use the 'query' tool; for breakdowns by category use 'queryGroupBy'. Input parameters: - `impressionId` (string, required): Impression ID - `licenseKey` (string, required): license key (uuid) to query - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `analyzeImpression` (~550 tokens) Analyze impression Deep-dive analysis of a SINGLE playback session identified by a specific impressionId: static properties, aggregated metrics, state-transition timeline, and an AI-powered interpretation of session quality. Use for detailed single-session troubleshooting. REQUIRES an impressionId. Do NOT use this for license-wide metrics, totals, trends, or any time-range ('last week', start/end) analysis — this tool does not accept start/end. For metrics over a time period use the 'query' tool; for breakdowns by category use 'queryGroupBy'. Input parameters: - `impressionId` (string, required): Impression ID - `licenseKey` (string, required): license key (uuid) to query - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `fetchImpressions` (~732 tokens) List impression ids for a timeframe List the impression ids (individual playback session ids) for a license over a time range, optionally narrowed by filters. Returns the ids themselves — NOT counts, totals, or trends. Use this to enumerate sessions before drilling into specific ones with `getImpressionOverview` or `analyzeImpression`. Typical uses: 'give me impression ids from yesterday', 'list sessions on Safari that errored last week', 'sample sessions from country US'. Every matching session is eligible (including failed/setup sessions), not only successful plays. Results are capped (default 100, max 200); if truncated, narrow the timeframe/filters or raise `limit`. REQUIRED: 1) a licenseKey (use `peekAllLicenses` if none given). OPTIONAL: 2) use `searchFilters` to resolve filter attributes/operators before setting `filters`. For metric counts/trends over a period use `query` / `queryTotal`; for category breakdowns use `queryGroupBy`. Input parameters: - `end` (string, required): end date/time in ISO 8601 format (e.g., '2025-10-02T00:00:00') - `filters` (array): optional filters to apply to the query - `licenseKey` (string, required): license key (uuid) to query - `limit` (integer): maximum number of impression ids to return (1-200, default 100) - `start` (string, required): start date/time in ISO 8601 format (e.g., '2025-10-01T00:00:00') - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `getAvailableMetrics` (~448 tokens) Get available metrics List the full catalog of metrics with their supported aggregation methods. Prefer searchMetrics to resolve a single keyword; use this only when you need every metric. Input parameters: - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `getAvailableFilters` (~463 tokens) Get available filters List the full catalog of filter attributes with their supported operators. Prefer searchFilters to resolve a single attribute; use this only when you need every filter. Input parameters: - `licenseKey` (string): license key (uuid) to query - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `searchMetrics` (~509 tokens) Search metrics Find the exact metric keyword for a topic or question (e.g. 'buffering', 'how many errors'). Preferred way to resolve a metric keyword; use getAvailableMetrics only to list the full catalog. Input parameters: - `limit` (integer): maximum number of results to return (default 5) - `query` (string, required): free-text term or question describing the metric/filter you want (e.g., 'buffering', 'browser', 'how many errors') - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ### `searchFilters` (~542 tokens) Search filters Find the exact filter/group-by attribute keyword for a topic or question (e.g. 'browser', 'device type', 'content tier'). Preferred way to resolve an attribute; use 'licenseKey' to resolve custom namings of attributes; use getAvailableFilters only to list the full static catalog. Input parameters: - `licenseKey` (string): license key (uuid) to query - `limit` (integer): maximum number of results to return (default 5) - `query` (string, required): free-text term or question describing the metric/filter you want (e.g., 'buffering', 'browser', 'how many errors') - `user_intent` (string): A concise summary of what the user is trying to accomplish, derived from their message or the conversation context that triggered this tool call. This is used to understand the user's intent and cont… ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-bitmovin-mcp-analytics-analytics-mcp/analytics#diagnostics ## Score history - 2026-08-15: 74 - 2026-08-14: 73 - 2026-08-13: 73 - 2026-08-12: 72 - 2026-08-11: 72 - 2026-08-10: 70 - 2026-08-09: 70 - 2026-08-08: 69 - 2026-08-07: 69 ## Links - Remote endpoint: https://analytics.mcp.bitmovin.com/ - Website: https://bitmovin.com/ - Changelog RSS feed: https://verifymcp.io/servers/com-bitmovin-mcp-analytics-analytics-mcp/analytics.xml - Changelog JSON feed: https://verifymcp.io/servers/com-bitmovin-mcp-analytics-analytics-mcp/analytics.json - HTML version of this page: https://verifymcp.io/servers/com-bitmovin-mcp-analytics-analytics-mcp/analytics