AI Agent Analytics
io.github.davisvillelabs/ai-agent-analyticsVersion 1.0.0Seller-side analytics for AI-agent discovery, settled revenue, delivery, and repeat use.
Status
Responds375 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:49 UTC
- Latency
- 375 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://analytics.davisvillelabs.com/mcpResponds375 msNo sign-in
Claude Code
claude mcp add --transport http ai-agent-analytics https://analytics.davisvillelabs.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: ai-agent-analytics
Remote MCP server URL: https://analytics.davisvillelabs.com/mcpCursor
{
"mcpServers": {
"ai-agent-analytics": {
"url": "https://analytics.davisvillelabs.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"ai-agent-analytics","type":"http","url":"https://analytics.davisvillelabs.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
get_daily_pulseReturn 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. | No | Yes | Yes | No |
list_productsList 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. | No | Yes | Yes | No |
scan_agent_commerce_readinessInspect 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. | No | Yes | Yes | Yes |
Details
- Registry status
- Active
- Published
- Sep 19, 2026
- Updated
- Sep 19, 2026
- Repository
- Not given
- Categories (suggested)
- E-commerceData and analyticsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared