AI Agent Analytics
REMOTE · ANALYTICS.DAVISVILLELABS.COM · SCANNED OCT 12
Seller-side analytics for AI-agent discovery, settled revenue, delivery, and repeat use.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 371 tokens (~123/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 23 days we've observed: 8 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the AI Agent Analytics MCP server?
AI Agent Analytics is a hosted endpoint at https://analytics.davisvillelabs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · analytics.davisvillelabs.com
claude mcp add --transport http davisvillelabs-ai-agent-analytics 'https://analytics.davisvillelabs.com/mcp'
{
"mcpServers": {
"davisvillelabs-ai-agent-analytics": {
"url": "https://analytics.davisvillelabs.com/mcp"
}
}
} {
"servers": {
"davisvillelabs-ai-agent-analytics": {
"type": "http",
"url": "https://analytics.davisvillelabs.com/mcp"
}
}
} [mcp_servers.davisvillelabs-ai-agent-analytics] url = "https://analytics.davisvillelabs.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"davisvillelabs-ai-agent-analytics": {
"type": "remote",
"url": "https://analytics.davisvillelabs.com/mcp",
"enabled": true
}
}
} openclaw mcp add davisvillelabs-ai-agent-analytics --url 'https://analytics.davisvillelabs.com/mcp' --transport streamable-http
mcp_servers:
davisvillelabs-ai-agent-analytics:
url: "https://analytics.davisvillelabs.com/mcp" {
"McpServers": {
"davisvillelabs-ai-agent-analytics": {
"Transport": "http",
"Url": "https://analytics.davisvillelabs.com/mcp"
}
}
} assistant mcp add davisvillelabs-ai-agent-analytics -t streamable-http -u 'https://analytics.davisvillelabs.com/mcp'
{
"mcpServers": {
"davisvillelabs-ai-agent-analytics": {
"type": "http",
"url": "https://analytics.davisvillelabs.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 0
- Server version: 1.0.1 → 1.0.2 functional
- 3 Oct 26 −3
- Tool “get_agents” was removed ▼ security
- Tool “get_attention_queue” was removed ▼ security
- Tool “get_connection_health” was removed ▼ security
- Tool “get_discovery” was removed ▼ security
- Tool “get_evidence” was removed ▼ security
- Tool “get_portfolio_pulse” was removed ▼ security
- Tool “get_report” was removed ▼ security
- Tool “get_revenue” was removed ▼ security
- Tool “validate_installation” was removed ▼ security
- Tool “get_daily_pulse” rewrote its description, which is the text the model reads security
- Tool “list_products” rewrote its description, which is the text the model reads security
- “get_daily_pulse” dropped the required parameter “product_id” ▼ functional
- Schema quality: fail → pass ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- “get_daily_pulse” dropped the optional parameter “day” cosmetic
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 28 to 31.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 14 to 18.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- New tool “get_attention_queue” functional
- 23 Sept 26 0
- Tool “validate_installation” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 12 Oct 2026 · Probed https://analytics.davisvillelabs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=davisvillelabs.com | CN=WE1,O=Google Trust Services,C=US | 16 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4871ed46f19e5ab60e8c279422324c31 |
| SANs: davisvillelabs.com, analytics.davisvillelabs.com, *.analytics.davisvillelabs.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of analytics.davisvillelabs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| davisvillelabs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://analytics.davisvillelabs.com/mcp | Verified | 200 | |
| http (plaintext) | http://analytics.davisvillelabs.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_daily_pulse Get Daily Pulse ~84
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| history_scan_on_read | boolean | yes | – |
| organization | object | yes | – |
| schema | string | yes | Delegated Daily Pulse response schema. |
| snapshot | – | yes | – |
| source | string | yes | – |
| state | string | yes | Whether a precomputed Daily Pulse snapshot is available. |
No examples provided.
list_products List analytics products ~91
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | Active products visible to this authorization. |
| schema | string | yes | Response schema identifier. |
No examples provided.
scan_agent_commerce_readiness Scan public agent-commerce readiness ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Any public HTTPS URL on the product host. Only its scheme and host are used; path, query, and fragment are ignored. Custom ports, embedded credentials, IP literals, localhost/private-style hostnames,… |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | Results for the fixed public surfaces; no user-supplied paths are fetched. |
| gaps | array | yes | Evidence-based follow-up gaps; absence is not proof a capability does not exist. |
| integrity | object | yes | Scanner safety properties and explicit limitations. |
| observed_at | string | yes | UTC scan timestamp. |
| schema | string | yes | Readiness-scan schema identifier. |
| summary | object | yes | – |
| target | object | yes | – |
No examples provided.
What is the AI Agent Analytics MCP server?
AI Agent Analytics is an MCP server listed in the public MCP registry as io.github.davisvillelabs/ai-agent-analytics. Seller-side analytics for AI-agent discovery, settled revenue, delivery, and repeat use. This page covers its hosted endpoint (https://analytics.davisvillelabs.com/mcp).
Is the AI Agent Analytics MCP server safe to use?
AI Agent Analytics scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI Agent Analytics MCP server expose?
AI Agent Analytics exposes 3 tools: list_products, get_daily_pulse, scan_agent_commerce_readiness. Their descriptions and schemas cost roughly 371 tokens of context every time the server is loaded.
Does the AI Agent Analytics MCP server require authentication?
No. We connected to AI Agent Analytics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Agent Analytics MCP server still maintained?
AI Agent Analytics is still listed as active in the MCP registry. We last reached this channel on 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.