YAP — Yet Another Packager
OCI · GHCR.IO/M0RF30/YAP-MCP
Build native Linux packages (.deb/.rpm/.apk/.pkg.tar.zst) from a single PKGBUILD via MCP.
Available components
Last scanned (7 hours ago)
Scores higher than 77% of OCI servers
Category CI/CD and DevOps
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2183 tokens (~109/item across 20 items; 19 tools + 1 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 99% of tool parameters carry a description.Partial
- 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 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Package version: 2.7.6 → 2.8.0 functional
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 oci/ghcr.io/m0rf30/yap-mcp@2.8.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
build ~581
Start a yap build asynchronously. Returns a buildID; poll via build_status. The tool-call context is NOT propagated to the build — use build_cancel to stop a running build.
| Name | Type | Req | Description |
|---|---|---|---|
| cleanBuild | boolean | – | clean build dirs before starting |
| compressionDeb | string | – | deb compression: zstd, gzip, or xz |
| compressionRpm | string | – | rpm compression: zstd, gzip, or xz |
| debugDir | string | – | dir to capture per-step build debug artifacts |
| distro | string | – | target distro; auto-detected when empty |
| extraRepos | null|array | – | extra apt/dnf repo defs (--repo syntax) |
| fromPkgName | string | – | start build at this pkg |
| noBuild | boolean | – | prepare/resolve only, skip the build step |
| noCheck | boolean | – | skip the PKGBUILD check() function |
| noContainer | boolean | – | force native build (CLI --no-container) |
| noMakeDeps | boolean | – | skip makedeps installation entirely |
| onlyPkgNames | string | – | csv allowlist of pkg names to build |
| overridePkgRel | string | – | override PKGBUILD pkgrel for all pkgs |
| overridePkgVer | string | – | override PKGBUILD pkgver for all pkgs |
| parallel | boolean | – | run independent build steps in parallel |
| path | string | yes | yap.json file, PKGBUILD file, or dir with either |
| release | string | – | target release; auto-detected when empty |
| sbom | boolean | – | emit CycloneDX+SPDX SBOMs per artifact |
| sbomFormat | string | – | sbom format: cyclonedx, spdx, or both |
| sign | boolean | – | sign produced artifacts |
| signKey | string | – | signing key path |
| signKeyName | string | – | key name embedded in APK signature stream |
| signPassphrase | string | – | passphrase for the signing key |
| skipDeps | null|array | – | pkgs to omit from makedeps |
| skipHashCheck | boolean | – | disable sha verification of sources |
| skipPkgNames | string | – | csv denylist of pkg names to skip |
| skipSyncDeps | boolean | – | skip pkg-manager update before makedeps |
| skipToolchainValidation | boolean | – | skip cross toolchain checks |
| targetArch | string | – | cross target; arm64/amd64 aliases ok |
| toPkgName | string | – | stop build order at this pkg (inclusive) |
| unverifiedRepos | boolean | – | allow apt sources w/o Signed-By |
| verbose | boolean | – | enable verbose logging for the build |
| zap | boolean | – | remove the build dir after a successful build |
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | opaque id; poll via build_status |
| containerImage | string | – | resolved image tag, e.g. ubuntu-jammy |
| containerRuntime | string | – | backend: cli (podman/docker) or rootless |
| distro | string | yes | – |
| inContainer | boolean | – | true when dispatched into a container image |
| path | string | yes | – |
| release | string | yes | – |
| state | string | yes | – |
No examples provided.
build_cancel ~39
Cancel a running yap build by buildID. May leave partial artifacts or stale package-manager locks inside the build container.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| canceled | boolean | yes | – |
No examples provided.
build_logs ~108
Fetch captured stdout+stderr from a build session, with tail/since/grep filters.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | identifier returned by build |
| context | integer | – | with grep: include N lines before/after each match |
| grep | string | – | return only lines matching this Go regexp |
| tail | integer | – | return only the last N lines; 0 = all |
| withLineNo | boolean | – | return per-line {lineno,text} structs alongside log |
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | – |
| bytes | integer | yes | byte count after filtering |
| lines | integer | yes | line count after filtering |
| log | string | yes | filtered log payload |
| numbered | null|array | – | set when withLineNo=true |
| regexpInvalid | boolean | – | true when the grep regexp failed to compile and was ignored |
| state | string | yes | running, succeeded, failed, canceled, or unknown |
No examples provided.
build_status ~31
Return the state of a previously-launched yap build.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | identifier returned by build |
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | – |
| containerImage | string | – | resolved image tag for the dispatch |
| containerRuntime | string | – | container backend: cli or rootless |
| distro | string | – | – |
| endedAt | string | – | – |
| error | string | – | – |
| inContainer | boolean | – | true when running in a yap image |
| logBytes | integer | – | current size of captured log; fetch via build_logs |
| logLines | integer | – | current line count of captured log |
| path | string | – | – |
| release | string | – | – |
| startedAt | string | – | – |
| state | string | yes | running, succeeded, failed, or canceled |
No examples provided.
build_summary ~54
One-shot terminal diagnosis: state, duration, last error line, best-guess failed step, artifact count, and keyword-based hints. Cheaper than fetching full logs.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | identifier returned by build |
| Name | Type | Req | Description |
|---|---|---|---|
| artifactCount | integer | yes | recognised artifacts found in output dir |
| buildID | string | yes | – |
| durationSec | integer | – | – |
| error | string | – | top-level error from the build pipeline |
| failedStep | string | – | phase tag from log: build/strip/package/sign/sbom |
| hints | null|array | – | diagnostic hints inferred from log keywords |
| lastErrorLine | string | – | last log line matching ERROR/FAIL/fatal |
| state | string | yes | running, succeeded, failed, canceled, or unknown |
No examples provided.
build_wait ~66
Block until a build reaches a terminal state or the timeout elapses.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | identifier returned by build |
| timeoutSec | integer | – | max seconds to wait; 0/omitted uses the 50s server cap. Poll again when timedOut=true |
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | yes | – |
| endedAt | string | – | – |
| error | string | – | – |
| startedAt | string | – | – |
| state | string | yes | final state, or 'running' on timeout |
| timedOut | boolean | – | – |
No examples provided.
graph ~61
Build the dependency graph (nodes+edges) for a yap project or single PKGBUILD.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | yap.json file, PKGBUILD file, or dir with either |
| theme | string | – | optional theme passed to loader; cosmetic only |
| Name | Type | Req | Description |
|---|---|---|---|
| edges | null|array | yes | – |
| nodes | null|array | yes | – |
No examples provided.
inspect ~75
Inspect an artifact: format, size, sibling SBOM/signature presence. Accepts any host path the server can stat — there is no project sandboxing; clients should pass paths returned by list_artifacts or known build outputs.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | string | yes | path to a built package (.deb/.rpm/.apk/.pkg.tar.*) |
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | string | yes | – |
| format | string | yes | – |
| hasCycloneDX | boolean | yes | – |
| hasSPDX | boolean | yes | – |
| hasSig | boolean | yes | – |
| sizeBytes | integer | yes | – |
No examples provided.
install ~60
Install a built package artifact on the host. Requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | string | yes | path to a built .deb/.rpm/.apk/.pkg.tar.* artifact |
| confirm | boolean | yes | must be true to perform the install; default refuses |
| Name | Type | Req | Description |
|---|---|---|---|
| artifact | string | yes | – |
| error | string | – | – |
| format | string | yes | – |
| ok | boolean | yes | – |
No examples provided.
list_artifacts ~70
List built package artifacts (.deb/.rpm/.apk/.pkg.tar.*) plus sibling SBOM/sig presence.
| Name | Type | Req | Description |
|---|---|---|---|
| buildID | string | – | build session whose output dir to scan |
| path | string | – | yap.json/PKGBUILD/dir to scan (used when buildID empty) |
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | null|array | yes | – |
| outputDir | string | yes | – |
No examples provided.
list_distros ~22
List supported distributions, their package managers, and known packers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| distros | null|array | yes | distro ids paired with their pkg manager |
| packers | null|array | yes | package managers yap knows how to drive |
| releases | null|array | yes | deprecated alias for distros[*].name |
No examples provided.
list_images ~67
List pre-built yap container image tags from build/deploy/ in the yap source tree. Requires running with repoPath pointing at a yap checkout; end-user installations should pass distros from list_distros instead.
| Name | Type | Req | Description |
|---|---|---|---|
| repoPath | string | – | path to yap source tree; defaults to cwd |
| Name | Type | Req | Description |
|---|---|---|---|
| images | null|array | yes | – |
| repoPath | string | yes | – |
No examples provided.
parse_pkgbuild ~102
Parse a PKGBUILD into structured JSON (name, version, deps, sources, ...).
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | – | distro context for arch/distro-qualified directives |
| path | string | yes | path to a dir containing a PKGBUILD, or to PKGBUILD itself |
| release | string | – | release/codename context; auto-detected when empty |
| targetArch | string | – | target arch for cross-compile; empty for native |
| Name | Type | Req | Description |
|---|---|---|---|
| arch | null|array | – | – |
| codename | string | – | – |
| conflicts | null|array | – | – |
| depends | null|array | – | – |
| distro | string | – | – |
| epoch | string | – | – |
| hashSums | null|array | – | – |
| isSplit | boolean | yes | – |
| license | null|array | – | – |
| makeDepends | null|array | – | – |
| optDepends | null|array | – | – |
| pkgBase | string | – | – |
| pkgDesc | string | yes | – |
| pkgName | string | yes | – |
| pkgNames | null|array | – | – |
| pkgRel | string | yes | – |
| pkgVer | string | yes | – |
| provides | null|array | – | – |
| replaces | null|array | – | – |
| sources | null|array | – | – |
| targetArch | string | – | – |
| url | string | – | – |
No examples provided.
prepare ~97
Prepare the host build environment (toolchain + base makedeps) for a distro.
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | – | distribution name; auto-detected when empty |
| goLang | boolean | – | install Go toolchain |
| release | string | – | release/codename; auto-detected when empty |
| skipSync | boolean | – | skip package-manager update before prerequisites |
| targetArch | string | – | target arch; empty for native |
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | yes | – |
| error | string | – | – |
| ok | boolean | yes | – |
| release | string | yes | – |
No examples provided.
pull ~38
Pull the yap container image for the requested distro.
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | yes | distro tag, e.g. 'ubuntu' or 'ubuntu-noble' |
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | yes | – |
| error | string | – | – |
| ok | boolean | yes | – |
| runtime | string | yes | – |
No examples provided.
resolve_distro ~59
Auto-detect distribution and release from /etc/os-release.
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | – | distro name; auto-detected from /etc/os-release when empty |
| release | string | – | release/codename; auto-detected when matching host |
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | yes | resolved distribution name |
| release | string | yes | resolved release / codename |
No examples provided.
status ~20
Return yap version, build metadata, and runtime/container detection info.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| buildTime | string | yes | RFC3339 build timestamp |
| commit | string | yes | git short commit hash |
| goVersion | string | yes | go runtime version |
| goarch | string | yes | runtime GOARCH |
| goos | string | yes | runtime GOOS |
| inContainer | boolean | yes | true when running inside a container |
| version | string | yes | yap semantic version |
No examples provided.
validate ~58
Validate a PKGBUILD: parse + check mandatory vars + general validation.
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | – | distro context |
| path | string | yes | path to PKGBUILD or its directory |
| release | string | – | release/codename context |
| Name | Type | Req | Description |
|---|---|---|---|
| errors | null|array | – | validation error messages; empty when valid |
| pkg | string | – | resolved package name |
| valid | boolean | yes | true when all mandatory fields are well-formed |
No examples provided.
zap ~114
Deeply clean a yap project's build env and artifacts. Requires confirm: true.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | must be true; zap removes build state and artifacts |
| distro | string | – | distro context; auto-detected when empty |
| fromPkgName | string | – | only clean from this package onward |
| path | string | yes | yap.json file, PKGBUILD file, or dir with either |
| release | string | – | release context |
| toPkgName | string | – | only clean up to this package |
| Name | Type | Req | Description |
|---|---|---|---|
| distro | string | yes | – |
| error | string | – | – |
| ok | boolean | yes | – |
| path | string | yes | – |
| release | string | yes | – |
No examples provided.
How do I install the YAP — Yet Another Packager MCP server?
YAP — Yet Another Packager runs locally as a container image, launched with docker run --rm -i -e YAP_VERBOSE ghcr.io/m0rf30/yap-mcp:2.8.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/m0rf30/yap-mcp
claude mcp add m0rf30-yap -- docker run --rm -i -e YAP_VERBOSE ghcr.io/m0rf30/yap-mcp:2.8.0
This image reads YAP_VERBOSE. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the YAP — Yet Another Packager MCP server?
YAP — Yet Another Packager is an MCP server listed in the public MCP registry as io.github.M0Rf30/yap. Build native Linux packages (.deb/.rpm/.apk/.pkg.tar.zst) from a single PKGBUILD via MCP. This page covers its container image (ghcr.io/m0rf30/yap-mcp).
Is the YAP — Yet Another Packager MCP server safe to use?
YAP — Yet Another Packager scores 50 out of 100 on VerifyMCP. 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 YAP — Yet Another Packager MCP server expose?
YAP — Yet Another Packager exposes 19 tools: build, build_cancel, build_logs, build_status, build_summary, and 14 more. Their descriptions and schemas cost roughly 1,722 tokens of context every time the server is loaded.
Is the YAP — Yet Another Packager MCP server still maintained?
YAP — Yet Another Packager 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.