io.github.joepangallo/mcp-server-agent-analytics
NPM · MCP-SERVER-AGENT-ANALYTICS · SCANNED SEP 25
Track AI agent fleet performance, costs, anomalies, and trends.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 207 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 483 tokens (~69/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.joepangallo/mcp-server-agent-analytics server?
io.github.joepangallo/mcp-server-agent-analytics runs locally as an npm package, launched with npx -y mcp-server-agent-analytics. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-server-agent-analytics
claude mcp add joepangallo-mcp-server-agent-analytics -- npx -y mcp-server-agent-analytics
{
"mcpServers": {
"joepangallo-mcp-server-agent-analytics": {
"command": "npx",
"args": [
"-y",
"mcp-server-agent-analytics"
]
}
}
} {
"servers": {
"joepangallo-mcp-server-agent-analytics": {
"command": "npx",
"args": [
"-y",
"mcp-server-agent-analytics"
]
}
}
} codex mcp add joepangallo-mcp-server-agent-analytics -- npx -y mcp-server-agent-analytics
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joepangallo-mcp-server-agent-analytics": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-server-agent-analytics"
],
"enabled": true
}
}
} openclaw mcp add joepangallo-mcp-server-agent-analytics --command npx --arg -y --arg mcp-server-agent-analytics
mcp_servers:
joepangallo-mcp-server-agent-analytics:
command: "npx"
args: ["-y", "mcp-server-agent-analytics"] {
"McpServers": {
"joepangallo-mcp-server-agent-analytics": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-server-agent-analytics"
]
}
}
} assistant mcp add joepangallo-mcp-server-agent-analytics -t stdio -c npx -a -y mcp-server-agent-analytics
{
"mcpServers": {
"joepangallo-mcp-server-agent-analytics": {
"command": "npx",
"args": [
"-y",
"mcp-server-agent-analytics"
]
}
}
} 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.
- 25 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
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Analysed npm/mcp-server-agent-analytics@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
agent_insights ~62
Get deep insights for a specific AI agent — top queries, unhandled intents, latency stats (avg + P95), token usage, cost estimate, daily volume, and user feedback summary.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent ID to get insights for |
No output schema declared.
No examples provided.
analytics_dashboard ~63
Get a fleet-wide analytics dashboard for all AI agents. Returns total events, unique agents, success rate, token usage, cost estimates, per-agent breakdowns, trending topics, and daily volume.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Time range in days (default: 30) |
No output schema declared.
No examples provided.
compare_agents ~54
Compare two agents side by side on key metrics: event volume, success rate, latency, token usage, and cost.
| Name | Type | Req | Description |
|---|---|---|---|
| agent1 | string | yes | First agent ID |
| agent2 | string | yes | Second agent ID |
No output schema declared.
No examples provided.
detect_anomalies ~32
Check for anomalies across the agent fleet — error rate spikes, latency degradation, and unusual patterns compared to baseline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_agents ~26
List all registered AI agents with their total events, success rate, and last seen timestamp.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_events ~98
Query stored agent events with optional filters. Returns raw event data for analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Filter by agent ID |
| days | number | – | Time range in days |
| event_type | string | – | Filter by event type (e.g. 'query_completed') |
| limit | number | – | Max events to return (default: 50, max: 1000) |
| success | boolean | – | Filter by success status |
No output schema declared.
No examples provided.
track_event ~148
Ingest a new agent interaction event. Use this to track queries, completions, errors, and feedback for any AI agent.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent that generated this event |
| error | string | – | Error message if the interaction failed |
| event_type | string | – | Event type (e.g. 'query_completed', 'error', 'feedback') |
| latency_ms | number | – | Response latency in milliseconds |
| prompt_tokens | number | – | Number of prompt tokens used |
| query | string | – | The query or task that was processed |
| response_tokens | number | – | Number of response tokens used |
| success | boolean | – | Whether the interaction was successful |
No output schema declared.
No examples provided.
What is the io.github.joepangallo/mcp-server-agent-analytics server?
io.github.joepangallo/mcp-server-agent-analytics is listed in the public MCP registry as io.github.joepangallo/mcp-server-agent-analytics. Track AI agent fleet performance, costs, anomalies, and trends. This page covers its npm package (mcp-server-agent-analytics).
Is the io.github.joepangallo/mcp-server-agent-analytics server safe to use?
io.github.joepangallo/mcp-server-agent-analytics scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.joepangallo/mcp-server-agent-analytics server expose?
io.github.joepangallo/mcp-server-agent-analytics exposes 7 tools: analytics_dashboard, agent_insights, list_agents, detect_anomalies, query_events, and 2 more. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.
Is the io.github.joepangallo/mcp-server-agent-analytics server still maintained?
io.github.joepangallo/mcp-server-agent-analytics is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.joepangallo/mcp-server-agent-analytics server under?
io.github.joepangallo/mcp-server-agent-analytics declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.