@quario/mcp

MCPattested
v0.2.1com.getquarioApache-2.0Updated 6d agonpmGitHub

Validate and render quario report definitions (JSON) to PDF, Excel, Word, HTML or CSV.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
298Downloads/wk
1GitHub stars
6d agoLast update
Reads these credentials
  • QUARIO_LICENSEAPI keyoptional

    The license key. Leave it unset to evaluate, and the output carries a watermark.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorcom.getquario
LicenseApache-2.0
Version0.2.1
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 286b836
Dependencies✓ 24 resolved · none vulnerable
Tool surface2 tools · none privileged
Security scan✓ Cleanv0.2.1 · 4d agoHow well does this scan work?
EvalsNone
IndexedOct 7, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged
Statically extracted from the published packagev0.2.1 · 4d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

validate_reportCheck 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.

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.

No input schema was published for this tool.

render_reportRender 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.

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.

No input schema was published for this tool.

2 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Validate and render quario report definitions (JSON) to PDF, Excel, Word, HTML or CSV.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-08 — observed resolution, not a publisher declaration.

24 packages resolved · 7 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.