Skip to content

Agent Analytics MCP server

io.github.dannyshmueli/agent-analytics-mcpdannyshmuelistreamable-httpv1.0.0Scanned

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

32 tools: 3 can delete or cancel things, 19 change things and 10 only read.

Tools: 3 delete, 0 irreversible, 19 write, 10 read.
  • Reads private data · 1
  • Reads text others write · 2
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Agent Analytics MCP server can do

The Agent Analytics MCP server is published by the GitHub account dannyshmueli. It has 32 tools. It can delete or cancel things (3 tools: set_project_context, update_experiment and delete_experiment) and create or change data (19 tools: analytics_panel, create_project, append_project_annotation, properties and 15 more). 10 tools only read.

1 tool reads private data (query); 2 tools bring in text other people can write (query and web_vitals).

The fixed checks matched 3 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.0.0.

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.

32 tools

Deletes or cancels 3Claude Code: deny
  • delete_experimentDelete an experimentNo findings

    Why it is in this group

    • The name "delete_experiment" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete an experiment

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • set_project_contextSet or replace compact project context.No findings

    Why it is in this group

    • The name "set_project_context" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
  • update_experimentUpdate experiment status (pause, resume, complete)No findings

    Why it is in this group

    • The name "update_experiment" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update experiment status (pause, resume, complete)

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Changes things 19Claude Code: ask
  • all_sites_bot_trafficFiltered automated traffic across all active projects in your account.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
    Filtered automated traffic across all active projects in your account.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • all_sites_overviewHistorical summary across all projects in your account: total events, active project count, daily trend, and top projects.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
    Historical summary across all projects in your account: total events, active project count, daily trend, and top projects.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • analytics_breakdownTop 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 project…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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • analytics_funnelFunnel analysis: track where users drop off across a sequence of events (e.g.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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • analytics_heatmapDay-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 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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • analytics_insightsPeriod-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 yo…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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • analytics_pagesEntry/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 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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • analytics_panelUse this when you want to explore an authorized project's analytics beside the conversation.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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • analytics_pathsBounded session path analysis from entry pages to goal, drop-off, or truncation.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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • analytics_retentionCohort retention analysis — track what % of users return over time.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 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • analytics_sessionsSession 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 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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • append_project_annotationAppend one annotation to project context.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.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • bot_traffic_overviewFiltered automated traffic for a single project: automated requests, dropped events, categories, and top actors.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
    Filtered automated traffic for a single project: automated requests, dropped events, categories, and top actors.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • create_experimentCreate an A/B experimentNo findings

    Why it is in this group

    • The name "create_experiment" says "create": a word for a change.
    Description, as the server wrote it
    Create an A/B experiment

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • create_projectCreate a new Agent Analytics project.No findings

    Why it is in this group

    • The name "create_project" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • live_nowReal-time snapshot: active visitors, sessions, events per minute, top pages, and recent events.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
    Real-time snapshot: active visitors, sessions, events per minute, top pages, and recent events. Reads from in-memory ring buffer — no D1 query.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • propertiesDiscover 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 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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • properties_receivedProperty 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 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
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • queryRun a flexible ad-hoc analytics query with custom metrics, filters, grouping, date ranges, and privacy-first customer email lookup.Reads private dataReads text others write2 findings

    Why it is in this group

    • The name "query" says "query": a word for reading.
    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "run" and "email": it reads inbound email, which other people can write.

    Findings

    • Info

      The description is 3,776 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...s fall back to event id. count_mode is ignored when event_count is not requested."

      What this check looks for
    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "query" says "query": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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 property filters. Result rows use the column name properties.<key>. A null or missing property value is grouped as null. Two properties.* entries return 400 INVALID_GROUP_BY. Metrics: event_count, unique_users, session_count, bounce_rate, avg_duration, sum, avg, p50, p75, p95 Numeric property metrics sum, avg, p50, p75, and p95 are Pro, with the same gating as this query. A free account gets 403 PRO_REQUIRED and that rejection is not metered. property is the event property key and is required when any of those metrics is requested. On hosted, cwv_lcp, cwv_inp, cwv_cls, cwv_fcp, and cwv_ttfb are properties on page_view when the tracker snippet includes data-track-vitals="true". Use the web_vitals tool for the p75 headline, ratings, and good/needs-improvement/poor shares. For an ad-hoc query, filter event to page_view. property must match ^[A-Za-z0-9_]+$ and be at most 128 characters. Missing property is 400 MISSING_FIELDS. An invalid key is 400 INVALID_PROPERTY_KEY. Only JSON numbers are aggregated. Numeric strings, booleans, nulls, and missing keys are skipped. Each row includes the requested metrics plus n (numeric values used) and skipped whenever an aggregation metric is requested. Percentiles are nearest-rank: percentile_method is nearest_rank when a percentile is requested and null for sum or avg only. avg is rounded to 6 decimal places. order_by may be a requested aggregate, for example p75. Count modes: raw, session_then_user. The default for event_count is session_then_user for activation-safe counting: session-backed rows count by session, no-session rows fall back to user only when that user has no session-backed row in the same group, and fully anonymous rows fall back to event id. count_mode is ignored when event_count is not requested.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 10Show 10 read-only tools
  • account_usageRead current account plan, usage, billing estimate and spend cap, Pro pricing, and a human payment handoff when needed.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • analytics_overviewGet 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 re…No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • compareCompare a shipped change and return a keep, revert, or extend verdict.1 finding

    Why it is in this group

    • The name "compare" says "compare": a word for reading.

    Findings

    • Info

      The description is 5,070 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...d, including the Newcombe interval. Compare stays a free read when metric is set."

      What this check looks for
    Description, as the server wrote it
    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 when lift is at or below revert_threshold and the 90% interval lies entirely below zero; extend inconclusive when the drop is within noise; keep keep_threshold_met when lift is at or above keep_threshold and interval.low is above 0; extend interval_includes_zero; extend no_evidence_of_gain. A drop by itself is not a revert. Each window reports date_from, date_to, day_count, denominator_unique_users, goal_unique_users, goal_converters, goal_users_outside_denominator, count_mode, and rate. The response also includes count_mode, reason_detail, lift, echoed denominator_filters, and a 90% interval (level, method newcombe_wilson_90, estimate rate_difference, low, high, excludes_zero, note). Optional metric compares a numeric property. metric is sum(<property>), avg(<property>), p50(<property>), p75(<property>), or p95(<property>), for example sum(revenue) or p75(cwv_lcp). The property uses the query property allowlist ^[A-Za-z0-9_]+$ with a maximum of 128 characters. Example: metric p75(cwv_lcp), metric_event page_view, better lower, while goal_event stays signup. On hosted, cwv_* vitals are properties on page_view. Prefer the web_vitals tool for the p75 headline, ratings, and shares. metric_event is the event whose property is measured and defaults to goal_event. Set it when the measured event is not the goal. better is higher (default) or lower and is not inferred from the property name. Use better=lower for cwv_lcp and the other Web Vitals. Shared filters apply to the metric event. denominator_filters still apply only to the denominator. sum() compares the sum divided by unique denominator users (per_user true). avg and percentiles compare the aggregate itself (per_user false). Percentiles are nearest-rank, so percentile_method is nearest_rank. With metric set, interval is null and interval_method is none. There is no bootstrap interval in v1. lift is (compare - baseline) / baseline, negated when better is lower, so the existing thresholds keep their meaning. raw_lift is the unnegated ratio. min_denominator is still unique denominator users per window. When metric is set, min_goal_events is numeric values (n) on metric_event across both windows, not unique converters. below_min_sample is extend when n across both windows is under min_goal_events (default 20) or either window is under min_denominator (default 200). incomplete_current_day, below_min_sample, zero_denominator, and zero_baseline stay in that order. A missing compare value, or a baseline of 0 or null, is zero_baseline with lift null. When lift meets keep_threshold or revert_threshold, the verdict is extend with reason no_interval_for_metric, and lift is still reported. Lift between the thresholds is extend / no_evidence_of_gain. The response metric object includes metric, fn, property, metric_event, better, per_user, and percentile_method. Each window still includes the conversion rate and user counts, plus value, n, and skipped. Omit metric and the compare response is unchanged, including the Newcombe interval. Compare stays a free read when metric is set.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • errorsRead grouped $error events for a project (GET /errors).No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_experimentGet experiment details with results Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.No findings

    Why it is in this group

    • The name "get_experiment" says "get": a word for reading.
    Description, as the server wrote it
    Get experiment details with results Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_project_contextGet compact self-improving project context: goals, activation events, event-name glossary, and major date annotations used to interpret analytics results.No findings

    Why it is in this group

    • The name "get_project_context" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_experimentsList A/B experiments for a project Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.No findings

    Why it is in this group

    • The name "list_experiments" says "list": a word for reading.
    Description, as the server wrote it
    List A/B experiments for a project Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_projectsList all your Agent Analytics projects Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    List all your Agent Analytics projects Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • sessionsList individual session records Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.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 individual session records Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • web_vitalsRead Core Web Vitals for a project (POST /vitals).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe name "web_vitals" says "web": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "read" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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.

Tools listed without sign-in

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

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
22
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.agentanalytics.sh/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.agentanalytics.sh
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 22 tools that change things (3 destructive, 19 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.agentanalytics.sh/mcp: tools/list returned 32 tools to an anonymous client, including set_project_context (destructive), update_experiment (destructive), delete_experiment (destructive), analytics_panel (write), create_project (write) and 17 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • RFC 9728 protected resource metadata: https://mcp.agentanalytics.sh/.well-known/oauth-protected-resource to https://mcp.agentanalytics.sh/.well-known/oauth-protected-resource/mcp
    • Client ID metadata documents: no to yes
  2. Nov 13, 2026
    • Tools that change things, listed without credentials: 21 to 22

Findings

Matches of fixed checks, with the text they matched.

1 warn2 info
  • Warnquery

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

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "query" says "query": a word for reading.

    What this check looks for
  • Infoquery

    The description is 3,776 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...s fall back to event id. count_mode is ignored when event_count is not requested."

    What this check looks for
  • The description is 5,070 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...d, including the Newcombe interval. Compare stays a free read when metric is set."

    What this check looks for

History

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

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.agentanalytics.sh/.well-known/oauth-protected-resource -> https://mcp.agentanalytics.sh/.well-known/oauth-protected-resource/mcp; Client ID metadata documents: no -> …View diff
    • RFC 9728 protected resource metadata: https://mcp.agentanalytics.sh/.well-known/oauth-protected-resource to https://mcp.agentanalytics.sh/.well-known/oauth-protected-resource/mcp
    • Client ID metadata documents: no to yes
  2. Tools4 added, 2 changed.+4 added~2 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 21 -> 22.View diff
    • Tools that change things, listed without credentials: 21 to 22

Install

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

claude mcp add --transport http agent-analytics https://mcp.agentanalytics.sh/mcp
claude mcp add --transport http agent-analytics https://mcp.agentanalytics.sh/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__agent-analytics__account_usage",
      "mcp__agent-analytics__list_projects",
      "mcp__agent-analytics__get_project_context",
      "mcp__agent-analytics__sessions",
      "mcp__agent-analytics__list_experiments",
      "mcp__agent-analytics__get_experiment",
      "mcp__agent-analytics__compare",
      "mcp__agent-analytics__errors",
      "mcp__agent-analytics__web_vitals",
      "mcp__agent-analytics__analytics_overview"
    ],
    "ask": [
      "mcp__agent-analytics__analytics_panel",
      "mcp__agent-analytics__create_project",
      "mcp__agent-analytics__append_project_annotation",
      "mcp__agent-analytics__properties",
      "mcp__agent-analytics__properties_received",
      "mcp__agent-analytics__create_experiment",
      "mcp__agent-analytics__live_now",
      "mcp__agent-analytics__all_sites_overview",
      "mcp__agent-analytics__bot_traffic_overview",
      "mcp__agent-analytics__all_sites_bot_traffic",
      "mcp__agent-analytics__query",
      "mcp__agent-analytics__analytics_funnel",
      "mcp__agent-analytics__analytics_retention",
      "mcp__agent-analytics__analytics_insights",
      "mcp__agent-analytics__analytics_breakdown",
      "mcp__agent-analytics__analytics_pages",
      "mcp__agent-analytics__analytics_paths",
      "mcp__agent-analytics__analytics_sessions",
      "mcp__agent-analytics__analytics_heatmap"
    ],
    "deny": [
      "mcp__agent-analytics__set_project_context",
      "mcp__agent-analytics__update_experiment",
      "mcp__agent-analytics__delete_experiment"
    ]
  }
}

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 agent-analytics. Review it before you use it.

Capability tags behind 2 rules
  • mcp__agent-analytics__query private-data, untrusted-input
  • mcp__agent-analytics__web_vitals 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.github.dannyshmueli/agent-analytics-mcp/verify?hash=746c7341c4abab550e9de277ad3de01032bf1c652bcbb0fcaff76707d7d07239" | jq -e '.changed == false'

Pinned hash 746c7341c4ab, from Nov 16, 2026, 15:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.dannyshmueli/agent-analytics-mcp/changes.xml

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

Badge

Anlyon Radar badge for io.github.dannyshmueli/agent-analytics-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.dannyshmueli/agent-analytics-mcp.svg)](https://radar.anlyon.com/servers/io.github.dannyshmueli/agent-analytics-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:29 UTC.

Agent Analytics MCP server: questions and answers

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

Is the Agent Analytics MCP server safe?

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

Can the Agent Analytics MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: set_project_context, update_experiment and delete_experiment.

Can the Agent Analytics MCP server 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 Agent Analytics MCP server have?

32 tools: 3 destructive, 19 write, 10 read. set_project_context, update_experiment, delete_experiment, analytics_panel, create_project, append_project_annotation, properties, properties_received and 24 more.

Does the Agent Analytics MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Agent Analytics MCP server send data to outside services?

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

Has the Agent Analytics MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.