Agent Analytics
REMOTE · MCP.AGENTANALYTICS.SH
Analytics your AI agent can actually use. Track, experiment, and optimize via MCP.
Available components
Last scanned (20 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Data and Analytics
Recent critical change
Authorization (4 Oct 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (set_project_context). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 6832 tokens (~93/item across 73 items; 32 tools + 41 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Nov 26 0
- Tool “query” rewrote its description, which is the text the model reads security
- “query” reworded the description of “group_by” cosmetic
- 13 Nov 26 0
- Tool “create_project” rewrote its description, which is the text the model reads security
- Tool “query” rewrote its description, which is the text the model reads security
- Schema quality: 47 → 91 ▼ functional
- New tool “append_project_annotation” functional
- New tool “compare” functional
- New tool “errors” functional
- New tool “web_vitals” functional
- “query” added an optional parameter “property” cosmetic
- “query” reworded the description of “metrics” cosmetic
- “query” reworded the description of “order_by” cosmetic
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://mcp.agentanalytics.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentanalytics.sh | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8e181847a91ee3cf134ee0d4ff93d3e7 |
| SANs: agentanalytics.sh, mcp.agentanalytics.sh | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.agentanalytics.sh. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | DS published | 34349 | 8 | Verified |
| agentanalytics.sh. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agentanalytics.sh/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.agentanalytics.sh/mcp | HTTPS enforced | 301 | https://mcp.agentanalytics.sh/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_usage ~62
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
all_sites_bot_traffic ~43
Filtered automated traffic across all active projects in your account.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max projects to include |
| period | string | – | Comparison period |
No output schema declared.
No examples provided.
all_sites_overview ~58
Historical summary across all projects in your account: total events, active project count, daily trend, and top projects.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max projects to include in the top-project list |
| period | string | – | Comparison period |
No output schema declared.
No examples provided.
analytics_breakdown ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window in days |
| event | string | – | Filter by event name (e.g. page_view) |
| limit | number | – | Max results |
| project | string | yes | Project name |
| property | string | – | Property key to group by (e.g. path, referrer, utm_source) |
No output schema declared.
No examples provided.
analytics_funnel ~212
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.
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | string | – | Property key to segment by (e.g. 'variant', 'country'). Extracted from step 1 events. |
| breakdown_limit | number | – | Max breakdown groups (default 10, max 50) |
| conversion_window_hours | number | – | Max hours from step 1 to last step (default: 168 = 7 days) |
| count_by | string | – | Count by users or sessions |
| project | string | yes | Project name |
| since | string | – | Lookback period (e.g. '30d', '90d', or ISO date) |
| steps | array | yes | Funnel steps (2-8), each with an event name and optional filters |
No output schema declared.
No examples provided.
analytics_heatmap ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
analytics_insights ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | – | Comparison period |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
analytics_overview ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window in days |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
analytics_pages ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results |
| project | string | yes | Project name |
| type | string | – | Page type |
No output schema declared.
No examples provided.
analytics_panel Analytics explorer ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
analytics_paths ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_session_cap | integer | – | Bound on candidate sessions scanned |
| entry_limit | integer | – | Max entry pages to include |
| goal_event | string | yes | Goal event to attribute within the same session |
| max_steps | integer | – | Max mixed page/event steps before truncation |
| path_limit | integer | – | Max children kept per node |
| project | string | yes | Project name |
| since | string | – | Lookback period |
No output schema declared.
No examples provided.
analytics_retention ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cohorts | number | – | Number of cohort periods (max: day=30, week=12, month=12) |
| event | string | – | First-seen event filter (e.g. signup). Switches to event-based retention. |
| period | string | – | Cohort grouping period |
| project | string | yes | Project name |
| returning_event | string | – | What counts as 'returned' (defaults to same as event) |
No output schema declared.
No examples provided.
analytics_sessions ~46
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
append_project_annotation ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional short note, max 500 characters |
| occurred_at | string | yes | ISO-8601 timestamp when the major product change happened |
| project | string | yes | Project name or ID |
| title | string | yes | Short annotation title, max 120 characters |
No output schema declared.
No examples provided.
bot_traffic_overview ~61
Filtered automated traffic for a single project: automated requests, dropped events, categories, and top actors.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max actors to include |
| period | string | – | Comparison period |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
compare ~1,537
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…
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | object | – | Explicit baseline window. Pass with compare, and omit ship_date and window_days |
| better | string | – | Which direction is an improvement. Defaults to higher and is not inferred from the property name. Use better=lower for cwv_lcp and the other Web Vitals |
| compare | object | – | Explicit compare window. Pass with baseline, and omit ship_date and window_days |
| denominator_event | string | – | Denominator event counted as unique users. Defaults to page_view. rate = goal_converters / denominator_unique_users |
| denominator_filters | array | – | Filters applied only to denominator events when counting denominator_unique_users. Same shape and operators as filters. Max 10. Omit or pass [] for today's behavior. Example: {"field":"properties.tit… |
| filters | array | – | Optional filters, same shape as query. Do not filter on event |
| goal_event | string | yes | Goal event counted as unique converters (count_mode unique_users). A user who fires it more than once counts once |
| metric | string | – | Numeric property metric, for example p75(cwv_lcp) or sum(revenue). One of sum, avg, p50, p75, p95. Omit to keep the conversion-rate compare |
| metric_event | string | – | Event whose property is measured. Defaults to goal_event. For hosted Web Vitals such as p75(cwv_lcp), set this to page_view |
| project | string | yes | Project name or ID |
| rule | object | – | Decision rule. Omitted fields use the documented day-7 examples, not product policy. Threshold absolute values above 5 are rejected |
| ship_date | string | – | Ship date (YYYY-MM-DD, UTC). The ship day is in neither window |
| window_days | integer | – | Days in each ship_date window. Integer from 1 to 90 and a multiple of 7. Defaults to 7. Omit when passing baseline and compare |
No output schema declared.
No examples provided.
create_experiment ~85
Create an A/B experiment
| Name | Type | Req | Description |
|---|---|---|---|
| goal_event | string | yes | Goal event name to measure conversions |
| name | string | yes | Experiment name |
| project | string | yes | Project name |
| variants | array | yes | Variant keys, e.g. ['control', 'new_cta'] |
| weights | array | – | Variant weights, e.g. [50, 50] |
No output schema declared.
No examples provided.
create_project ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_origins | string | – | Allowed CORS origins, defaults to * |
| name | string | yes | Project name (letters, numbers, hyphens, dots, max 64 chars) |
No output schema declared.
No examples provided.
delete_experiment ~22
Delete an experiment
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Experiment ID |
No output schema declared.
No examples provided.
errors ~521
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max groups. Defaults to 20 and maxes at 100 |
| new_since | string | – | YYYY-MM-DD or an annotation title. Zero matches is 400. More than one match is 400 with matches of occurred_at and title |
| project | string | yes | Project name or ID |
| since | string | – | Lookback window: 7d or YYYY-MM-DD. Defaults to 7 days |
| until | string | – | Inclusive end date YYYY-MM-DD. Defaults to today UTC |
No output schema declared.
No examples provided.
get_experiment ~43
Get experiment details with results Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Experiment ID |
No output schema declared.
No examples provided.
get_project_context ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name or ID |
No output schema declared.
No examples provided.
list_experiments ~46
List A/B experiments for a project Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
No output schema declared.
No examples provided.
list_projects ~34
List all your Agent Analytics projects Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
live_now ~68
Real-time snapshot: active visitors, sessions, events per minute, top pages, and recent events. Reads from in-memory ring buffer — no D1 query.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
| window | number | – | Time window in seconds (10-300, default 60) |
No output schema declared.
No examples provided.
properties ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Lookback window in days |
| project | string | yes | Project name |
No output schema declared.
No examples provided.
properties_received ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name |
| sample | number | – | Events to sample |
| since | string | – | Start date (ISO or shorthand like 7d) |
No output schema declared.
No examples provided.
query ~1,312
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 p…
| Name | Type | Req | Description |
|---|---|---|---|
| count_mode | string | – | How event_count is aggregated. Default for event_count: session_then_user. Session-backed rows count by session, no-session rows fall back to user only when that user has no session-backed row in the… |
| date_from | string | – | Start date (ISO 8601 or Nd shorthand like '30d'). Defaults to 7 days ago. |
| date_to | string | – | End date (ISO 8601). Defaults to today. |
| string | – | Filter by server-side scoped HMAC email lookup. Raw email is sent only in the authenticated HTTPS POST body and is not stored in event rows or profile traits. | |
| filters | array | – | Filters to apply |
| group_by | array | – | Fields to group by. Each item is event, date, user_id, session_id, country, or properties.<key>. The key matches ^[A-Za-z0-9_]{1,128}$. At most one properties.<key>. The result column is properties.<… |
| limit | number | – | Max results (default 100, max 1000) |
| metrics | array | – | Metrics to compute. sum, avg, p50, p75, and p95 require property |
| order | string | – | Sort direction |
| order_by | string | – | Field to sort by. Aggregate metrics such as p75 are allowed when requested |
| project | string | yes | Project name |
| property | string | – | Event property key to aggregate, for example cwv_lcp or revenue. Required when metrics include sum, avg, p50, p75, or p95. Must match ^[A-Za-z0-9_]+$ and be at most 128 characters |
No output schema declared.
No examples provided.
sessions ~58
List individual session records Anonymous preview is limited to agentanalytics-demo synthetic read-only data; sign in for your own projects.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results |
| project | string | yes | Project name |
| since | string | – | Start date |
No output schema declared.
No examples provided.
set_project_context ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| activation_events | array | – | Event names that define activation, max 8 |
| annotations | array | – | Major date annotations, max 100 |
| glossary | array | – | Event-name glossary entries, max 10 |
| goals | array | – | Short business goals, max 5 |
| project | string | yes | Project name or ID |
No output schema declared.
No examples provided.
update_experiment ~49
Update experiment status (pause, resume, complete)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Experiment ID |
| status | string | yes | New status |
| winner | string | – | Winning variant (for completing) |
No output schema declared.
No examples provided.
web_vitals ~648
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Inclusive start date (YYYY-MM-DD). Optional |
| date_to | string | – | Inclusive end date (YYYY-MM-DD). Optional |
| days | integer | – | Lookback in days. Omit when date_from and date_to are set |
| group_by | string | – | Split rows by device (mobile, tablet, desktop) or path. Omit for one site-wide row |
| limit | integer | – | Maximum rows. Defaults to 10 and maxes at 20 |
| project | string | yes | Project name or ID |
No output schema declared.
No examples provided.
How do I install the Agent Analytics MCP server?
Agent Analytics is a hosted endpoint at https://mcp.agentanalytics.sh/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.agentanalytics.sh
claude mcp add --transport http dannyshmueli-agent-analytics-mcp 'https://mcp.agentanalytics.sh/mcp'
What is the Agent Analytics MCP server?
Agent Analytics is an MCP server listed in the public MCP registry as io.github.dannyshmueli/agent-analytics-mcp. Analytics your AI agent can actually use. Track, experiment, and optimize via MCP. This page covers its hosted endpoint (https://mcp.agentanalytics.sh/mcp).
Is the Agent Analytics MCP server safe to use?
Agent Analytics scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Analytics MCP server expose?
Agent Analytics exposes 32 tools: account_usage, analytics_panel, list_projects, create_project, get_project_context, and 27 more. Their descriptions and schemas cost roughly 6,344 tokens of context every time the server is loaded.
Does the Agent Analytics MCP server require authentication?
No. We connected to Agent Analytics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Analytics MCP server still maintained?
Agent Analytics is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Agent Analytics MCP server?
VerifyMCP ran 14 checks on Agent Analytics, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.