MCP Risk

Directory / server

app.cellarion/cellarion

This directory entry reports an automated security scan of app.cellarion/cellarion, scanned 2026-07-28. Trust grade A rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via package-source

A 93/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as app.cellarion/cellarion. 1 finding
  • Registry entry: app.cellarion/cellarion ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 0 days ago
  • Stars: 14
  • License: AGPL-3.0
  • Security policy (SECURITY.md): absent
WARN Published package is consistent and attested §1.3
Minor integrity gaps: package is only 9 days old; no npm provenance attestation. 6 findings
  • Package: cellarion-mcp@0.1.1 ↗
  • Ecosystem: npm
  • Age: 9 days
  • Weekly downloads: 317
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned; no high-risk capability signals. 1 finding
  • Detected capabilities: none
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://cellarion.app/api/mcp
PASS Authentication required §3.2
Server rejects anonymous requests and advertises its auth scheme. 1 finding
  • WWW-Authenticate: Bearer resource_metadata="https://cellarion.app/.well-known/oauth-protected-resource/api/mcp"
PASS OAuth protected-resource metadata published §3.3
Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec. 1 finding
  • Authorization server: https://cellarion.app
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for cellarion-mcp @0.1.1 (npm).
UNVERIFIABLE Server-supplied instructions free of poisoning indicators §5.1–§5.4

No server-supplied instructions or tool descriptions were obtainable to scan.
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.