crapkit
PYPI · CRAPKIT
Twelve tools to inspect CRAP scores, find work, and check edited functions against their ceiling.
Available components
Last scanned (11 hours ago)
Scores higher than 57% of PyPI servers
Category Testing and QA
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 Security44
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Declares code that runs automatically (setup.py, a custom setup.py cmdclass) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 50 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2669 tokens (~222/item across 12 items; 12 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 21 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 16 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 11 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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/crapkit@0.8.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 3 scripts
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
| setup_py | Not reviewed | <setup.py, unreviewed> |
| cmdclass | Not reviewed | <custom, unreviewed> |
Background: Why install scripts are a supply-chain risk →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
check_config Config and repo health check ~150
Checks that crapkit.toml agrees with the repo: typo keys, empty scopes, missing lane cwds, runners that fail to start. Run it first when any tool answers strangely or the ranking misses a file, and list_runs when only the history is in question. It needs no run, probes each runner once per lane directory and environment, runs no lane, and any problem arrives with isError true. repo can be any directory under the checkout, and one with no crapkit.toml above it answers a pointer, never a parent's config.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis_version | integer | – | the analysis semantics version; with the lizard version it stamps every ratchet mark, so a bump refuses old marks until the repo re-seeds |
| lanes | array | – | per declared lane |
| newest_run | object|null | – | the newest run, or null when nothing has run |
| problems | array | – | FAIL findings as sentences naming the fix; non-empty is exit 1 and the result carries isError true |
| resources | object | – | effective resource policy; limits and estimates, not sampled utilization |
| schema | integer | – | payload schema version, 1 |
| store | object | – | the run store |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
| versions | object | – | the tools behind every number |
| warnings | array | – | WARN findings: unmeasured directories, scopes with a lane but no scoped_tests template, artifacts written outside .crapkit, lanes without results_artifact; exit stays 0 |
No examples provided.
check_gate rescore --gate verdict for an edited file ~262
Checks an edited file by rescore --gate's rule: each changed function's ccn against its scope's ceiling, pardoned only while its crap is at or under its ratchet mark. The hook's commit gate pardons any marked function, so this is stricter and a breach predicts a verify refusal. Call it after an edit once get_function_brief states the rule. It runs no tests, and a breach reads gate.ok false, not an error. Marks are read only on a breach, so a clean gate skips a broken marks file. A tracked file is judged on its diff from HEAD, an untracked one in full.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | repo-relative, or absolute inside repo, source file to judge as edited. Outside the repo, missing or a directory answers a config error, and an unchanged or unscoped file judges 0. A file a scope tak… |
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| Name | Type | Req | Description |
|---|---|---|---|
| baseline_commit | string | – | that run's commit, full sha |
| baseline_run | integer | – | id of the run whose coverage was reused |
| functions | array | – | every function in the file, rescored |
| gate | object | – | the verdict block |
| note | string | – | fixed reminder that coverage is the baseline run's and complexity the working tree's; crapkit verify gives the real verdict |
| schema | integer | – | payload schema version, 1 |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
No examples provided.
get_function_brief Start-editing packet for one function ~259
Returns one function's start-editing packet from the newest trusted run: scored row, uncovered lines and the refresh, test, gate and verify command lines, none of them run. Use it once a function is chosen. Skip it for picking what to fix, that is get_next_item, and for a score across runs, get_function_history. Twins come from the run's stored index, whose first build takes seconds. name must live in path. A miss is a tool error (isError true, the exit-1 error object) whose message lists the file's functions.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | the long_name get_next_item printed (classify( score , late )), the bare identifier (classify, or route for a Rust `route cmd : & Cmd`), a fragment of either, the line the function starts on, or a ha… |
| path | string | yes | source file, repo-relative or absolute inside the repo; a backslash separates folders on Windows only |
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| Name | Type | Req | Description |
|---|---|---|---|
| attempts | array | – | every claim ever taken on this function, oldest first; [] on a first attempt, and a row with closed null is a claim still open |
| churn | object|null | – | the file's churn, or null when it had no commits in the window |
| commands | object | – | the rest of the loop as whole command lines for this file and scope; run them as given |
| commit | string | – | that run's commit, full sha |
| coupling | array | – | up to 5 change-coupling partners at support 5 and confidence 0.5, strongest first; empty when none qualify; list_coupled_files has the repo-wide list |
| duplication_twins | array | – | up to 10 near-duplicate functions at similarity 0.8, best first; empty is normal; list_duplicate_functions has the repo-wide pairs |
| est_splits | integer | – | 0 when ccn <= target, else ceil(ccn / target) |
| est_uncovered_paths | integer | – | (1 - cov) x ccn rounded half to even, so 2.5 reads 2 |
| file_functions | array | – | every scored function in the same file: where an extracted helper lands, and which names are taken |
| file_totals | object | – | the file rolled up |
| function | string | – | the resolved lizard long name, whichever name form was asked with |
| gate_rule | object | – | what check_gate will judge this edit by |
| handle | string | – | short name form: the bare identifier or (anonymous)#N, the same value get_next_item prints |
| lane | object|null | – | the lane whose artifact produced cov and uncovered_lines, verbatim from the config; null when no lane covers the scope |
| notes | object | – | prose the config carries for whoever edits here |
| params | array | – | parameters in declaration order, so a test can call the function without opening the file |
| path | string | – | the resolved file, repo-relative |
| ratchet_mark | number|null | – | the committed ratchet mark, or null when the function carries none or the repo has no ratchet file |
| regrowth | object | – | did this get fixed before |
| remedy | string | – | decompose, split-lines, add-tests or ok: the branch the session takes; scored.remedy carries the same value |
| run_id | integer | – | id of the run these numbers come from: the newest trusted run (a coverage run, or a verify run whose verdict passed) |
| schema | integer | – | payload schema version, 1 |
| scored | object | – | the whole scored row from the run |
| scored_changes | integer|null | – | how many files the run scored hold other content now than the run recorded, deleted files included; 0 means the numbers describe the files on disk; null when crapkit cannot compare: the run recorded… |
| shallow | boolean | – | true when this checkout is a shallow clone: churn and gate_rule.mark_age_days count only the commits the clone holds; set fetch-depth: 0 on the checkout or run git fetch --unshallow for the real coun… |
| source | string | – | the function's own text, start to end inclusive, newlines intact: editable without reading the file |
| stale | boolean | – | true when the run's commit is not HEAD. It judges the commit, not the files: an amend or a commit that touched no scored file sets it, and an uncommitted edit leaves it false; scored_changes counts t… |
| target | integer | – | this scope's effective ceiling: the highest CRAP a function may carry, and so also the highest ccn; the same value as gate_rule.ceiling |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
| uncovered_lines | array|null | – | line numbers no test ran; [] when the span is fully covered; null when no artifact could answer, then uncovered_lines_note says why |
| uncovered_lines_note | string | – | present only when uncovered_lines is null: the reason and the move (stale artifact, no test imports the file, coverage_optional scope) |
| unmeasured | boolean | – | true when no measurement stands behind cov: flag no-lane (no lane covers the scope) or cc-only (the scope asks for no coverage). cov 0.0 and est_uncovered_paths are then stand-ins, not a count of pat… |
| versions | object | – | what produced these numbers |
No examples provided.
get_function_history One function's score across runs ~310
Returns one function's ccn, coverage, crap and flag per run, oldest first, plus its ratchet mark. Use it to tell improving from decaying or regrown, and get_function_brief to start an edit. history true spawns git log -L capped at 10 commits, and tests true is null unless the lane recorded contexts. name matches the long names any run scored in path, so a fragment returns one entry per match, and a bare twin name picks the worst twin. A same-line twin's history skips runs stored before same-line positions. repo may be any directory under the checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| history | boolean | – | also list the commits that touched this function (git log -L), as commits |
| name | string | yes | the long_name get_next_item printed (classify( score , late )), the bare identifier (classify, or route for a Rust `route cmd : & Cmd`), a fragment of either, the line the function starts on, or a ha… |
| path | string | yes | source file, repo-relative or absolute inside the repo; a backslash separates folders on Windows only |
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| tests | boolean | – | also list the tests covering this function (coverage.py contexts), as tests |
| Name | Type | Req | Description |
|---|---|---|---|
| functions | array | – | the functions name resolved to, in store order |
| name | string | – | the name argument as given |
| path | string | – | the file asked about |
| schema | integer | – | payload schema version, 1 |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
No examples provided.
get_next_item Next function to fix ~228
Returns the next function to fix as a work packet, the newest trusted run's worst row by crap. Use it to start a fix, list_worklist to survey the same run by risk, and get_function_brief once a function is chosen. It runs no tests, and empty true means the queue is spent, not the work, so read reasons. Filters cut before top counts: top 3 with exclude ["tests/"] returns the three worst rows outside tests, and an unknown scope name is a config error.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | array | – | skip rows whose path or long function name contains any of these fragments (one --exclude each) |
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| scope | array | – | restrict the ranking to these declared scopes (exact [[scope]] names from crapkit.toml, one --scope each) |
| top | integer | – | return the next N packets as items instead of one item (N >= 1, default 1) |
| Name | Type | Req | Description |
|---|---|---|---|
| commands | object | – | the call that answers stale and scored_changes; run it as given |
| commit | string | – | that run's commit, full sha |
| empty | boolean | – | true when the queue has nothing to hand out; then reasons is present and item and items are absent |
| item | object | – | the one packet, present when empty is false and top is absent or 1 |
| items | array | – | up to top packets in crap-descending order, present when empty is false and top is above 1 |
| reasons | object | – | why the queue is empty, present only when empty is true; the stop condition is empty true with skipped_claimed and no_lane_over_target both 0 or absent and scored_changes 0 |
| run_id | integer | – | id of the run these numbers come from: the newest trusted run (a coverage run, or a verify run whose verdict passed) |
| schema | integer | – | payload schema version, 1 |
| scored_changes | integer|null | – | how many files the run scored hold other content now than the run recorded, deleted files included; 0 means the numbers describe the files on disk; null when crapkit cannot compare: the run recorded… |
| shallow | boolean | – | true when this checkout is a shallow clone: commits, authors and the churn the ranking reads count only the commits the clone holds; set fetch-depth: 0 on the checkout or run git fetch --unshallow fo… |
| skipped_claimed | integer | – | rows another session's claim hid; present only when non-zero, and list_claims names the holders |
| skipped_no_lane | integer | – | rows above the floor that no lane measures, kept out of the ranking because their cov 0 is a tooling gap, not a testing gap |
| stale | boolean | – | true when the run's commit is not HEAD. It judges the commit, not the files: an amend or a commit that touched no scored file sets it, and an uncommitted edit leaves it false; scored_changes counts t… |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
No examples provided.
get_ratchet_report Ratchet debt burn-down ~160
Reports the ratchet debt burn-down: open marks with their age, repayments and policy findings. Use it to judge whether marked debt is repaid or piling up, and get_function_history for one function's mark. It reads the marks file and its git history only, and ages count from the newest commit touching that file, never the clock. Open marks are the file's rows, committed or not. A deleted or emptied file reports the marks its history last held as open, none repaid, and no file with no history reports zeros. repo may be any directory under the checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_ts | integer | – | unix seconds of the newest commit that touched the ratchet file; every age and window counts back from here, never from the wall clock; 0 with no ratchet history |
| dropped_last_30d | integer | – | marks repaid in the 30 days before anchor_ts |
| dropped_last_90d | integer | – | marks repaid in the 90 days before anchor_ts |
| dropped_total | integer | – | marks repaid over the whole committed history |
| oldest | array | – | up to 20 open marks, oldest first |
| open | integer | – | marks open on disk, working tree included: an uncommitted seed counts |
| policy_violations | array|null | – | null when no debt policy is configured, [] when the policy ran clean, else the findings as sentences |
| schema | integer | – | payload schema version, 1 |
| shallow | boolean | – | true when this checkout is a shallow clone: ages and repayments count only the commits the clone holds; set fetch-depth: 0 on the checkout or run git fetch --unshallow for the real counts, and crapki… |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
| uncommitted | integer | – | marks the working tree and the newest committed ratchet file disagree on: added, repaid or tightened but not committed |
No examples provided.
get_trend Debt trend per run ~154
Returns per-run totals for every trusted run, oldest first, with a grade per scope. Use it for the whole repo's trajectory. Use get_function_history for one function and get_ratchet_report for marked debt. It runs no lane and spawns no git. The first call on a large store sums every run into a rollup cache and takes seconds. Later calls read the cache back. repo may be any directory under a checkout where crapkit init and crapkit coverage have run. One with no snapshot store yet answers isError true with the setup pointer.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| Name | Type | Req | Description |
|---|---|---|---|
| runs | array | – | one row per trusted run, oldest first |
| schema | integer | – | payload schema version, 1 |
| target | integer | – | the [crapkit] target: the default ceiling, the highest CRAP a function may carry, and so also the highest ccn, that every scope inherits unless it sets its own |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
No examples provided.
list_claims Open queue claims ~161
Lists open claims on queue items, oldest first. Use it when get_next_item answers empty or skipped_claimed above 0, and use get_function_brief to see one function's own attempts. No tool here writes a claim: the CLI releases a stale one with crapkit claims release PATH NAME, and verify closes one at the ceiling. repo may be any directory under the checkout, since the server walks up to the nearest crapkit.toml. No crapkit.toml above it answers an init pointer, and one with no snapshot store yet a coverage pointer, both as isError true.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | – | open claims, oldest first |
| open | integer | – | number of open claims |
| schema | integer | – | payload schema version, 1 |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
No examples provided.
list_coupled_files Files that change together ~208
Lists file pairs that keep landing in the same commits over the churn window, strongest first, at most 50. Use it before editing a file to learn what an edit drags along, and list_duplicate_functions for copied code. It reads a cached ranking, not the scored run, and walks git log again only when HEAD, the churn window or the clone depth moved. An empty list means no pair cleared both thresholds, not a missing run: min_support 5 needs five shared commits, and min_confidence 0.5 means the rarer file moved with its partner half the time.
| Name | Type | Req | Description |
|---|---|---|---|
| min_confidence | number | – | minimum P(pair changes together), 0 to 1 (default 0.5) |
| min_support | integer | – | minimum shared commits before a pair counts (default 5) |
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| Name | Type | Req | Description |
|---|---|---|---|
| pairs | array | – | pairs clearing both thresholds, ordered by support x confidence descending, at most 50 |
| schema | integer | – | payload schema version, 1 |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
| window_months | integer | – | months of git history the pairs were counted over, back from the commit date of HEAD (the config's churn_window_months) |
No examples provided.
list_duplicate_functions Near-duplicate function pairs ~188
Lists near-duplicate function pairs in the newest run, at most 50. Use it before a refactor so twins are folded together, and get_function_brief for one function's twins. It reads the run's stored index, whose first build takes seconds on a large repo, skips functions with under 8 lines of their own and nested pairs, and an empty list means no pair reached similarity. similarity is shared shingles over the smaller function: 1.0 admits only a function found whole inside another, 0.8 four lines in five, and repo may be any directory under the checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| similarity | number | – | containment threshold, shared over smaller, 0 to 1 (default 0.8) |
| Name | Type | Req | Description |
|---|---|---|---|
| pairs | array | – | pairs at or above similarity, best containment first, at most 50 |
| run_id | integer | – | the newest run whose rows were compared |
| schema | integer | – | payload schema version, 1 |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
No examples provided.
list_runs Scored run history ~164
Lists every run in the store, oldest first by id. Use it to see which commit the other tools answer from, get_trend for totals and get_function_history for one function. Marking the baseline run costs one git ancestry check per trusted run's commit, newest first, down to it: one when it is the newest, on any branch, none with no trusted run. repo may be any directory under the checkout, and a relative path resolves from the server's start directory. With no crapkit.toml above it, or no snapshot store yet, it answers isError true with the command to run.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| Name | Type | Req | Description |
|---|---|---|---|
| runs | array | – | every run in the store, oldest first |
| schema | integer | – | payload schema version, 1 |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
No examples provided.
list_worklist Risk ranking of every function ~219
Lists the newest trusted run's whole risk ranking, every admitted function ordered by ccn times recency-weighted churn. Use it to survey a repo or split work, and get_next_item for the one packet to fix now. It runs no tests and keeps finished rows, so it never empties. Churn is cached per HEAD: after a commit, or on first use, the next read walks git log. git ls-files and git status count changed scored files (scored_changes). scope narrows before top caps, and an unknown scope is a config error. repo may be any directory under the measured checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | – | path to the scored repo's root (default: the repo the server was started in); a leading ~ is the home directory |
| scope | array | – | restrict the ranking to these declared scopes (exact [[scope]] names from crapkit.toml, one --scope each) |
| top | integer | – | cap the active list (default: the config's worklist_top, 50) |
| Name | Type | Req | Description |
|---|---|---|---|
| active | array | – | the ranking: functions in files with churn in the window, risk descending, cut at top or worklist_top |
| active_total | integer | – | active rows admitted before the cap: what top or worklist_top hid |
| churn_window_months | integer | – | months of git history the churn weights cover, counted back from the commit date of HEAD |
| commands | object | – | the call that answers stale and scored_changes; run it as given |
| commit | string | – | that run's commit, full sha |
| dormant_count | integer | – | ranked functions whose file had no commits in the window |
| dormant_top | array | – | the first 10 dormant functions, same shape as active: sleeping hazards kept out of the queue |
| floor | integer | – | the effective worklist_floor: rows under this ccn are listed only when over their ceiling or in a hot file |
| run_id | integer | – | id of the run these numbers come from: the newest trusted run (a coverage run, or a verify run whose verdict passed) |
| schema | integer | – | payload schema version, 1 |
| scored_changes | integer|null | – | how many files the run scored hold other content now than the run recorded, deleted files included; 0 means the numbers describe the files on disk; null when crapkit cannot compare: the run recorded… |
| shallow | boolean | – | true when this checkout is a shallow clone: commits, authors and the churn the ranking reads count only the commits the clone holds; set fetch-depth: 0 on the checkout or run git fetch --unshallow fo… |
| stale | boolean | – | true when the run's commit is not HEAD. It judges the commit, not the files: an amend or a commit that touched no scored file sets it, and an uncommitted edit leaves it false; scored_changes counts t… |
| truncated | object | – | present only when the whole answer was longer than one tool result the server sends (7,500 characters): each list, string or object field it cut, at any depth, keeps its start, and full is the CLI co… |
No examples provided.
How do I install the crapkit MCP server?
crapkit runs locally as a PyPI package, launched with uvx crapkit 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 · crapkit
claude mcp add jeanfrancoisgagne-crapkit -- uvx crapkit mcp
What is the crapkit MCP server?
crapkit is an MCP server listed in the public MCP registry as io.github.JeanFrancoisGagne/crapkit. Twelve tools to inspect CRAP scores, find work, and check edited functions against their ceiling. This page covers its PyPI package (crapkit).
Is the crapkit MCP server safe to use?
crapkit scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 crapkit MCP server expose?
crapkit exposes 12 tools: get_next_item, list_worklist, list_runs, get_trend, get_function_brief, and 7 more. Their descriptions and schemas cost roughly 2,463 tokens of context every time the server is loaded.
Is the crapkit MCP server still maintained?
crapkit 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 crapkit MCP server under?
crapkit declares the MIT 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 crapkit MCP server?
VerifyMCP ran 15 checks on crapkit, 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 crapkit: 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.