Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Convai Analytics

NPM · @CONVAI/ANALYTICS-MCP

Analyze Convai sessions, latency, reliability, usage, and provider telemetry via API key.

−3 this week 85 Trust /100

Last scanned (22 hours ago)

Scores higher than 86% of npm servers

Category Monitoring and Observability

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Conv-AI/convai-analytics). View diagnostics → Pass
  • License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 177 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5091 tokens (~106/item across 48 items; 44 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 44 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 45 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 29 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 22 Oct 26 +1
    • Stability: 0.97 → pass security
  • 21 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +3
    • Stability: 0.80 → pass security
  • 16 Oct 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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 5 Nov 2026 · Analysed npm/@convai/analytics-mcp@0.2.5

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Conv-AI/convai-analytics
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Conv-AI/convai-analytics/.github/workflows/publish-mcp-registry.yml@refs/heads/main
Rekor log index 1513289774
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9a841fd633067fddcc97b08334bccad6bd037af9766c98103011327fdb7813fce647b445b09125fbb676904db4cd625b4dc71aa5e20e3532675dbea69

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 94 packages
Packages resolved 94
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 44 exposed · ~5,011 tokens

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 →

Tool Tokens
advanced_query ~44

Plan-gated. Run an advanced analytics query through the public API for questions not covered by curated tools.

NameTypeReqDescription
queryobjectyesPublic analytics query body accepted by the API.

No output schema declared.

No examples provided.

compare_providers ~142

Compare provider or model latency for LLM, TTS, ASR, or NeuroSync components.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
componentstring––
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
modelstring–Optional model filter.
percentilestring––
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

detect_regressions ~67

Plan-gated. Detect whether latency regressed in the current window compared with a baseline window.

NameTypeReqDescription
baselineRangestring––
currentRangestring––
groupBystring––
measurestring––
thresholdnumber––

No output schema declared.

No examples provided.

estimate_active_session_concurrency ~101

Estimate active session and LiveKit room pressure from session start/end/duration telemetry.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
bucketMinutesinteger––
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
rangestring–Relative time range.

No output schema declared.

No examples provided.

explain_slow_session ~125

Find a traceable slow interaction in a session or slow-session list and return the session timeline, trace, top span, and waterfall chart.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
rangestring–Relative time range.
sessionIdstring–Optional specific session id. If omitted, the tool scans slow sessions.

No output schema declared.

No examples provided.

find_component_latency_bottlenecks ~144

Rank the top latency offenders by component so an agent can explain likely bottlenecks.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
modelstring–Optional model filter.
percentilestring––
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.
topNinteger––

No output schema declared.

No examples provided.

generate_active_session_concurrency_chart ~99

Generate a Vega-Lite area chart estimating active sessions over time.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
bucketMinutesinteger––
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
rangestring–Relative time range.

No output schema declared.

No examples provided.

generate_character_usage_chart ~88

Generate a Vega-Lite leaderboard chart of sessions by character.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
rangestring–Relative time range.

No output schema declared.

No examples provided.

generate_component_latency_chart ~131

Generate a Vega-Lite bar chart showing p95 latency by processor/component.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
modelstring–Optional model filter.
percentilestring––
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

generate_dropped_error_persist_chart ~139

Generate a Vega-Lite trend chart for dropped error-persistence events.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

generate_error_breakdown_chart ~138

Generate a Vega-Lite bar chart of errors by processor/component.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
groupBystring––
limitinteger––
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

generate_error_trend_chart ~135

Generate a Vega-Lite line chart showing errors over time.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

generate_interaction_waterfall ~40

Generate a Vega-Lite waterfall chart for one interaction id's per-component latency breakdown.

NameTypeReqDescription
interactionIdstringyesConvai interaction id.

No output schema declared.

No examples provided.

generate_llm_model_latency_chart ~133

Generate a Vega-Lite chart ranking LLM models by p95 latency.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

generate_peak_concurrency_chart ~101

Generate a Vega-Lite chart showing estimated active sessions with a peak concurrency annotation.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
bucketMinutesinteger––
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
rangestring–Relative time range.

No output schema declared.

No examples provided.

generate_reliability_summary_chart ~79

Generate a Vega-Lite chart of interactions, sessions, errors, and error rate for a time range.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
experienceIdstring–Optional experience filter.
rangestring–Relative time range.

No output schema declared.

No examples provided.

generate_reliability_trends_chart ~140

Generate a Vega-Lite trend chart that combines errors and dropped persistence events.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

generate_session_duration_scatter ~103

Generate a Vega-Lite scatter plot of session duration versus interactions, colored by p95 latency.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
rangestring–Relative time range.
sortstring––

No output schema declared.

No examples provided.

generate_tts_provider_chart ~129

Generate a Vega-Lite chart of TTS provider attribution.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

generate_usage_trends_chart ~141

Generate a Vega-Lite chart for sessions, interactions, and unique end users over time.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_character_usage_leaderboard ~89

Rank characters by session volume for the selected time range.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
rangestring–Relative time range.

No output schema declared.

No examples provided.

get_component_latency_breakdown ~132

Answer which processor/component is contributing most to p95 end-to-end latency.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
modelstring–Optional model filter.
percentilestring––
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_dropped_error_persist_trend ~139

Track dropped error-persistence events over time as a reliability signal.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_error_breakdown ~135

Break down errors by processor/component to identify reliability hotspots.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
groupBystring––
limitinteger––
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_error_trend ~132

Answer whether errors are rising or falling over time.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_first_response_breakdown ~164

Group first-response SLA P50/P95/P99 for one character by mode, settings_hash, stage, provider, model, status, or turn_scope.

NameTypeReqDescription
characterIdstringyesCharacter id. Required for SLA views.
groupBystring––
latencyKindstring–Primary maps by observed mode: voice+animation -> all_modalities_ready, voice -> first_voice, text -> first_text.
limitinteger––
modestring–Optional observed mode, e.g. voice_to_voice_animation.
rangestring–Relative time range.
turnScopestring–Turn scope: all includes turn 1, warm is turn_id > 1, cold is turn_id = 1.

No output schema declared.

No examples provided.

get_first_response_markers ~133

Return settings-hash change markers for one character's first-response latency graph.

NameTypeReqDescription
characterIdstringyesCharacter id. Required for SLA views.
latencyKindstring–Primary maps by observed mode: voice+animation -> all_modalities_ready, voice -> first_voice, text -> first_text.
modestring–Optional observed mode, e.g. voice_to_voice_animation.
rangestring–Relative time range.
turnScopestring–Turn scope: all includes turn 1, warm is turn_id > 1, cold is turn_id = 1.

No output schema declared.

No examples provided.

get_first_response_settings ~61

Fetch one sanitized latency-relevant settings snapshot by settings hash.

NameTypeReqDescription
characterIdstring–Optional character id filter.
rangestring–Relative lookup window.
settingsHashstringyesSettings hash from a first-response row or marker.

No output schema declared.

No examples provided.

get_first_response_summary ~150

Character-first, mode-specific first-response SLA P50/P95/P99. Defaults include turn 1; use turnScope=warm for turn_id > 1.

NameTypeReqDescription
characterIdstringyesCharacter id. Required for SLA views.
latencyKindstring–Primary maps by observed mode: voice+animation -> all_modalities_ready, voice -> first_voice, text -> first_text.
modestring–Optional observed mode, e.g. voice_to_voice_animation.
rangestring–Relative time range.
turnScopestring–Turn scope: all includes turn 1, warm is turn_id > 1, cold is turn_id = 1.

No output schema declared.

No examples provided.

get_first_response_timeseries ~158

Bucketed first-response SLA P50/P95/P99 for one character and optional observed mode.

NameTypeReqDescription
characterIdstringyesCharacter id. Required for SLA views.
granularitystring–Bucket size for trend charts.
groupBystring––
latencyKindstring–Primary maps by observed mode: voice+animation -> all_modalities_ready, voice -> first_voice, text -> first_text.
modestring–Optional observed mode, e.g. voice_to_voice_animation.
rangestring–Relative time range.
turnScopestring–Turn scope: all includes turn 1, warm is turn_id > 1, cold is turn_id = 1.

No output schema declared.

No examples provided.

get_interaction_first_response ~34

Return the additive first-response waterfall for one interaction id.

NameTypeReqDescription
interactionIdstringyesConvai interaction id.

No output schema declared.

No examples provided.

get_interaction_trace ~41

Show the per-request component spans for one interaction id, including processor/provider/model durations where available.

NameTypeReqDescription
interactionIdstringyesConvai interaction id.

No output schema declared.

No examples provided.

get_latency_heatmap_chart ~145

Generate a Vega-Lite heatmap of p95 latency by day and UTC hour to spot systemic slow windows.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_latency_percentile_chart ~148

Generate a Vega-Lite line chart for aggregate P50/P95/P99 latency distribution over time for production readiness sign-off.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_latency_percentile_series ~152

Fetch one raw P50/P95/P99 end-to-end latency timeseries for custom analysis or charting.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
percentilestring––
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_latency_threshold_chart ~147

Generate a Vega-Lite chart showing p95 latency against a production-readiness threshold.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.
thresholdMsnumber––

No output schema declared.

No examples provided.

get_llm_model_latency ~132

Rank LLM models by p95 latency to spot model-driven latency issues.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_metrics_catalog ~36

List the public metrics this account can query so an agent can choose the right latency, reliability, usage, provider, or model metric.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_p95_latency_over_time ~141

Answer whether p95 end-to-end voice latency is getting better or worse over time.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_session_timeline ~43

Show the timeline of metrics and interaction ids inside one session, useful for explaining why a session felt slow.

NameTypeReqDescription
sessionIdstringyesConvai session id.

No output schema declared.

No examples provided.

get_summary ~82

Answer account-level questions like how many sessions, interactions, unique end users, errors, and headline latency percentiles happened in a time range.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
experienceIdstring–Optional experience filter.
rangestring–Relative time range.

No output schema declared.

No examples provided.

get_tts_provider_attribution ~132

Show which TTS voice providers contributed samples in the selected time range.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

get_usage_trends ~145

Fetch sessions, interactions, and unique end users over time for usage trend analysis.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
granularitystring–Bucket size for trend charts.
metricsarray––
modelstring–Optional model filter.
processorstring–Optional processor filter.
providerstring–Optional provider filter.
rangestring–Relative time range.
statusstring–Optional status filter.

No output schema declared.

No examples provided.

list_sessions ~121

Find recent, longest, or slowest sessions for the caller's account before drilling into a session timeline or interaction trace.

NameTypeReqDescription
appKeystring–Optional Convai app key filter.
characterIdstring–Optional character filter.
cursorstring–Opaque pagination cursor returned by the previous call.
endUserIdstring–Optional end-user filter.
experienceIdstring–Optional experience filter.
limitinteger––
rangestring–Relative time range.
sortstring––

No output schema declared.

No examples provided.

Install

How do I install the Convai Analytics MCP server?

Convai Analytics runs locally as an npm package, launched with npx -y @convai/analytics-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @convai/analytics-mcp

# add to Claude Code
claude mcp add conv-ai-convai-analytics-mcp -- npx -y @convai/analytics-mcp
Common questions

What is the Convai Analytics MCP server?

Convai Analytics is an MCP server listed in the public MCP registry as io.github.Conv-AI/convai-analytics-mcp. Analyze Convai sessions, latency, reliability, usage, and provider telemetry via API key. This page covers its npm package (@convai/analytics-mcp).

Is the Convai Analytics MCP server safe to use?

Convai Analytics scores 85 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Convai Analytics MCP server expose?

Convai Analytics exposes 44 tools: get_summary, get_metrics_catalog, list_sessions, get_session_timeline, get_interaction_trace, and 39 more. Their descriptions and schemas cost roughly 5,011 tokens of context every time the server is loaded.

Is the Convai Analytics MCP server still maintained?

Convai Analytics is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Convai Analytics MCP server under?

Convai Analytics declares the UNLICENSED licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the Convai Analytics MCP server?

VerifyMCP ran 16 checks on Convai Analytics, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.