AI Agent Analytics MCP Server

by davisvillelabs Your server? Claim it

answering

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

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

Uptime history 50 days of history · worst day 93%

50 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

243 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 16

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 September 2026. No other catalogue keeps this.

4 Oct a tool changed version

3 Oct 9 tools disappeared get_agents, get_attention_queue, get_connection_health and 6 more

3 Oct 2 tool descriptions were rewritten get_daily_pulse, list_products

3 Oct a tool changed the parameters it asks for get_daily_pulse

3 Oct a tool changed version

24 Sep a tool appeared get_attention_queue

22 Sep a tool description was rewritten validate_installation

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "ai-agent-analytics": {
      "type": "http",
      "url": "https://analytics.davisvillelabs.com/mcp"
    }
  }
}

Available tools 3

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

daily

get_daily_pulse

Return the customer's latest precomputed 24-hour Daily Pulse snapshot. Use this for the same bounded once-daily view shown in the customer dashboard. It does not run a historical event scan when called and takes no parameters because the organization comes from the authorization. Requires analytics:read; if the first 6 PM local snapshot has not been built yet, state is preparing.

products

list_products

List the active product in the bearer token's organization. Use this for setup and identity checks; use get_daily_pulse for the customer's current precomputed 24-hour snapshot. The current Founder plan supports one active product. 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.

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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_agents

removed 3 Oct 2026

get_attention_queue

removed 3 Oct 2026

get_connection_health

removed 3 Oct 2026

get_discovery

removed 3 Oct 2026

get_evidence

removed 3 Oct 2026

get_portfolio_pulse

removed 3 Oct 2026

get_report

removed 3 Oct 2026

get_revenue

removed 3 Oct 2026

validate_installation

removed 3 Oct 2026

Endpoints

URL	Transport	State	Latency	Checked
https://analytics.davisvillelabs.com/mcp	streamable-http	answering	142 ms	10 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 398 installs/wk local only

Flowsery

by flowsery

Web analytics for AI agents: realtime visitors, revenue, funnels and AI-detected site issues

27 tools answering

Talivia Revenue Analytics

by talivia-group

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

52 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

LopeBase

by lopebase

SEO, Search Console, analytics, revenue, and uptime for every site you run, from LopeBase.

439 installs/wk answering

MCP Pickaxe

by aplaceforallmystuff

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

63 installs/wk local only

AI Agent Analytics — questions

Answers built from our own checks of this server.

What can AI Agent Analytics do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_daily_pulse, list_products, scan_agent_commerce_readiness. 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 91 of 91 checks got a reply (100.0%), average response time 243 ms. The bar chart above shows every period we have measured.

Did AI Agent Analytics ever remove tools?

Yes. get_agents, get_attention_queue, get_connection_health, get_discovery and 5 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

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 in the form 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 3 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 243 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.