quario
NPM · @QUARIO/MCP
Validate and render quario report definitions (JSON) to PDF, Excel, Word, HTML or CSV.
Available components
Last scanned (19 hours ago)
Scores higher than 93% of npm servers
Category Documents and Files
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 Security100
- 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
- 1 of 24 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to getquario/mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 23 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 477 tokens (~238/item across 2 items; 2 tools + 0 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 Management73
- Stability observed for 22 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
- 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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 →
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +3
- Stability: unverified → 0.27 ▲ functional
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/@quario/mcp@0.3.0
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 | getquario/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/getquario/meta/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3226826943 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5e7f19a6ab1d0ab886655a78de484116c6a4e6a3b6bfda80b6ec1af17621b72fc8aac1f38adb371963daf1c1c4e43029d1de1e3a2d363104e11ae8dbc |
Background: How many MCP packages publish verified provenance →
Dependencies 24 packages
| Packages resolved | 24 |
|---|---|
| Stale | 1 |
| 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 →
render_report ~381
Render a quario report definition to one target and write the output to a file. Returns the file's absolute path, never its content. A definition with problems returns them instead, as validate_report does.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | The default currency code for `format: "currency"`, for this render. |
| data | – | – | The render data, any JSON value. Give exactly one of `data` and `dataPath`. An object whose only key is `$image` or `$base64` decodes to bytes, which is how an image's `source` expression reads a pic… |
| dataPath | string | – | A JSON file holding the render data, as a path inside the server's data root. `$image` and `$base64` objects decode there too, and an `$image` path resolves against the data root, not the file. |
| definition | object | yes | The report definition to check or render. |
| filename | string | – | The basename to write under, without a directory. The target's extension is forced, and a name that exists is never overwritten. Omit it for `report-<timestamp>`. |
| locale | string | – | The locale `format` presents in, for this render. |
| options | object | – | Options for the target: `page` and `meta` for pdf, xlsx and docx, and `filter` for xlsx. The csv target takes none. |
| params | object | – | Values for the definition's declared `params`. |
| target | string | yes | The target to render with. |
| timeZone | string | – | The time zone dates present in, for this render. |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | integer | yes | – |
| path | string | yes | – |
| target | string | yes | – |
No examples provided.
validate_report ~96
Check a quario report definition without rendering it. Returns its problems, each at the schema path it sits at, and its warnings. Name targets to also check the definition's `required` declarations against what each target makes of them.
| Name | Type | Req | Description |
|---|---|---|---|
| definition | object | yes | The report definition to check or render. |
| targets | array | – | Targets to check the definition's `required` declarations against. Omit it to check the document alone. |
| Name | Type | Req | Description |
|---|---|---|---|
| problems | array | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the quario MCP server?
quario runs locally as an npm package, launched with npx -y @quario/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 · @quario/mcp
claude mcp add com-getquario-mcp -- npx -y @quario/mcp
What is the quario MCP server?
quario is an MCP server listed in the public MCP registry as com.getquario/mcp. Validate and render quario report definitions (JSON) to PDF, Excel, Word, HTML or CSV. This page covers its npm package (@quario/mcp).
Is the quario MCP server safe to use?
quario scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting 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 quario MCP server expose?
quario exposes 2 tools: validate_report, render_report. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.
Is the quario MCP server still maintained?
quario 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 quario MCP server under?
quario declares the Apache-2.0 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 quario MCP server?
VerifyMCP ran 16 checks on quario, 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.