Home / MCP registry index / io.github.dannyshmueli/agent-analytics-mcp

Agent Analytics

io.github.dannyshmueli/agent-analytics-mcp in the official MCP registry. Endpoint https://mcp.agentanalytics.sh/mcp. Source: github.com/Agent-Analytics/agent-analytics-mcp.

The registry describes it as: Analytics your AI agent can actually use. Track, experiment, and optimize via MCP.

We read its 28 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http agent-analytics-mcp https://mcp.agentanalytics.sh/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "agent-analytics-mcp": {
      "url": "https://mcp.agentanalytics.sh/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"agent-analytics-mcp","type":"http","url":"https://mcp.agentanalytics.sh/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

account_usage analytics_panel list_projects create_project get_project_context set_project_context properties properties_received sessions list_experiments create_experiment get_experiment update_experiment delete_experiment live_now all_sites_overview bot_traffic_overview all_sites_bot_traffic query analytics_funnel analytics_retention analytics_overview analytics_insights analytics_breakdown analytics_pages analytics_paths analytics_sessions analytics_heatmap

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-dannyshmueli-agent-analytics-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-dannyshmueli-agent-analytics-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Analytics and SEO MCP servers

SendIt
io.github.Shree-git/sendit
148 tools, nothing matched
2026-10-29
Support Agent Admin by Nova (CIVAI)
co.civai.nova/support-agent-admin
93 tools, nothing matched
2026-10-22
EventTrader Research (read-only)
com.cymetica/event-trader-research
82 tools, nothing matched
2026-10-27
com.validoria/validoria-mcp
com.validoria/validoria-mcp
78 tools, nothing matched
2026-10-27
io.github.tdobrowolski1/flashalpha
io.github.tdobrowolski1/flashalpha
78 tools, nothing matched
2026-10-22
io.github.webberdesign/webbersites-x402-data-api
io.github.webberdesign/webbersites-x402-data-api
78 tools, nothing matched
2026-10-22