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

Cejel

OCI · GHCR.IO/BARGLABS/CEJEL:0.2.2 · SCANNED AUG 3

Offline deterministic engineering-trust certificates for repositories, with no telemetry.

Available components

oci · ghcr.io/barglabs/cejel:0.2.2 40
40 Trust /100
Trust breakdown (6 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 →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • CVE data not yet available for this package.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency-health data not yet available.Unverified
Provenance & Transparency45
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
  • Tool/resource definitions use about 268 tokens (~89/item across 3 items; 1 tools + 2 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 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 2 categories

Categories scored 0 because we could not verify them: 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.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

oci · ghcr.io/barglabs/cejel:0.2.2

# add to Claude Code
claude mcp add barglabs-cejel -- docker run --rm -i ghcr.io/barglabs/cejel:0.2.2
# add to Codex CLI
codex mcp add barglabs-cejel -- docker run --rm -i ghcr.io/barglabs/cejel:0.2.2
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "barglabs-cejel": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/barglabs/cejel:0.2.2"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  barglabs-cejel:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/barglabs/cejel:0.2.2"]
// mcp.json
{
  "mcpServers": {
    "barglabs-cejel": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/barglabs/cejel:0.2.2"
      ]
    }
  }
}
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.

  • 31 Jul 26 −6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +35
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: good functional
  • 29 Jul 26 11

    First indexed and scored.

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 3 Aug 2026 · Analysed oci/ghcr.io/barglabs/cejel:0.2.2

Provenance none

Ecosystem: oci · Outcome: none

Reason: no_attestation

MCP tools — 1 exposed · ~227 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.

Tool Tokens
scan ~227

Score a repository's engineering-trust signals (tests, secrets, isolation, claim-vs-reality, CI discipline) with the @cejel/cejel trust-certificate scan — the exact same offline, deterministic scoring as running the @cejel/cejel CLI on the path. Returns the trust cert as JSON: overall + code/process sub-scores (0-4) for a scored repository, or null scores with an abstention reason when Cejel establishes structural source absence or zero measurable free-core criteria; plus the verdict and top findings. No network, no telemetry, no signup. After a scan, the full HTML certificate and SVG badge are readable as the resources cejel-cejel://last-scan/certificate.html and cejel-cejel://last-scan/badge.svg.

NameTypeReqDescription
formatstring—summary (default): compact cert digest — scores, verdict, top findings. json: the full structured report, identical to the CLI's report.json.
pathstringyesPath to the repository to score (absolute, or relative to the server CWD)

No output schema declared.

No examples provided.