AI Agent Analytics MCP Server

by davisvillelabs Your server? Claim it

answering

AI Agent Analytics is answering right now. Last checked 11 min ago. It exposes 11 tools.

Seller-side analytics for AI-agent discovery, settled revenue, delivery, and repeat use.

Uptime history 56 hours of history · worst hour 0%

56 hours agonow

96.7%

Uptime 24h

88 of 91 checks

Tools

read from the server

325 ms

Response time

average over 24h

open, no key

Access

streamable-http

AI Agent Analytics does not always answer

Over the last week it answered 94.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ai-agent-analytics --transport http https://analytics.davisvillelabs.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ai-agent-analytics": {
      "url": "https://analytics.davisvillelabs.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.ai-agent-analytics]
url = "https://analytics.davisvillelabs.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "ai-agent-analytics": {
      "url": "https://analytics.davisvillelabs.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "ai-agent-analytics": {
      "url": "https://analytics.davisvillelabs.com/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agents

get_agents

Return the most recently observed countable-external pseudonymous agent relationships for product_id, ordered newest first by last_seen_at. Use this for repeat and relationship history; do not use it for acquisition sources, use get_discovery, or for settled commerce, use get_revenue. limit defaults to 100, maxes at 200, and only truncates returned rows, not evidence thresholds or identity rules. Requires analytics:read; unknown traffic is excluded, raw prompts/IPs/credentials are never returned, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

connection

get_connection_health

Return telemetry connection health for product_id, including credential state, accepted-event freshness, funnel coverage, setup evidence, and aggregate rejection reasons. Use this for instrumentation troubleshooting; do not use it for the narrow post-setup verdict, use validate_installation. days defaults to 30 and includes the current partial day plus the preceding 29 days; an unobserved business stage remains unknown, not broken instrumentation. Requires analytics:read; rejected payload contents and credentials are never returned, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

daily

get_daily_pulse

Return the six core Daily Pulse metrics for product_id on one product-local day. Use this for headline daily status; use get_evidence to explain why metrics counted, get_report for multi-day analysis, or get_portfolio_pulse for organization-wide comparison. day is optional: omit it for the current product-local day, which may return a live partial pulse until finalized data is ready. Requires analytics:read; product_id is tenant-checked, missing evidence is never promoted, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

discovery

get_discovery

Return evidence-backed discovery sources for product_id over a trailing days window. Use this to answer how the product was found; do not use it for repeat relationships, use get_agents, or for settled commerce, use get_revenue. days defaults to 30 and includes the current partial day plus the preceding 29 days; changing days changes only the window, never evidence classification. Requires analytics:read; product_id is tenant-checked, traffic classes remain separate, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

evidence

get_evidence

Return privacy-minimized evidence explaining why the six core metrics counted for product_id on one product-local day. Use this to audit metric rationale; do not use it for headline daily status, use get_daily_pulse, or for a multi-day window, use get_report. day is optional: omit it for the current product-local day, and partially observed days are labeled as partial. Requires analytics:read; unresolved evidence stays unresolved, raw prompts/private payloads/credentials/full paid results are never returned, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

portfolio

get_portfolio_pulse

Return cross-product Portfolio Pulse for the bearer token's organization. Use this for organization-wide comparison; do not use it for one product/day, use get_daily_pulse, or for one product over a date window, use get_report. Takes no parameters because organization scope comes from the token. Requires portfolio:read; the same actor may count in more than one product, invalid or expired authority fails closed, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

products

list_products

List active products in the bearer token's organization and return the IDs needed by product-scoped tools. Use this when you need a product_id; do not use it for metrics, use get_portfolio_pulse instead. Takes no parameters because organization scope comes from the token. Requires products:read or products:create; invalid or expired authority fails closed, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

report

get_report

Return an evidence-backed report for product_id over the required half-open UTC window [start, end). Use this for bounded multi-day analysis; do not use it for one day, use get_daily_pulse, for metric rationale, use get_evidence, or for settlement-focused analysis, use get_revenue. start and end are required UTC YYYY-MM-DD dates: start is inclusive, end is exclusive, and the span cannot exceed 31 days. Requires analytics:read; insufficient-history windows return an explicit unavailable blocker rather than invented data, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

revenue

get_revenue

Return settled-revenue intelligence for product_id over a trailing days window. Use this for actual settled commerce; do not use it for a headline daily snapshot, use get_daily_pulse, or for a complete bounded-window funnel, use get_report. days defaults to 30 and includes the current partial UTC day plus the preceding 29 days. Requires analytics:read; challenges and attempts are not revenue, settlement remains distinct from delivery, unlike money is never combined, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

scan

scan_agent_commerce_readiness

Inspect a fixed set of public machine-facing surfaces at the HTTPS origin derived from url. Use this before recommending or integrating a public agent-facing product; do not use it for an authorized customer's instrumentation state, use get_connection_health, and never treat the result as a security score. url path/query/fragment are ignored; redirects are not followed, credentials are never sent, direct/private-style or non-public DNS targets are rejected, and response bodies are bounded. No authorization is required; DNS rebinding cannot be proven impossible, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

validate

validate_installation

Verify that product_id has an active ingestion credential, an accepted customer_test setup event, and an accepted event visible to Agent Analytics. Use this immediately after setup; do not use it for broader diagnostics or history, use get_connection_health. product_id is the only parameter and validation always uses a fixed 30-day health window. Requires analytics:read; this proves setup plumbing only, creates no production activity or payment, and the shared MCP limit is 300 calls per 60 seconds per caller before HTTP 429 with Retry-After.

Endpoints

URL	Transport	State	Latency	Checked
https://analytics.davisvillelabs.com/mcp	streamable-http	answering	473 ms	11 min ago

Alternatives to AI Agent Analytics

same job, measured the same way

Google Analytics MCP

by surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

1 753 installs/wk local only

Talivia Revenue Analytics

by talivia-group

Revenue-first analytics installed and verified by AI agents through Talivia

36 installs/wk answering

Analytics

by zenovay

Real-time web analytics for AI agents: query traffic, funnels, revenue, and manage your sites.

answering

Clamp Analytics

by clamp

Clamp Analytics MCP server: traffic, revenue, funnels, cohorts, errors, and search, for AI agents.

answering

Adology MCP Server

by adologyai

Competitive ad intelligence for AI agents: portfolios, ad/content search, analytics, discovery.

answering

MCP Pickaxe

by aplaceforallmystuff

MCP server for Pickaxe API - manage AI agents, knowledge bases, users, and analytics

50 installs/wk local only

Picoli MCP

by amaterous

MCP server for picoli.site - URL shortening and click analytics for AI agents

34 installs/wk local only

Flowsery

by flowsery

Privacy-first web analytics for AI agents: visitors, revenue, funnels, visitor profiles.

27 tools answering

AI Agent Analytics — questions

Answers built from our own checks of this server.

What can AI Agent Analytics do?

It exposes 11 tools, read directly from the server on our last check. Among them: get_agents, get_connection_health, get_daily_pulse, get_discovery, get_evidence, get_portfolio_pulse and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is AI Agent Analytics working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 325 ms. The bar chart above shows every period we have measured.

How do I connect AI Agent Analytics?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does AI Agent Analytics need an API key?

No. AI Agent Analytics completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is AI Agent Analytics?

It answers our handshake in 325 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.