AVA
NPM · MCP-SERVER-AVA
Load data, inspect schemas, run SQL, analyze datasets, and build charts with AVA via MCP.
Available components
Last scanned (13 hours ago)
Scores higher than 56% of npm servers
Category Data and Analytics
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
- 98 of 317 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to DoubleCore/mcp-server-ava). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 387 tokens (~48/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ava_query" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 8 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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 →
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.
- 13 Nov 26 77
First indexed and scored.
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 21 Nov 2026 · Analysed npm/mcp-server-ava@0.1.3
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 | DoubleCore/mcp-server-ava |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/DoubleCore/mcp-server-ava/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3843608265 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:166ad7f44915f1f356d759eacb32b7df5516e42c8f4600f2596a4008655eea798160587868aaad01a021c2c20f2b2a29f608d4373a8e9d936bf896e60 |
Background: How many MCP packages publish verified provenance →
Dependencies 317 packages
| Packages resolved | 317 |
|---|---|
| Deprecated | 1 |
| Stale | 97 |
| 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 →
ava_analyze Answer a question in natural language ~84
Ask a question about the loaded dataset. AVA writes and executes the SQL, then summarizes the result. Requires OPENAI_API_KEY (and optionally OPENAI_MODEL / OPENAI_BASE_URL) in the server environment.
| Name | Type | Req | Description |
|---|---|---|---|
| includeSummary | boolean | – | Whether to write a prose answer. Defaults to true. |
| question | string | yes | The question to answer from the data. |
No output schema declared.
No examples provided.
ava_load_data Load data into AVA ~48
Load a dataset and return its schema. Replaces the previously loaded dataset. Use inline CSV or JSON for small pasted data, or a file path for larger local files.
| Name | Type | Req | Description |
|---|---|---|---|
| source | – | yes | – |
No output schema declared.
No examples provided.
ava_profile Profile the loaded dataset ~49
Compute column statistics (row count, nulls, distinct, min, max, mean, median) for the dataset.
| Name | Type | Req | Description |
|---|---|---|---|
| metrics | array | – | Statistics to compute. Omit for AVA defaults. |
No output schema declared.
No examples provided.
ava_query Run SQL against the dataset ~51
Execute one read-only SELECT statement with DuckDB semantics. Aggregate, filter, and sort in SQL so the result stays small.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | A single SELECT statement, using table names from ava_schema. |
No output schema declared.
No examples provided.
ava_schema Inspect the loaded dataset ~21
Return table names, columns, and types for the loaded dataset.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ava_suggest Suggest questions about the data ~30
Suggest questions worth asking about the loaded dataset. Requires a model configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
No output schema declared.
No examples provided.
ava_translate Translate a question to SQL ~33
Translate a question into SQL without running it, so a human can review the statement first.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
No output schema declared.
No examples provided.
ava_visualize Build a chart for a result ~71
Recommend a chart for rows from ava_query or ava_analyze. Returns a GPT-Vis config, which AVA renders to standalone HTML with the `viz --spec` CLI command.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | Rows from a previous tool call. |
| question | string | yes | The question the rows answer. |
No output schema declared.
No examples provided.
How do I install the AVA MCP server?
AVA runs locally as an npm package, launched with npx -y mcp-server-ava. 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-ava
claude mcp add doublecore-mcp-server-ava -- npx -y mcp-server-ava
What is the AVA MCP server?
AVA is an MCP server listed in the public MCP registry as io.github.DoubleCore/mcp-server-ava. Load data, inspect schemas, run SQL, analyze datasets, and build charts with AVA via MCP. This page covers its npm package (mcp-server-ava).
Is the AVA MCP server safe to use?
AVA scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 AVA MCP server expose?
AVA exposes 8 tools: ava_load_data, ava_schema, ava_profile, ava_query, ava_analyze, and 3 more. Their descriptions and schemas cost roughly 387 tokens of context every time the server is loaded.
Is the AVA MCP server still maintained?
AVA is still listed as active in the MCP registry. We last reached this channel on 21 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 AVA MCP server under?
AVA declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the AVA MCP server?
VerifyMCP ran 15 checks on AVA, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about AVA: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.