Skip to content

AI Agent Analytics MCP server

io.github.davisvillelabs/ai-agent-analyticsdavisvillelabsstreamable-httpv1.0.0Scanned

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

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • 2 findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the AI Agent Analytics MCP server can do

The AI Agent Analytics MCP server is published by the GitHub account davisvillelabs. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool brings in text other people can write (scan_agent_commerce_readiness); 1 tool can send data out of your system (scan_agent_commerce_readiness).

The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.

Last scanned Nov 6, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Only reads 3Show 3 read-only tools
  • get_daily_pulseReturn the customer's latest precomputed 24-hour Daily Pulse snapshot.No findings

    Why it is in this group

    • The name "get_daily_pulse" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_productsList the active product in the bearer token's organization.No findings

    Why it is in this group

    • The name "list_products" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • scan_agent_commerce_readinessInspect a fixed set of public machine-facing surfaces at the HTTPS origin derived from url.Reads text others writeCan send data out2 findings

    Why it is in this group

    • The description's first verb is "inspect": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "inspect" and "http": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...re ignored; redirects are not followed, credentials are never sent, direct/private-style or..."

      What this check looks for
    • Info

      The input schema at properties.url.description mentions "credentials".

      Matched text

      inputSchema.properties.url.description: "...ent are ignored. Custom ports, embedded credentials, IP literals, localhost/private-style h..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: analytics.davisvillelabs.com does not resolve.

Posture changes

  1. Nov 20, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://analytics.davisvillelabs.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://analytics.davisvillelabs.com to none
    • Dynamic client registration: no to not observed
    • Client ID metadata documents: yes to not observed

Findings

Matches of fixed checks, with the text they matched.

2 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 5 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://analytics.davisvillelabs.com/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://analytics.davisvillelabs.com to none
    • Dynamic client registration: no to not observed
    • Client ID metadata documents: yes to not observed

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ai-agent-analytics__list_products",
      "mcp__ai-agent-analytics__get_daily_pulse"
    ],
    "ask": [
      "mcp__ai-agent-analytics__scan_agent_commerce_readiness"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ai-agent-analytics. Review it before you use it.

Capability tags behind 1 rule
  • mcp__ai-agent-analytics__scan_agent_commerce_readiness untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.davisvillelabs/ai-agent-analytics/verify?hash=6d24e1702932f936aed8879484f4f82808972d0210dd7d3eb13a2aa8824d9080" | jq -e '.changed == false'

Pinned hash 6d24e1702932, from Nov 6, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.davisvillelabs/ai-agent-analytics/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.davisvillelabs/ai-agent-analytics
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.davisvillelabs/ai-agent-analytics.svg)](https://radar.anlyon.com/servers/io.github.davisvillelabs/ai-agent-analytics)

Source: MCP Registry. Synced Oct 21, 2026, 18:31 UTC.

AI Agent Analytics MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AI Agent Analytics MCP server safe?

No scan can promise that. What its definitions show: 3 tools, all of which only read, and 2 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the AI Agent Analytics MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AI Agent Analytics MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AI Agent Analytics MCP server have?

3 tools: 3 read. list_products, get_daily_pulse and scan_agent_commerce_readiness.

Does the AI Agent Analytics MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the AI Agent Analytics MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_agent_commerce_readiness.

Has the AI Agent Analytics MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 6, 2026.