Agent Analytics

io.github.dannyshmueli/agent-analytics-mcpVersion 1.0.0

Analytics your AI agent can actually use. Track, experiment, and optimize via MCP.

Status

Responds518 msNov 14, 2026, 14:49 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:49 UTC
Latency: 518 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.agentanalytics.sh/mcpResponds518 msNov 14, 2026, 14:49 UTC

No sign-in

Claude Code

claude mcp add --transport http agent-analytics-mcp https://mcp.agentanalytics.sh/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: agent-analytics-mcp
Remote MCP server URL: https://mcp.agentanalytics.sh/mcp

Cursor

{
  "mcpServers": {
    "agent-analytics-mcp": {
      "url": "https://mcp.agentanalytics.sh/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"agent-analytics-mcp","type":"http","url":"https://mcp.agentanalytics.sh/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

32 tools

Tools of Agent Analytics
	Description		Read-only	Idempotent	Open world
`account_usage`Read current account plan, usage, billing estimate and spend cap, Pro pricing, and a human payment handoff when needed. Requires account:read. Read-only: cannot charge or manage billing. Call again after checkout to verify hosted entitlement, then retry the original task.	Read current account plan, usage, billing estimate and spend cap, Pro pricing, and a human payment handoff when needed. Requires account:read. Read-only: cannot charge or manage billing. Call again after checkout to verify hosted entitlement, then retry the original task.	No	Yes	Yes	No
`all_sites_bot_traffic`Filtered automated traffic across all active projects in your account.	Filtered automated traffic across all active projects in your account.	No	Yes	Not declared	No
`all_sites_overview`Historical summary across all projects in your account: total events, active project count, daily trend, and top projects.	Historical summary across all projects in your account: total events, active project count, daily trend, and top projects.	No	Yes	Not declared	No
`analytics_breakdown`Top property values ranked by count (pages, referrers, UTM sources, etc.) Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Top property values ranked by count (pages, referrers, UTM sources, etc.) Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`analytics_funnel`Funnel analysis: track where users drop off across a sequence of events (e.g. page_view → signup → purchase). Returns per-step user counts, conversion rates, and average time between steps. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Funnel analysis: track where users drop off across a sequence of events (e.g. page_view → signup → purchase). Returns per-step user counts, conversion rates, and average time between steps. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`analytics_heatmap`Day-of-week × hour traffic grid with peak detection (times in UTC) Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Day-of-week × hour traffic grid with peak detection (times in UTC) Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`analytics_insights`Period-over-period comparison with trend (events, users, bounce rate, session duration) Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Period-over-period comparison with trend (events, users, bounce rate, session duration) Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`analytics_overview`Get time series chart, KPIs (events, users), and country breakdown (events, unique users) for a project over N days Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Get time series chart, KPIs (events, users), and country breakdown (events, unique users) for a project over N days Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`analytics_pages`Entry/exit page stats with bounce rate, avg duration, events per session Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Entry/exit page stats with bounce rate, avg duration, events per session Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`analytics_panel`Use this when you want to explore an authorized project's analytics beside the conversation. Opens a compact project/view picker; accepts empty input. Analysis queries retain their existing plan and access checks. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Use this when you want to explore an authorized project's analytics beside the conversation. Opens a compact project/view picker; accepts empty input. Analysis queries retain their existing plan and access checks. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Yes	No
`analytics_paths`Bounded session path analysis from entry pages to goal, drop-off, or truncation. Useful for connecting page behavior to funnels, retention, and experiments. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Bounded session path analysis from entry pages to goal, drop-off, or truncation. Useful for connecting page behavior to funnels, retention, and experiments. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`analytics_retention`Cohort retention analysis — track what % of users return over time. By default uses session-based retention (any return visit counts). Pass 'event' to switch to event-based retention. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Cohort retention analysis — track what % of users return over time. By default uses session-based retention (any return visit counts). Pass 'event' to switch to event-based retention. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`analytics_sessions`Session duration histogram with engaged percentage and median bucket Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Session duration histogram with engaged percentage and median bucket Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`append_project_annotation`Append one annotation to project context. Append-only: goals, activation events, glossary entries, and existing annotations stay in place. Allowed fields are project, occurred_at (ISO-8601 timestamp, stored as UTC), title (max 120 characters), and an optional note (max 500 characters). The annotation identity is normalized occurred_at plus title. A duplicate returns 200 with appended false and keeps the stored note. The 100 annotation cap returns 409 and stores nothing. Use this for a meaningful landing page, pricing, onboarding, feature, release, or experiment change. Do not store git commit logs, noisy edits, PII, secrets, or long notes.	Append one annotation to project context. Append-only: goals, activation events, glossary entries, and existing annotations stay in place. Allowed fields are project, occurred_at (ISO-8601 timestamp, stored as UTC), title (max 120 characters), and an optional note (max 500 characters). The annotation identity is normalized occurred_at plus title. A duplicate returns 200 with appended false and keeps the stored note. The 100 annotation cap returns 409 and stores nothing. Use this for a meaningful landing page, pricing, onboarding, feature, release, or experiment change. Do not store git commit logs, noisy edits, PII, secrets, or long notes.	No	No	Yes	No
`bot_traffic_overview`Filtered automated traffic for a single project: automated requests, dropped events, categories, and top actors.	Filtered automated traffic for a single project: automated requests, dropped events, categories, and top actors.	No	Yes	Not declared	No
`compare`Compare a shipped change and return a keep, revert, or extend verdict. Compare is a free read. Each successful call counts as one metered read. Pass ship_date plus window_days, or explicit baseline and compare windows. window_days is an integer from 1 to 90 and a multiple of 7 (default 7, so the largest ship window is 84). The ship day is in neither window: baseline is ship-N through ship-1, and compare is ship+1 through ship+N. Run a day-7 read on ship day + 8 so the last day is complete. If either window includes today UTC, the verdict is extend with reason incomplete_current_day, and that reason overrides every other verdict. goal_event is required and is counted as unique converters (count_mode unique_users): a user who fires the goal more than once counts once. denominator_event defaults to page_view and is counted as unique users. rate = goal_converters / denominator_unique_users. Optional filters use the query filter shape and apply as they do today. A filter on event is rejected. Optional denominator_filters use the same {field, op, value} shape and operators and apply only to denominator events when computing denominator_unique_users. goal_converters still counts only goal users inside that filtered denominator. Omit denominator_filters or pass [] for today's behavior. Max 10 entries. To exclude one-hit 404 page views from the denominator: denominator_filters [{"field":"properties.title","op":"neq","value":"Page not found \| grokbotpages.com"}]. rule thresholds are relative fractions (0.15 means +15%). The absolute value of keep_threshold and revert_threshold must be at most 5. Omitted rule fields use the documented day-7 examples (keep_threshold 0.15, revert_threshold -0.1, min_denominator 200, min_goal_events 20 unique converters across both windows). Those examples are not product policy. Verdict order: extend incomplete_current_day; extend below_min_sample; extend zero_denominator; extend zero_baseline when lift is null; revert revert_threshold_met only	Compare a shipped change and return a keep, revert, or extend verdict. Compare is a free read. Each successful call counts as one metered read. Pass ship_date plus window_days, or explicit baseline and compare windows. window_days is an integer from 1 to 90 and a multiple of 7 (default 7, so the largest ship window is 84). The ship day is in neither window: baseline is ship-N through ship-1, and compare is ship+1 through ship+N. Run a day-7 read on ship day + 8 so the last day is complete. If either window includes today UTC, the verdict is extend with reason incomplete_current_day, and that reason overrides every other verdict. goal_event is required and is counted as unique converters (count_mode unique_users): a user who fires the goal more than once counts once. denominator_event defaults to page_view and is counted as unique users. rate = goal_converters / denominator_unique_users. Optional filters use the query filter shape and apply as they do today. A filter on event is rejected. Optional denominator_filters use the same {field, op, value} shape and operators and apply only to denominator events when computing denominator_unique_users. goal_converters still counts only goal users inside that filtered denominator. Omit denominator_filters or pass [] for today's behavior. Max 10 entries. To exclude one-hit 404 page views from the denominator: denominator_filters [{"field":"properties.title","op":"neq","value":"Page not found \| grokbotpages.com"}]. rule thresholds are relative fractions (0.15 means +15%). The absolute value of keep_threshold and revert_threshold must be at most 5. Omitted rule fields use the documented day-7 examples (keep_threshold 0.15, revert_threshold -0.1, min_denominator 200, min_goal_events 20 unique converters across both windows). Those examples are not product policy. Verdict order: extend incomplete_current_day; extend below_min_sample; extend zero_denominator; extend zero_baseline when lift is null; revert revert_threshold_met only	No	Yes	Not declared	No
`create_experiment`Create an A/B experiment	Create an A/B experiment	No	No	Not declared	No
`create_project`Create a new Agent Analytics project. Returns the tracking snippet and API example. Idempotent: returns the existing project if the name is already taken. The tracking snippet includes data-track-vitals="true" so new installs collect Core Web Vitals on page_view.	Create a new Agent Analytics project. Returns the tracking snippet and API example. Idempotent: returns the existing project if the name is already taken. The tracking snippet includes data-track-vitals="true" so new installs collect Core Web Vitals on page_view.	No	No	Not declared	No
`delete_experiment`Delete an experiment	Delete an experiment	Yes	No	Not declared	No
`errors`Read grouped $error events for a project (GET /errors). Errors is a Pro read. A free account gets 403 PRO_REQUIRED, the same status and error code as POST /query, and that rejection is not metered. Each successful call counts as one metered read. Errors is the post-ship guardrail next to compare: after a ship, read errors for the same window before you keep the change. The group key is a SHA-256 fingerprint of the normalized message (URL query strings and hashes removed, then UUIDs, hex hashes, and numbers replaced), the source filename without query or hash, and the numeric line. There is no stack, and col is not part of the key. Each group includes fingerprint, a sample message, source, line, count, users, sessions, first_seen, last_seen, and up to 3 top_paths. count, users, sessions, and top_paths use the since/until window. first_seen and last_seen use every stored $error for that fingerprint. Groups with no event in the window are omitted. since defaults to 7 days and accepts 7d or YYYY-MM-DD. until defaults to today UTC. limit defaults to 20 and maxes at 100. new_since is a YYYY-MM-DD or an annotation title. A date is used directly. Any other string matches project annotations by exact title, then case-insensitive title, then note, then substring. Zero matches is 400. More than one match is 400 with matches listing occurred_at and title. The group new_since boolean is present only when this param is set, and is true when first_seen is on or after the resolved date. new_since_annotation is returned only when new_since matched an annotation. Every response includes approximate, a boolean. When approximate is true, caps is an array of the scan caps that were hit: distinct_triples and window_rows. There is no singular cap field. A large project stays 200. The response also includes truncated.	Read grouped $error events for a project (GET /errors). Errors is a Pro read. A free account gets 403 PRO_REQUIRED, the same status and error code as POST /query, and that rejection is not metered. Each successful call counts as one metered read. Errors is the post-ship guardrail next to compare: after a ship, read errors for the same window before you keep the change. The group key is a SHA-256 fingerprint of the normalized message (URL query strings and hashes removed, then UUIDs, hex hashes, and numbers replaced), the source filename without query or hash, and the numeric line. There is no stack, and col is not part of the key. Each group includes fingerprint, a sample message, source, line, count, users, sessions, first_seen, last_seen, and up to 3 top_paths. count, users, sessions, and top_paths use the since/until window. first_seen and last_seen use every stored $error for that fingerprint. Groups with no event in the window are omitted. since defaults to 7 days and accepts 7d or YYYY-MM-DD. until defaults to today UTC. limit defaults to 20 and maxes at 100. new_since is a YYYY-MM-DD or an annotation title. A date is used directly. Any other string matches project annotations by exact title, then case-insensitive title, then note, then substring. Zero matches is 400. More than one match is 400 with matches listing occurred_at and title. The group new_since boolean is present only when this param is set, and is true when first_seen is on or after the resolved date. new_since_annotation is returned only when new_since matched an annotation. Every response includes approximate, a boolean. When approximate is true, caps is an array of the scan caps that were hit: distinct_triples and window_rows. There is no singular cap field. A large project stays 200. The response also includes truncated.	No	Yes	Not declared	No
`get_experiment`Get experiment details with results Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Get experiment details with results Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`get_project_context`Get compact self-improving project context: goals, activation events, event-name glossary, and major date annotations used to interpret analytics results. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Get compact self-improving project context: goals, activation events, event-name glossary, and major date annotations used to interpret analytics results. Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`list_experiments`List A/B experiments for a project Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	List A/B experiments for a project Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`list_projects`List all your Agent Analytics projects Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	List all your Agent Analytics projects Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`live_now`Real-time snapshot: active visitors, sessions, events per minute, top pages, and recent events. Reads from in-memory ring buffer — no D1 query.	Real-time snapshot: active visitors, sessions, events per minute, top pages, and recent events. Reads from in-memory ring buffer — no D1 query.	No	Yes	Not declared	No
`properties`Discover event names and property keys from recent events Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Discover event names and property keys from recent events Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`properties_received`Property keys by event name, sampled from recent events Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	Property keys by event name, sampled from recent events Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`query`Run a flexible ad-hoc analytics query with custom metrics, filters, grouping, date ranges, and privacy-first customer email lookup. This is the most powerful endpoint — use it when other tools don't answer the question. Examples of questions this tool answers: - "How many signups from Germany this week?" → filters: [{field:"event",op:"eq",value:"signup"},{field:"country",op:"eq",value:"DE"}] - "Which events contain 'page' in the name?" → filters: [{field:"event",op:"contains",value:"page"}], group_by: ["event"] - "Daily unique users for the last 30 days" → metrics: ["unique_users"], group_by: ["date"], date_from: "30d" - "Events per country" → group_by: ["country"] - "Signups by path and day" → metrics: ["event_count"], filters: [{field:"event",op:"eq",value:"signup"}], group_by: ["date", "properties.path"] - "p75 of LCP" → use the web_vitals tool (p75 is the headline). For an ad-hoc percentile on hosted, metrics: ["p75"], property: "cwv_lcp", filters: [{field:"event",op:"eq",value:"page_view"}] - "Revenue collected" → metrics: ["sum"], property: "revenue" Filter operators: eq, neq, gt, lt, gte, lte, contains Filterable fields: event, user_id, date, country, session_id, timestamp, and any properties.* field (e.g. properties.path) For customer-specific reads, use the top-level email input instead of hashing locally. Raw email is sent only in the authenticated HTTPS POST body; the server matches via a project-scoped HMAC index and does not store raw email in event rows or profile traits. Built-in fields are a closed list. Event properties such as referrer, utm_source, path, browser, and hostname must be queried as properties.referrer, properties.utm_source, properties.path, properties.browser, and properties.hostname. Invalid filter fields fail loudly and return /properties-style guidance instead of being silently ignored. Group by: event, date, user_id, session_id, country, and at most one properties.<key>. The key matches ^[A-Za-z0-9_]{1,128}$, the same rule as pr	Run a flexible ad-hoc analytics query with custom metrics, filters, grouping, date ranges, and privacy-first customer email lookup. This is the most powerful endpoint — use it when other tools don't answer the question. Examples of questions this tool answers: - "How many signups from Germany this week?" → filters: [{field:"event",op:"eq",value:"signup"},{field:"country",op:"eq",value:"DE"}] - "Which events contain 'page' in the name?" → filters: [{field:"event",op:"contains",value:"page"}], group_by: ["event"] - "Daily unique users for the last 30 days" → metrics: ["unique_users"], group_by: ["date"], date_from: "30d" - "Events per country" → group_by: ["country"] - "Signups by path and day" → metrics: ["event_count"], filters: [{field:"event",op:"eq",value:"signup"}], group_by: ["date", "properties.path"] - "p75 of LCP" → use the web_vitals tool (p75 is the headline). For an ad-hoc percentile on hosted, metrics: ["p75"], property: "cwv_lcp", filters: [{field:"event",op:"eq",value:"page_view"}] - "Revenue collected" → metrics: ["sum"], property: "revenue" Filter operators: eq, neq, gt, lt, gte, lte, contains Filterable fields: event, user_id, date, country, session_id, timestamp, and any properties.* field (e.g. properties.path) For customer-specific reads, use the top-level email input instead of hashing locally. Raw email is sent only in the authenticated HTTPS POST body; the server matches via a project-scoped HMAC index and does not store raw email in event rows or profile traits. Built-in fields are a closed list. Event properties such as referrer, utm_source, path, browser, and hostname must be queried as properties.referrer, properties.utm_source, properties.path, properties.browser, and properties.hostname. Invalid filter fields fail loudly and return /properties-style guidance instead of being silently ignored. Group by: event, date, user_id, session_id, country, and at most one properties.<key>. The key matches ^[A-Za-z0-9_]{1,128}$, the same rule as pr	No	Yes	Not declared	No
`sessions`List individual session records Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	List individual session records Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.	No	Yes	Not declared	No
`set_project_context`Set or replace compact project context. The encoded API request body is capped at 512KB. Read existing context first, merge still-valid entries, inspect event names with properties or properties_received, and save only durable product truth tied to goals, activation events, event-name glossary entries, or date annotations for major product changes. Use annotations for meaningful landing page, pricing, onboarding, feature, release, or experiment changes; do not store git commit logs, noisy edits, PII, secrets, or long release notes.	Set or replace compact project context. The encoded API request body is capped at 512KB. Read existing context first, merge still-valid entries, inspect event names with properties or properties_received, and save only durable product truth tied to goals, activation events, event-name glossary entries, or date annotations for major product changes. Use annotations for meaningful landing page, pricing, onboarding, feature, release, or experiment changes; do not store git commit logs, noisy edits, PII, secrets, or long release notes.	Yes	No	Not declared	No
`update_experiment`Update experiment status (pause, resume, complete)	Update experiment status (pause, resume, complete)	Yes	No	Not declared	No
`web_vitals`Read Core Web Vitals for a project (POST /vitals). p75 is the headline: each metric is assessed at the 75th percentile of page loads, using nearest-rank. Web Vitals is a Pro read. A free account gets 403 PRO_REQUIRED, the same status and error code as POST /query, and that rejection is not metered. Each successful call counts as one metered read. The event is fixed to page_view. On hosted, vitals are cwv_lcp, cwv_inp, cwv_cls, cwv_fcp, and cwv_ttfb properties on page_view. Collect them by installing the project snippet with data-track-vitals="true". Thresholds follow web.dev (https://web.dev/articles/vitals) and PageSpeed Insights. LCP: good at or below 2500 ms, poor above 4000 ms. INP: good at or below 200 ms, poor above 500 ms. CLS: good at or below 0.1, poor above 0.25 (unitless). FCP: good at or below 1800 ms, poor above 3000 ms. TTFB: good at or below 800 ms, poor above 1800 ms. A value at or below good_max is good. A value above poor_min is poor. Any value in between is needs-improvement. The same rule rates every page load for the good, needs-improvement, and poor share, and rates the p75. cwv_pass is true only when the LCP, INP, and CLS p75 ratings are all good. If INP n is 0, the decision uses LCP and CLS only. cwv_pass is null when LCP n is 0 or CLS n is 0. FCP and TTFB do not affect cwv_pass. group_by is optional. device returns mobile, tablet, and desktop. path returns the top limit paths by sample size, sorted by worst LCP p75. Omit group_by for one site-wide row (group null). limit defaults to 10 and maxes at 20. days, date_from, and date_to select the window. Each metric row includes p75 with its unit, rating, n, skipped, the good/needs-improvement/poor share, and up to 5 top poor targets. FCP and TTFB targets are empty. skipped counts page views that did not report that vital. When the scan hits the 200,000 event cap, approximate is true.	Read Core Web Vitals for a project (POST /vitals). p75 is the headline: each metric is assessed at the 75th percentile of page loads, using nearest-rank. Web Vitals is a Pro read. A free account gets 403 PRO_REQUIRED, the same status and error code as POST /query, and that rejection is not metered. Each successful call counts as one metered read. The event is fixed to page_view. On hosted, vitals are cwv_lcp, cwv_inp, cwv_cls, cwv_fcp, and cwv_ttfb properties on page_view. Collect them by installing the project snippet with data-track-vitals="true". Thresholds follow web.dev (https://web.dev/articles/vitals) and PageSpeed Insights. LCP: good at or below 2500 ms, poor above 4000 ms. INP: good at or below 200 ms, poor above 500 ms. CLS: good at or below 0.1, poor above 0.25 (unitless). FCP: good at or below 1800 ms, poor above 3000 ms. TTFB: good at or below 800 ms, poor above 1800 ms. A value at or below good_max is good. A value above poor_min is poor. Any value in between is needs-improvement. The same rule rates every page load for the good, needs-improvement, and poor share, and rates the p75. cwv_pass is true only when the LCP, INP, and CLS p75 ratings are all good. If INP n is 0, the decision uses LCP and CLS only. cwv_pass is null when LCP n is 0 or CLS n is 0. FCP and TTFB do not affect cwv_pass. group_by is optional. device returns mobile, tablet, and desktop. path returns the top limit paths by sample size, sorted by worst LCP p75. Omit group_by for one site-wide row (group null). limit defaults to 10 and maxes at 20. days, date_from, and date_to select the window. Each metric row includes p75 with its unit, rating, n, skipped, the good/needs-improvement/poor share, and up to 5 top poor targets. FCP and TTFB targets are empty. skipped counts page views that did not report that vital. When the scan hits the 200,000 event cap, approximate is true.	No	Yes	Not declared	No

Details

Registry status: Active
Published: Feb 22, 2026
Updated: Feb 22, 2026
Website: Not given
Repository: https://github.com/Agent-Analytics/agent-analytics-mcp⁠ (opens in a new tab)
Categories (suggested): Data and analyticsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing