keelyard
PYPI · KEELYARD
Proof gate, undo and output trimming for Claude Code, Codex and OpenCode coding agents.
Available components
Last scanned (3 hours ago)
Scores higher than 62% of PyPI servers
Category Developer Tools
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 hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 38 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to akobirjontulqinovfuture/keelyard). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1382 tokens (~98/item across 14 items; 14 tools + 0 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
- 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 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 66
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 5 Nov 2026 · Analysed pypi/keelyard@1.2.1
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 | akobirjontulqinovfuture/keelyard |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/akobirjontulqinovfuture/keelyard/.github/workflows/publish.yml@refs/tags/v1.2.1 |
| Rekor log index | 3562935249 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:ba38e43d6c08ccd3952a56ce01ba9d3fe763bb93e59677111ff432047cbb8aab |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 38 packages
| Packages resolved | 38 |
|---|---|
| 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 →
find_symbol ~105
Where is a symbol defined (best match first), and with refs=true where it is used. Returns {"matches": [...], "remaining", "next_offset"?}; results are paged, never cut silently.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Function, class or type name, e.g. "Cart". |
| offset | integer | – | Skip this many results; use next_offset from the last call. |
| refs | boolean | – | Also list call sites and uses (source before tests). |
Structured output declared, but exposes no named fields.
No examples provided.
memory_search ~128
Search past Claude Code, Codex and OpenCode sessions, best match first. New sessions are indexed first. Returns {"hits": [{"agent", "session", "project", "ts", "role", "snippet"}], "remaining", "next_offset"?}.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_chars | integer | – | Max characters of snippets returned. |
| offset | integer | – | Skip this many hits; use next_offset from the last call. |
| query | string | yes | Words to look for, e.g. "stripe webhook signature". |
| this_project_only | boolean | – | Only sessions that ran in this project. |
Structured output declared, but exposes no named fields.
No examples provided.
proof_check ~91
Mark one requirement as verified, with concrete evidence (a command and its result, or file:line). Returns the updated requirement.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence | string | yes | What you ran or saw, e.g. "pytest tests/test_cart.py::test_once passed" or "cart.py:14 caps at one use". |
| requirement_id | integer | yes | The id from proof_requirements, e.g. 1. |
Structured output declared, but exposes no named fields.
No examples provided.
proof_requirements ~79
Record what the user asked for as a checklist. Call this first. Duplicate items are ignored. Returns {"requirements": [{"id", "text", "done", "evidence"}]}.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | One short, checkable item per user ask, e.g. ["discount applies once", "empty cart costs 0"]. |
Structured output declared, but exposes no named fields.
No examples provided.
proof_run_tests ~101
Run the project's tests and record the result as evidence. Returns {"exit", "passed", "seconds", "cmd", "output"} where output is a compact tail.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | Optional override, e.g. "pytest -q tests/test_cart.py". Default: [proof].test_cmd or auto-detected. |
| phase | string | – | "before" your change (baseline) or "after" it (required by the gate). |
Structured output declared, but exposes no named fields.
No examples provided.
proof_status ~34
Is the work proven? Returns {"proven", "missing": [what to do next], "requirements", "report"}.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
read_file ~129
Read a project file. A repeat read of an unchanged file returns a one-line notice instead of the text; a changed file returns only the diff since your last read. Returns {"path", "content"}.
| Name | Type | Req | Description |
|---|---|---|---|
| end | integer | – | Last line, inclusive; 0 = end of file. |
| force | boolean | – | Return the full text even if you read it before (e.g. after compaction). |
| path | string | yes | Project-relative path, e.g. "src/cart.py". Windows separators are accepted. |
| start | integer | – | First line, 1-based. |
Structured output declared, but exposes no named fields.
No examples provided.
recall ~55
Return the full raw output that run_compact or the shell-output filter shortened.
| Name | Type | Req | Description |
|---|---|---|---|
| output_id | string | yes | The id printed by run_compact, e.g. "3f9a1c2b7d4e". |
Structured output declared, but exposes no named fields.
No examples provided.
rewind_list ~68
List recent workspace snapshots, oldest first. One is taken after every edit or shell command. Returns {"steps": [{"step", "tool", "ts", "files", "n_files"}], "total"}.
| Name | Type | Req | Description |
|---|---|---|---|
| last | integer | – | How many recent steps, e.g. 20. |
Structured output declared, but exposes no named fields.
No examples provided.
rewind_to ~75
Restore project files to how they were after `step`. A safety snapshot is taken first, so calling rewind_to(safety_step) undoes this. Returns {"restored", "removed", "safety_step", "new_step"}.
| Name | Type | Req | Description |
|---|---|---|---|
| step | integer | yes | A step number from rewind_list, e.g. 3. |
Structured output declared, but exposes no named fields.
No examples provided.
run_compact ~94
Run a command and return output with failures, errors and file:line kept and noise dropped. Returns {"exit", "output"}; the output ends with an id for recall() when anything was cut.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Command line, run without a shell, e.g. "pytest -q" or "git log -n 20". |
| timeout | integer | – | Seconds before the command is killed. |
Structured output declared, but exposes no named fields.
No examples provided.
swarm ~193
Run small tasks on the configured helper model in parallel. Each answer is checked: citations (path:line) must exist; drafts must apply and pass the tests in a throwaway copy (never applied to your files). Failed answers are retried with the checker's notes, best-of-N, then escalated to the strong model if set. With no helper model configured, returns {"mode": "plan", "subagent_tasks": [...]} for your own subagents.
| Name | Type | Req | Description |
|---|---|---|---|
| tasks | array | yes | Each: {"kind": "ask"|"summarize"|"draft_edit"|"grep", "prompt": str, "files": [paths], "symbols": [names]}. "symbols" narrows the context to those definitions. Tip: swarm_plan builds this list for yo… |
Structured output declared, but exposes no named fields.
No examples provided.
work_state ~108
Compact state that survives compaction: requirements, decisions, changed files, open questions. Record each key decision with a ref to the file line or command that backs it.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | show, record, or resolve. |
| item | integer | – | Id to resolve. |
| ref | string | – | Evidence: "path:line", "cmd: <command>" or "#<proof item>". Required for decisions. |
| text | string | – | The decision or question, one line. |
Structured output declared, but exposes no named fields.
No examples provided.
workflow ~40
A short step-by-step guide: plan (plan-implement-verify), debug (loop), review (diff checklist).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Which guide. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the keelyard MCP server?
keelyard runs locally as a PyPI package, launched with uvx keelyard. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · keelyard
claude mcp add akobirjontulqinovfuture-keelyard -- uvx keelyard
What is the keelyard MCP server?
keelyard is an MCP server listed in the public MCP registry as io.github.akobirjontulqinovfuture/keelyard. Proof gate, undo and output trimming for Claude Code, Codex and OpenCode coding agents. This page covers its PyPI package (keelyard).
Is the keelyard MCP server safe to use?
keelyard scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 keelyard MCP server expose?
keelyard exposes 14 tools: proof_requirements, proof_check, proof_run_tests, proof_status, rewind_list, and 9 more. Their descriptions and schemas cost roughly 1,300 tokens of context every time the server is loaded.
Is the keelyard MCP server still maintained?
keelyard is still listed as active in the MCP registry. We last reached this channel on 5 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 keelyard MCP server under?
keelyard 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.