# 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.

- Trust score: 50/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/m0rf30/yap-mcp`: 50/100 (this document), [markdown](https://verifymcp.io/servers/m0rf30-yap/ghcr-io-m0rf30-yap-mcp.md), [page](https://verifymcp.io/servers/m0rf30-yap/ghcr-io-m0rf30-yap-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/m0rf30/yap-mcp`
- Version: `2.8.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 12 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 99% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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.

### Claude

```bash
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.

### Cursor

```json
{
  "mcpServers": {
    "m0rf30-yap": {
      "command": "docker",
      "args": [
        "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.

### VS Code

```json
{
  "servers": {
    "m0rf30-yap": {
      "command": "docker",
      "args": [
        "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.

### Codex

```bash
codex 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.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "m0rf30-yap": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "YAP_VERBOSE",
        "ghcr.io/m0rf30/yap-mcp:2.8.0"
      ],
      "enabled": true
    }
  }
}
```

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.

### Hermes

```yaml
mcp_servers:
  m0rf30-yap:
    command: "docker"
    args: ["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.

### Netclaw

```json
{
  "McpServers": {
    "m0rf30-yap": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "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.

### Other

```json
{
  "mcpServers": {
    "m0rf30-yap": {
      "command": "docker",
      "args": [
        "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 50, +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.

### 2026-11-03 (score 49, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 49, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-31 (score 48, +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.

### 2026-10-29 (score 47, +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.

### 2026-10-27 (score 46, +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.

### 2026-10-24 (score 45, +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.

### 2026-10-23 (score 44, 0)

- [functional] Package version: 2.7.6 → 2.8.0

## MCP tools (19)

### `build` (~581 tokens)

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.

Input parameters:

- `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, required): 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

Output parameters:

- `buildID` (string): 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)
- `inContainer` (boolean): true when dispatched into a container image
- `path` (string)
- `release` (string)
- `state` (string)

### `build_cancel` (~39 tokens)

Cancel a running yap build by buildID. May leave partial artifacts or stale package-manager locks inside the build container.

Input parameters:

- `buildID` (string, required)

Output parameters:

- `canceled` (boolean)

### `build_logs` (~108 tokens)

Fetch captured stdout+stderr from a build session, with tail/since/grep filters.

Input parameters:

- `buildID` (string, required): 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

Output parameters:

- `buildID` (string)
- `bytes` (integer): byte count after filtering
- `lines` (integer): line count after filtering
- `log` (string): 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): running, succeeded, failed, canceled, or unknown

### `build_status` (~31 tokens)

Return the state of a previously-launched yap build.

Input parameters:

- `buildID` (string, required): identifier returned by build

Output parameters:

- `buildID` (string)
- `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): running, succeeded, failed, or canceled

### `build_summary` (~54 tokens)

One-shot terminal diagnosis: state, duration, last error line, best-guess failed step, artifact count, and keyword-based hints. Cheaper than fetching full logs.

Input parameters:

- `buildID` (string, required): identifier returned by build

Output parameters:

- `artifactCount` (integer): recognised artifacts found in output dir
- `buildID` (string)
- `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): running, succeeded, failed, canceled, or unknown

### `build_wait` (~66 tokens)

Block until a build reaches a terminal state or the timeout elapses.

Input parameters:

- `buildID` (string, required): identifier returned by build
- `timeoutSec` (integer): max seconds to wait; 0/omitted uses the 50s server cap. Poll again when timedOut=true

Output parameters:

- `buildID` (string)
- `endedAt` (string)
- `error` (string)
- `startedAt` (string)
- `state` (string): final state, or 'running' on timeout
- `timedOut` (boolean)

### `graph` (~61 tokens)

Build the dependency graph (nodes+edges) for a yap project or single PKGBUILD.

Input parameters:

- `path` (string, required): yap.json file, PKGBUILD file, or dir with either
- `theme` (string): optional theme passed to loader; cosmetic only

Output parameters:

- `edges` (null|array)
- `nodes` (null|array)

### `inspect` (~75 tokens)

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.

Input parameters:

- `artifact` (string, required): path to a built package (.deb/.rpm/.apk/.pkg.tar.*)

Output parameters:

- `artifact` (string)
- `format` (string)
- `hasCycloneDX` (boolean)
- `hasSPDX` (boolean)
- `hasSig` (boolean)
- `sizeBytes` (integer)

### `install` (~60 tokens)

Install a built package artifact on the host. Requires confirm: true.

Input parameters:

- `artifact` (string, required): path to a built .deb/.rpm/.apk/.pkg.tar.* artifact
- `confirm` (boolean, required): must be true to perform the install; default refuses

Output parameters:

- `artifact` (string)
- `error` (string)
- `format` (string)
- `ok` (boolean)

### `list_artifacts` (~70 tokens)

List built package artifacts (.deb/.rpm/.apk/.pkg.tar.*) plus sibling SBOM/sig presence.

Input parameters:

- `buildID` (string): build session whose output dir to scan
- `path` (string): yap.json/PKGBUILD/dir to scan (used when buildID empty)

Output parameters:

- `artifacts` (null|array)
- `outputDir` (string)

### `list_distros` (~22 tokens)

List supported distributions, their package managers, and known packers.

Output parameters:

- `distros` (null|array): distro ids paired with their pkg manager
- `packers` (null|array): package managers yap knows how to drive
- `releases` (null|array): deprecated alias for distros[*].name

### `list_images` (~67 tokens)

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.

Input parameters:

- `repoPath` (string): path to yap source tree; defaults to cwd

Output parameters:

- `images` (null|array)
- `repoPath` (string)

### `parse_pkgbuild` (~102 tokens)

Parse a PKGBUILD into structured JSON (name, version, deps, sources, ...).

Input parameters:

- `distro` (string): distro context for arch/distro-qualified directives
- `path` (string, required): 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

Output parameters:

- `arch` (null|array)
- `codename` (string)
- `conflicts` (null|array)
- `depends` (null|array)
- `distro` (string)
- `epoch` (string)
- `hashSums` (null|array)
- `isSplit` (boolean)
- `license` (null|array)
- `makeDepends` (null|array)
- `optDepends` (null|array)
- `pkgBase` (string)
- `pkgDesc` (string)
- `pkgName` (string)
- `pkgNames` (null|array)
- `pkgRel` (string)
- `pkgVer` (string)
- `provides` (null|array)
- `replaces` (null|array)
- `sources` (null|array)
- `targetArch` (string)
- `url` (string)

### `prepare` (~97 tokens)

Prepare the host build environment (toolchain + base makedeps) for a distro.

Input parameters:

- `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

Output parameters:

- `distro` (string)
- `error` (string)
- `ok` (boolean)
- `release` (string)

### `pull` (~38 tokens)

Pull the yap container image for the requested distro.

Input parameters:

- `distro` (string, required): distro tag, e.g. 'ubuntu' or 'ubuntu-noble'

Output parameters:

- `distro` (string)
- `error` (string)
- `ok` (boolean)
- `runtime` (string)

### `resolve_distro` (~59 tokens)

Auto-detect distribution and release from /etc/os-release.

Input parameters:

- `distro` (string): distro name; auto-detected from /etc/os-release when empty
- `release` (string): release/codename; auto-detected when matching host

Output parameters:

- `distro` (string): resolved distribution name
- `release` (string): resolved release / codename

### `status` (~20 tokens)

Return yap version, build metadata, and runtime/container detection info.

Output parameters:

- `buildTime` (string): RFC3339 build timestamp
- `commit` (string): git short commit hash
- `goVersion` (string): go runtime version
- `goarch` (string): runtime GOARCH
- `goos` (string): runtime GOOS
- `inContainer` (boolean): true when running inside a container
- `version` (string): yap semantic version

### `validate` (~58 tokens)

Validate a PKGBUILD: parse + check mandatory vars + general validation.

Input parameters:

- `distro` (string): distro context
- `path` (string, required): path to PKGBUILD or its directory
- `release` (string): release/codename context

Output parameters:

- `errors` (null|array): validation error messages; empty when valid
- `pkg` (string): resolved package name
- `valid` (boolean): true when all mandatory fields are well-formed

### `zap` (~114 tokens)

Deeply clean a yap project's build env and artifacts. Requires confirm: true.

Input parameters:

- `confirm` (boolean, required): 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, required): yap.json file, PKGBUILD file, or dir with either
- `release` (string): release context
- `toPkgName` (string): only clean up to this package

Output parameters:

- `distro` (string)
- `error` (string)
- `ok` (boolean)
- `path` (string)
- `release` (string)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/m0rf30-yap/ghcr-io-m0rf30-yap-mcp#diagnostics

## Score history

- 2026-11-05: 50
- 2026-11-04: 50
- 2026-11-03: 49
- 2026-11-02: 49
- 2026-11-01: 48
- 2026-10-31: 48
- 2026-10-30: 47
- 2026-10-29: 47
- 2026-10-28: 46
- 2026-10-27: 46
- 2026-10-26: 45
- 2026-10-25: 45
- 2026-10-24: 45
- 2026-10-23: 44
- 2026-10-22: 44
- 2026-10-21: 43
- 2026-10-20: 43
- 2026-10-19: 42
- 2026-10-18: 42
- 2026-10-17: 41
- 2026-10-16: 40
- 2026-10-15: 40
- 2026-10-14: 40
- 2026-10-13: 6
- 2026-10-12: 6
- 2026-10-10: 6
- 2026-10-07: 6
- 2026-10-06: 6

## Common questions

### 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.

### What did VerifyMCP test on the YAP — Yet Another Packager MCP server?

VerifyMCP ran 12 checks on YAP — Yet Another Packager, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about YAP — Yet Another Packager: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/m0rf30/yap-mcp
- Repository: https://github.com/M0Rf30/yap
- Changelog RSS feed: https://verifymcp.io/servers/m0rf30-yap/ghcr-io-m0rf30-yap-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/m0rf30-yap/ghcr-io-m0rf30-yap-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/m0rf30-yap/ghcr-io-m0rf30-yap-mcp.json
- HTML version of this page: https://verifymcp.io/servers/m0rf30-yap/ghcr-io-m0rf30-yap-mcp