crit
PYPI · CRIT
Build, evaluate and serve a bespoke LLM inference engine for your own GPU with crit's commands.
Available components
Last scanned (13 hours ago)
Scores higher than 55% of PyPI servers
Category AI and Machine Learning
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 25 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to crit-labs/crit). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability33
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 12725 tokens (~176/item across 72 items; 62 tools + 10 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety94
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 13 of 17 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "crit_eval_context" implies "eval" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 64 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 (15)
- 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
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.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
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.
- 20 Nov 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.
- 18 Nov 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.
- 17 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 9 Nov 26 73
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 pypi/crit@0.17.2
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | crit-labs/crit |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/crit-labs/crit/.github/workflows/release.yml@refs/tags/v0.17.2 |
| Rekor log index | 3763503317 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:33e3a4022c60291a4978b5b22949695a6b395a456e03839987c3b1d343de1526 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 25 packages
| Packages resolved | 25 |
|---|---|
| Stale | 1 |
| No linked repository | 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 →
crit_eval_ab crit eval ab ~262
Alternate two engines' speed runs in one session and report paired ratios
| Name | Type | Req | Description |
|---|---|---|---|
| adapter | string | – | Adapter of engine A |
| adapter_b | string | – | Adapter of engine B (default: engine A's adapter) |
| config | string | – | JSON configuration overrides of engine A (text or a file), over its packaged configuration.json |
| config_b | string | – | JSON configuration overrides of engine B (text or a file), over its packaged configuration.json |
| context | integer | – | Context both engines are built for (the run's kv_tokens) |
| data | string | yes | – |
| model | string | yes | – |
| out | string | yes | Result JSON path |
| package | string | – | Engine A's crit package, opened through Core's loader |
| package_b | string | – | Engine B's crit package (default: engine A's engine) |
| repetitions | integer | – | Measured repetitions per engine and round |
| rounds | integer | – | Rounds; each round runs both engines, order alternating |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
| warmups | integer | – | Warmup runs per engine and round |
No output schema declared.
No examples provided.
crit_eval_compare crit eval compare ~58
Print a side-by-side table of result files
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_context crit eval context ~271
The max context for a model on a device: the model's positions and the KV cache that fits next to its weights
| Name | Type | Req | Description |
|---|---|---|---|
| context_reserve_gib | number | – | Device memory kept out of the KV cache for workspaces and speed techniques (default: settings.toml context_reserve_gib, else the protocol's reserve_gib) |
| device | string | yes | Device file from `crit eval probe` |
| drafter | array | – | A companion drafter the engine may load beside the model; its stored weights are kept out of the KV cache (repeatable) |
| json | boolean | – | Print the computation as JSON |
| model | string | yes | Model directory |
| ram_headroom_gib | number | – | Host memory left free, for the placement scenario (default: settings.toml ram_headroom_gib, else 2) |
| requested_context | integer | – | The longest request wanted (default: settings.toml context_tokens, else 200,000) |
| vram_headroom_gib | number | – | Device memory left free (default: settings.toml vram_headroom_gib, else 1) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_fetch crit eval fetch ~169
Fetch the checkpoint's reference package (prepared data and reference scores) into the data, so a run needs only the engine
| Name | Type | Req | Description |
|---|---|---|---|
| chat_template | string | – | Chat template (jinja) to render the prompts with, for a model that carries none (default: the one crit ships for the model's family); it becomes part of the model's identity; the package was prepared… |
| data | string | yes | Data directory to write |
| model | string | yes | The checkpoint the engine serves |
| packages | string | – | Package source: a folder or an https base URL (default: settings.toml's eval_packages) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_journal crit eval journal ~89
How far a round got: its journal's engines, parts and requests, replayed and live, and how it ended
| Name | Type | Req | Description |
|---|---|---|---|
| journal | string | yes | A round's journal (R.journal.jsonl beside its result R.json) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_kernels crit eval kernels ~360
Trace every kernel of the speed cases (CUPTI, Linux) and rank them per phase by time, launch width and share of peak
| Name | Type | Req | Description |
|---|---|---|---|
| adapter | string | – | Python file exporting create_eval_engine(context) |
| backend | string | – | Device API the engine runs on: cuda (CUPTI) or hip (rocprofiler-sdk) |
| case | array | – | Trace only these speed cases (repeatable); default all |
| config | string | – | JSON configuration overrides for the adapter, text or a file, over the configuration.json packaged beside it |
| context | integer | – | Context the engine is built for (the run's kv_tokens) |
| data | string | yes | Prepared suite directory for this model |
| device | string | – | Device ceilings from `crit eval probe` for share of peak |
| hipcc | string | – | hipcc of a ROCm that ships rocprofiler-sdk (--backend hip) |
| model | string | yes | Model directory passed to the adapter |
| nvcc | string | – | nvcc of a CUDA toolkit that ships CUPTI |
| out | string | yes | Kernel report JSON path |
| package | string | – | A crit engine package, opened through Core's loader |
| top | integer | – | Kernels listed per phase |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
| work | string | – | kernel_work rules ahead of the adapter's own, as JSON text or a file: [{"match": NAME_PART, "term": matmul|attention|recurrent|other|draft, "format": nvfp4|fp8|bf16, ...}] |
No output schema declared.
No examples provided.
crit_eval_pack crit eval pack ~79
Add prepared data scored by the reference to a package folder
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Prepared suite directory holding reference scores |
| packages | string | yes | Package folder to add it to |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_pin crit eval pin ~172
Record one engine's plain greedy output of every speed case as the data directory's pinned continuation (decode is then measured on that text)
| Name | Type | Req | Description |
|---|---|---|---|
| adapter | string | – | Python file exporting create_eval_engine(context) |
| config | string | – | JSON configuration overrides for the adapter, text or a file, over the configuration.json packaged beside it |
| context | integer | – | Context the engine is built for (the run's kv_tokens) |
| data | string | yes | Prepared data directory to pin the continuation in |
| model | string | yes | Model directory passed to the adapter |
| package | string | – | A crit engine package, opened through Core's loader |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_precheck crit eval precheck ~365
In minutes, the gates a candidate most often fails a whole round on: honesty of short replies and of one long reply, the request history around them, device memory and (with an adapter) the lower context
| Name | Type | Req | Description |
|---|---|---|---|
| adapter | string | – | Python file exporting create_eval_engine(context) |
| chat_template | string | – | Chat template (jinja) to render the prompts with, for a model that carries none (default: the one crit ships for the model's family); it becomes part of the model's identity |
| config | string | – | JSON configuration overrides for the adapter |
| context | integer | yes | Context the engine is built for (the run's kv_tokens) |
| data | string | yes | Prepared suite directory for this model |
| model | string | yes | Model directory passed to the adapter |
| no_lower | boolean | – | Skip the lower-context reopen |
| out | string | – | Write the items as JSON here |
| package | string | – | A crit engine package, opened through Core's loader |
| quality_mode | string | – | The run's quality mode (default speed): speed bounds honesty as Eval does and lets history part at near-ties; preserve does neither |
| served_model | string | – | With --url: the model to request |
| url | string | – | Base URL of an OpenAI-compatible server the engine runs behind (no lower-context check: a server cannot be opened again) |
| vram_headroom_gib | number | – | Device memory to find free after the load (default: settings.toml vram_headroom_gib, else 1) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_prepare crit eval prepare ~179
Freeze the suite as token ids for one model
| Name | Type | Req | Description |
|---|---|---|---|
| chat_template | string | – | Chat template (jinja) to render the prompts with, for a model that carries none (default: the one crit ships for the model's family); it becomes part of the model's identity |
| data | string | yes | – |
| model | string | yes | – |
| sampling | string | – | The user's sampling for the sampled speed suite in place of the model's generation_config.json, e.g. temperature=0.6,top_p=0.95,top_k=20 (temperature required; top_p, top_k, min_p optional). Results… |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_probe crit eval probe ~214
Measure device bandwidth and GEMM rates per weight format (needs nvcc, or hipcc on ROCm)
| Name | Type | Req | Description |
|---|---|---|---|
| backend | string | – | Device API to probe (default: cuda when nvcc is found, else hip when hipcc is) |
| devices | string | – | Probe several GPUs (CUDA): each one's figures and the copy rate between each pair, for multi-GPU limits (default: device 0 alone) |
| hipcc | string | – | hipcc to build the HIP probe with (default: PATH, ROCM_PATH, /opt/rocm*) |
| nvcc | string | – | nvcc to build the probe with (default: PATH, CUDA_HOME, /usr/local/cuda*) |
| out | string | yes | Device JSON path for `run --device` |
| repeats | integer | – | Probe runs; each value is the median |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_reference crit eval reference ~147
Score the prepared quality texts once on the checkpoint they were prepared from and store the scores under the data (torch + transformers, GPU; stop any engine first)
| Name | Type | Req | Description |
|---|---|---|---|
| allowance | boolean | – | Also score the texts with the activations quantized as the checkpoint declares and store how far that lands from the scores (allowance.json): what the format itself costs, reported, not judged; a sec… |
| data | string | yes | Prepared suite directory |
| model | string | yes | The checkpoint the data was prepared from |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_run crit eval run ~1,266
Evaluate one engine (prepares the data first when missing)
| Name | Type | Req | Description |
|---|---|---|---|
| adapter | string | – | Python file exporting create_eval_engine(context) |
| adaptive_sampled | string | – | Repeat each sampled speed case at further seeds until its relative standard error reaches the protocol's target or its repetition cap (protocol sampled_speed.adaptive), recorded in the result; off by… |
| attribute_drift | boolean | – | After quality, score it again on an engine opened with each of the adapter's exact_variants (one matrix group or arithmetic choice exact) and report each one's share of the drift budget |
| bandwidth | number | – | Achievable device memory bandwidth in GB/s; overrides the --device value |
| baseline | string | – | Earlier result of the same data to show KPI changes against |
| budget_minutes | number | – | The staged run's wall-clock budget, loads included (default: the protocol's 45) |
| certify | boolean | – | The candidate that will ship: stage 3 whatever the budget, then one request at the required context itself, which the capacity gate needs |
| chat_template | string | – | Chat template (jinja) to render the prompts with, for a model that carries none (default: the one crit ships for the model's family); it becomes part of the model's identity; data prepared already mu… |
| config | string | – | JSON configuration overrides for the adapter, text or a file, over the configuration.json packaged beside it |
| context | integer | – | Context (prompt plus output) every engine is built and measured for: the run's kv_tokens. Default: crit-eval's max context for the model on the --device |
| context_reserve_gib | number | – | Device memory kept out of the KV cache when crit-eval computes the max context: activations, workspaces, graphs and speed techniques (default: settings.toml context_reserve_gib, else the protocol's r… |
| data | string | yes | Prepared suite directory for this model |
| device | string | – | Device ceilings from `crit eval probe` (bandwidth and GEMM rates) |
| exactness | string | – | reported (default): agreement with plain greedy is shown and the quality budget judges the output; required: any difference fails the gate |
| jitter_seed | integer | – | Draw the held-out prompts' and the long-context curve's lengths from this seed, a recorded result's jitter.seed, to measure at its lengths again (default: a new seed per run; a resumed round's from i… |
| keep_disturbed | boolean | – | Finish the round even when a speed case's repetitions show a disturbed device (by default the round stops there; protocol speed.disturbed_spread) |
| label | string | – | Name shown in comparisons |
| model | string | yes | Model directory passed to the adapter |
| no_journal | boolean | – | Write no journal beside the result (by default every engine opened and request served is one line of OUT's .journal.jsonl, synced as it completes) |
| only | array | – | Run only these parts (repeatable); default is all. context: the long-context curve and retrieval up to the required context and the speed cases again at a lower context; history: the same requests on… |
| out | string | yes | Result JSON path |
| package | string | – | A crit engine package (plugins/ and configuration.json), which Core's eval-v1 adapter opens through Core's loader |
| profile | string | – | A protocol profile fixing what the run measures (protocol profiles). hub: crit-hub submissions, 200,000 tokens of context, the curve at its two ends, one engine load |
| quality_budget | string | – | Drift limits over the protocol defaults, e.g. '{"ppl_ratio_max": 1.02}'; keys ppl_ratio_max, kld_mean_max, kld_p99_max |
| quality_mode | string | – | The quality mode: how much output drift from the checkpoint the engine may trade for speed, whatever format the checkpoint is stored in; both modes judge against the same reference (its stored weight… |
| repetitions | integer | – | Override the protocol's measured repetitions |
| requested_context | integer | – | The longest request wanted, which caps the max context crit-eval computes without --context (default: settings.toml context_tokens, else 200,000) |
| resume | string | – | Go on from a round that stopped (interrupted, crashed, a disturbed device, a hung engine): its journal (R.journal.jsonl beside its result R.json) answers the requests it served, the engine loads only… |
| served_model | string | – | With --url: the model to request (default: the one the server lists) |
| stage | string | – | How far a run without a profile measures (protocol stages): by default as far as the budget allows at the engine's measured rates; 1, 2 or 3 at most that far; full every part at the protocol's repeti… |
| url | string | – | Base URL of an OpenAI-compatible server the engine runs behind, for example http://127.0.0.1:8000/v1 (needs --context: the context the server was started with) |
| vram_headroom_gib | number | – | Device memory left free when crit-eval computes the max context (default 1) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
| warmups | integer | – | Override the protocol's warmup runs |
No output schema declared.
No examples provided.
crit_eval_status crit eval status ~188
Gates, goals, KPIs against their physical limits, gaps and missing inputs
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | string | – | Earlier result to show KPI changes against |
| data | string | – | The data directory the result was measured on: its model arithmetic prices prefill for a result that does not record it |
| device | string | – | Price prefill and time to first token with this `crit eval probe` result's rates instead of the result's own device |
| json | boolean | – | Print the status as JSON |
| kernels | string | – | A kernel trace of the engine (crit eval kernels): its prefill GPU time per floor term against the term's floor, with a gap each |
| result | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_eval_workbench crit eval workbench ~205
Check, time or profile a kernel on its workbench folder (crit kernels new): reference, floor, yardstick
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| device | string | – | bench: a `crit eval probe` result, for the floor |
| folder | string | yes | The workbench folder |
| iters | integer | – | bench: timed calls per shape and column count |
| ncu | string | – | profile: Nsight Compute's ncu, to add its sections |
| out | string | – | check and bench: the result JSON (default FOLDER/check.json, bench.json) |
| python | string | – | The engine's Python (torch and the GPU); default this one |
| shape | integer | – | One shape of kernel.json by index (profile: default the first) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_inference_check crit inference check ~51
Check the techniques' code against their metadata
| Name | Type | Req | Description |
|---|---|---|---|
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_inference_list crit inference list ~55
List the techniques by category
| Name | Type | Req | Description |
|---|---|---|---|
| json | boolean | – | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_inference_search crit inference search ~67
The techniques whose metadata holds every word of the query
| Name | Type | Req | Description |
|---|---|---|---|
| json | boolean | – | – |
| query | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_inference_show crit inference show ~65
One technique's guidance, symbols and files
| Name | Type | Req | Description |
|---|---|---|---|
| json | boolean | – | – |
| query | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_job_output Read a job's logs ~79
A job's command output (its JSON result) or errors (progress and reports) from a byte offset; offset -1 reads the end
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | yes | The job a command's call returned, such as job-3 |
| limit | integer | – | – |
| offset | integer | – | – |
| stream | string | – | – |
No output schema declared.
No examples provided.
crit_job_stop Stop a job ~76
Interrupt a running job as Ctrl+C would (crit releases its leases and settles what it can), ending its process tree after grace_seconds; an Eval stopped so goes on with crit_run_eval resume
| Name | Type | Req | Description |
|---|---|---|---|
| grace_seconds | number | – | – |
| job | string | yes | The job a command's call returned, such as job-3 |
No output schema declared.
No examples provided.
crit_job_wait Wait on a job ~77
Wait for a job to end, at most SECONDS; returns its result once it ended, else its state and newest errors
| Name | Type | Req | Description |
|---|---|---|---|
| job | string | yes | The job a command's call returned, such as job-3 |
| seconds | number | – | Longest wait (at most 3600); call again to go on |
No output schema declared.
No examples provided.
crit_jobs List jobs ~20
This server's jobs: state, exit code, logs
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
crit_kernels_inspect crit kernels inspect ~67
Explain every declared applicability match, rejection or unknown
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | yes | – |
| request | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_kernels_inventory crit kernels inventory ~57
Hash local artifact files without importing them
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_kernels_new crit kernels new ~377
Scaffold a workbench folder for a kernel: reference, shapes, yardstick, harness (measure it with crit eval workbench)
| Name | Type | Req | Description |
|---|---|---|---|
| column_invariant | string | – | – |
| columns | string | – | column (token) counts, comma-separated |
| format | string | – | bf16, fp8 or nvfp4 (NVFP4 weights against bf16 activations) for gemv and gemm |
| from | string | – | a kernel-builder project to start src/ from (a crit-kernels project, a Hub kernel's source); without it, kernel-builder init starts one |
| model | string | – | take the shapes from this checkpoint's matrices in the format |
| name | string | yes | – |
| op | string | yes | gemv or gemm (a working start in bf16, fp8 or nvfp4), or any other operation name for a harness to fill in |
| repeatable | string | – | no: the kernel may give other bits on a repeat (atomics, a split the workload chooses); the check judges repeats within the tolerance. For quality mode speed engines |
| root | string | – | – |
| run | string | – | the run folder, for --starter |
| shape | array | – | N,K (repeatable) |
| starter | boolean | – | the kernel --from copies is the starter (crit-kernels' workbench-starter: a simple, correct gemv/gemm in bf16 and fp8); allowed from a run's fourth candidate on |
| tolerance | number | – | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
| yardstick | string | – | the provider to time beside the kernel (provider syntax of plan levers) |
No output schema declared.
No examples provided.
crit_kernels_retain crit kernels retain ~104
Copy and verify a selected dependency into a new directory
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | yes | – |
| destination | string | yes | – |
| max_bytes | integer | – | – |
| reason | string | yes | – |
| request | string | yes | – |
| root | string | yes | – |
| select | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_kernels_search crit kernels search ~61
Search local implementation declarations
| Name | Type | Req | Description |
|---|---|---|---|
| catalog | string | yes | – |
| query | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_kernels_target crit kernels target ~52
Observe host OS/architecture; ABI remains explicit
| Name | Type | Req | Description |
|---|---|---|---|
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_kernels_verify crit kernels verify ~59
Recheck a retained dependency's bytes and applicability
| Name | Type | Req | Description |
|---|---|---|---|
| directory | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_models_drafter crit models drafter ~161
Distill a draft head for speculative decoding from the target itself and write its models_transform record
| Name | Type | Req | Description |
|---|---|---|---|
| calibration | string | yes | JSONL of {"text": ...} documents unrelated to Eval |
| device | string | – | torch device (default: cuda when available, else cpu) |
| out | string | yes | New or empty directory for the drafter |
| recipe | string | yes | models_recipe JSON with method drafter |
| record | string | yes | New models_transform JSON outside the source and output |
| source | string | yes | The target model directory (the checkpoint the engine serves) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_models_eval crit models eval ~126
Bind the Eval result of an engine serving the output to its record, with its quality replies scored on the source checkpoint
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | Eval data directory prepared from the source checkpoint |
| evaluation | string | yes | New models_evaluation JSON |
| record | string | yes | models_transform JSON |
| result | string | yes | crit eval run --url result of the engine serving the output; stop the server first |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_models_plan crit models plan ~92
Resolve a recipe against a checkpoint's headers: targets and bytes
| Name | Type | Req | Description |
|---|---|---|---|
| json | boolean | – | Print the resolved recipe and plan as JSON |
| recipe | string | yes | models_recipe JSON |
| source | string | yes | Unquantized source model directory |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_models_ptq crit models ptq ~149
Quantize a checkpoint and write its models_transform record
| Name | Type | Req | Description |
|---|---|---|---|
| calibration | string | – | JSONL of {"text": ...} documents unrelated to Eval (gptq only) |
| device | string | – | torch device (default: cuda when available, else cpu) |
| out | string | yes | New or empty directory for the transformed checkpoint |
| recipe | string | yes | models_recipe JSON |
| record | string | yes | New models_transform JSON outside the source and output |
| source | string | yes | Unquantized source model directory |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_models_verify crit models verify ~61
Re-hash a transform's output and source against its record
| Name | Type | Req | Description |
|---|---|---|---|
| record | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_pull crit pull ~645
crit pull OWNER/NAME: install a crit-hub engine, so that crit serve --engine OWNER/NAME serves it. It reads the engine's card (from a crit-hub checkout with --hub, else crit-hub's index.json), checks the card's requirements against this machine (a crit eval probe result, and nvcc), fetches the engine's source at the commit the card pins (from a crit-engines checkout with --engines, else its repository), checks its configuration against the sealed run's in card.lock.json, fetches the checkpoint at its pinned Hugging Face revision (or takes a local folder with --model) and checks every file against card.lock.json, fetches and checks the card's drafter downloads the same way, runs the card's build command (or unpacks a prebuilt artifact whose toolchain matches this machine instead), and installs the built package in the engine store (crit.pull.store). Nothing is installed until every step has passed.
| Name | Type | Req | Description |
|---|---|---|---|
| build_from_source | boolean | – | Build even when one of the card's prebuilt artifacts matches this machine |
| build_timeout | number | – | Seconds the build may take (default: 1800) |
| checkpoint | string | – | The checkpoint, when the engine was measured on several |
| context | integer | – | Context the engine serves at (default: the context its card measured) |
| device | string | – | A crit eval probe result to check the requirements against (default: settings.toml's device, else a probe run now) |
| download | array | – | A local copy of one of the card's downloads (a drafter's folder, an artifact's file), checked like a download (repeatable; default: fetch it from Hugging Face) |
| engine | string | – | The crit-hub engine, as OWNER/NAME |
| engines | string | – | Take the source from this crit-engines checkout, which holds the pinned commit (default: fetch that commit from the card's source repository) |
| force | boolean | – | Install again over an installed engine |
| hub | string | – | Read the card from this crit-hub checkout (default: crit-hub's index.json) |
| ignore_requirements | boolean | – | Install even when this machine does not meet the card's requirements |
| index | string | – | crit-hub's index.json, a URL or file (default: https://crit-hub.dev/index.json) |
| list | boolean | – | List the installed engines instead |
| model | string | – | A local copy of the checkpoint, checked file by file and hard-linked into the store (default: download it at the pinned Hugging Face revision) |
| project | string | – | crit checkout whose settings.toml gives the device and headroom and whose engines/ is the default store (default: this checkout); a crit installed without a checkout takes any folder (default: the cu… |
| store | string | – | Engine store (default: PROJECT/engines) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_ablate crit run ablate ~277
Serve a candidate built from plugins with each variant of its plugins (as built, at its base, without each and with each alone): a short bench of the run's cases and crit smoke per variant, and what each plugin adds, costs or breaks (docs/PLUGINS.md)
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string | yes | – |
| id | string | yes | Existing run identity |
| no_smoke | boolean | – | Leave out crit smoke on each variant |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| repetitions | integer | – | Repetitions per case and variant (default 3) |
| root | string | – | Run root; defaults to PROJECT/runs |
| seconds | number | – | Reservation length (default: the check process cap) |
| smoke_test | array | – | Run only this crit smoke test on each variant (repeatable) |
| variant | array | – | Serve only this variant (repeatable), e.g. full, base, without:ID, only:ID; crit plugins variants lists them |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_benchmark crit run benchmark ~152
Append a case's benchmark evidence to a candidate
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string | yes | – |
| id | string | yes | Existing run identity |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| record | object|array|string | yes | A JSON object (written to a file for the command) or a JSON file's path |
| root | string | – | Run root; defaults to PROJECT/runs |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_build crit run build ~252
Build a candidate's retained source with the recipe's build.command under a build attempt (log kept, attempt settled), then package the result
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string | yes | – |
| drop | array | – | Remove these build-folder paths (intermediates) before packaging; repeatable |
| id | string | yes | Existing run identity |
| no_package | boolean | – | Build and settle only |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| record | object|array|string | yes | Recipe: build {toolchain, command[, dependencies]}; the build's outputs are bound as dependencies, and the package is the plugin package Core's loader runs. A JSON object (written to a file for the c… |
| root | string | – | Run root; defaults to PROJECT/runs |
| seconds | number | – | Reservation length (default: the build process cap) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_candidate crit run candidate ~169
Allocate a candidate ID and retain its source and proposal
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Existing run identity |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| record | object|array|string | yes | label, rationale, strategy, configuration, store_decisions, parent/origin IDs. A JSON object (written to a file for the command) or a JSON file's path |
| root | string | – | Run root; defaults to PROJECT/runs |
| source | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_capture crit run capture ~255
Write a case's chat request (captured/CASE/request.json) that renders to the workload's prompt tokens with the template variables candidates serve
| Name | Type | Req | Description |
|---|---|---|---|
| case | string | – | – |
| id | string | yes | Existing run identity |
| inputs | string | – | Set the case's manifest row in this resolve payload (created when missing) |
| instruction | string | – | Line after the text (default: a summary request; '' for none) |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| root | string | – | Run root; defaults to PROJECT/runs |
| system | string | – | A leading system message |
| template_kwargs | string | – | chat_template_kwargs the request renders with, over recon's frozen template_variables (text or a file) |
| text | string | – | File of the user message's text (default: a neutral passage); it is cut to whole words and padded to the exact count |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_check crit run check ~195
Append a case's check evidence to a candidate
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string | yes | – |
| from_eval | boolean|string | – | Instead of --record: record the arithmetic, functional and resources check of every case from the candidate's retained Eval result (default its newest). true gives --from-eval alone |
| id | string | yes | Existing run identity |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| record | object|array|string | – | A JSON object (written to a file for the command) or a JSON file's path |
| root | string | – | Run root; defaults to PROJECT/runs |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_cost crit run cost ~246
Account the run's build cost from the agent's transcripts: wall time, tokens and API price per candidate, written to cost.json
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | The agent and model that built the run, as the record names it |
| id | string | yes | Existing run identity |
| prices | string | – | JSON object or file of {model: {input, cache_read, cache_write_5m, cache_write_1h, output}} in USD per million tokens, over the list prices |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| root | string | – | Run root; defaults to PROJECT/runs |
| transcript | array | yes | A Claude Code session, Codex rollout or plain usage JSONL (repeatable) |
| until | string | – | Count requests up to this UTC timestamp (default: the run's stop, else now) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_create crit run create ~187
Create a run and its first segment from a request
| Name | Type | Req | Description |
|---|---|---|---|
| from_engine | string | – | Start from a crit-hub engine: its engines/<owner>/<name>/ folder (card.yaml, card.lock.json, evidence/) is recorded as the run's origin_engine |
| id | string | – | Existing run identity |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| record | object|array|string | yes | A JSON object (written to a file for the command) or a JSON file's path |
| root | string | – | Run root; defaults to PROJECT/runs |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_eval crit run eval ~469
Run Eval on a packaged candidate through crit serve, quality against the run's model's scores of the fixed texts (scored once into the data)
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | string | – | Earlier Eval result to show KPI changes against |
| budget_minutes | number | – | Eval's wall-clock budget, loads included (default: crit-eval's 45) |
| candidate | string | yes | – |
| certify | boolean | – | The candidate that will ship: stage 3 whatever the budget, then one request at the run's kv_tokens, which the resources check needs. On the candidate ladder the full Eval of candidate 5 on and of the… |
| data | string | yes | Eval data directory prepared from the run's model |
| id | string | yes | Existing run identity |
| label | string | – | – |
| only | array | – | Run only these Eval parts (repeatable); default all |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| resume | boolean|string | – | Go on from an Eval attempt that stopped (interrupted, failed, timed out, a disturbed or hung engine): its journal's requests are answered again, the engine loads for the requests left; default the ca… |
| root | string | – | Run root; defaults to PROJECT/runs |
| seconds | number | – | Reservation length (default: to the segment's deadline; each request is bounded by the rates the engine measured) |
| stage | string | – | How far Eval measures (crit-eval's protocol stages): by default as far as its budget allows at the candidate's measured rates; 1, 2 or 3 at most that far; full every part as before stages. On the can… |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_measure crit run measure ~203
Benchmark the run's cases on a packaged candidate through crit serve, once its checks are recorded (check --from-eval)
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string | yes | – |
| exploratory | boolean | – | Measure even when the candidate's checks would leave its benchmarks exploratory (not recorded, or a required one did not pass), for telemetry or memory: a benchmark that does not qualify keeps the ca… |
| id | string | yes | Existing run identity |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| root | string | – | Run root; defaults to PROJECT/runs |
| seconds | number | – | Reservation length (default: the benchmark process cap) |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_package crit run package ~169
Package a candidate's runnable files and manifest
| Name | Type | Req | Description |
|---|---|---|---|
| candidate | string | yes | – |
| id | string | yes | Existing run identity |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| record | object|array|string | yes | Recipe: build {toolchain, command[, dependencies]}. A JSON object (written to a file for the command) or a JSON file's path |
| root | string | – | Run root; defaults to PROJECT/runs |
| source | string | yes | – |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
crit_run_plan crit run plan ~170
Record the next candidate's plan
| Name | Type | Req | Description |
|---|---|---|---|
| check | boolean | – | Run the plan's checks and print the record crit would store, recording nothing (the plan command of a replay) |
| id | string | yes | Existing run identity |
| project | string | – | crit checkout the run follows, whose settings.toml it reads (default: this checkout); a crit installed without a checkout takes any folder (default: the current one) |
| record | object|array|string | yes | A JSON object (written to a file for the command) or a JSON file's path |
| root | string | – | Run root; defaults to PROJECT/runs |
| wait_seconds | number | – | Seconds to wait for the command to end before returning its job to wait on with crit_job_wait (the command keeps running) |
No output schema declared.
No examples provided.
How do I install the crit MCP server?
crit runs locally as a PyPI package, launched with uvx crit mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · crit
claude mcp add crit-labs-crit -- uvx crit mcp
What is the crit MCP server?
crit is an MCP server listed in the public MCP registry as io.github.crit-labs/crit. Build, evaluate and serve a bespoke LLM inference engine for your own GPU with crit's commands. This page covers its PyPI package (crit).
Is the crit MCP server safe to use?
crit scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 crit MCP server expose?
crit exposes 62 tools: crit_run_create, crit_run_resolve, crit_run_plan, crit_run_check, crit_run_benchmark, and 57 more. Their descriptions and schemas cost roughly 12,417 tokens of context every time the server is loaded.
Is the crit MCP server still maintained?
crit 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 crit MCP server under?
crit 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 crit MCP server?
VerifyMCP ran 15 checks on crit, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about crit: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.