# YAML Workflow (pypi · yaml-workflow)

Expose declarative YAML-defined workflows as MCP tools over stdio

- Trust score: 37/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-23

## Components

- pypi · `yaml-workflow`: 37/100 (this document), [markdown](https://verifymcp.io/servers/orieg-yaml-workflow/yaml-workflow.md), [page](https://verifymcp.io/servers/orieg-yaml-workflow/yaml-workflow)

## Channel facts

- Registry: `pypi`
- Package: `yaml-workflow`
- Version: `0.9.6`
- 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-08-23.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 35/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (MIT License) isn't a recognized OSI-approved license.
  - Actively maintained (last published 5 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

**Unverified: 4 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the YAML Workflow MCP server?

YAML Workflow runs locally as a PyPI package, launched with uvx yaml-workflow. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add orieg-yaml-workflow -- uvx yaml-workflow
```

### Cursor

```json
{
  "mcpServers": {
    "orieg-yaml-workflow": {
      "command": "uvx",
      "args": [
        "yaml-workflow"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "orieg-yaml-workflow": {
      "command": "uvx",
      "args": [
        "yaml-workflow"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add orieg-yaml-workflow -- uvx yaml-workflow
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "orieg-yaml-workflow": {
      "type": "local",
      "command": [
        "uvx",
        "yaml-workflow"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add orieg-yaml-workflow --command uvx --arg yaml-workflow
```

### Hermes

```yaml
mcp_servers:
  orieg-yaml-workflow:
    command: "uvx"
    args: ["yaml-workflow"]
```

### Netclaw

```json
{
  "McpServers": {
    "orieg-yaml-workflow": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "yaml-workflow"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add orieg-yaml-workflow -t stdio -c uvx -a yaml-workflow
```

### Other

```json
{
  "mcpServers": {
    "orieg-yaml-workflow": {
      "command": "uvx",
      "args": [
        "yaml-workflow"
      ]
    }
  }
}
```

## 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-08-23 (score 37, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-21 (score 22, −15)

- [security regression] Malware scan: pass → unverified

### 2026-08-20 (score 37, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-08-19 (score 22, +15)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Install scripts: unverified → pass
- [security] Provenance: Provenance check failed: no build-provenance attestation is published.
- [security] The scripts that run when this package is installed changed: build_backend
- [functional improvement] Dependency health: unverified → 1.00
- [functional] License: License check failed: the license (MIT License) isn't a recognized OSI-approved license.
- [functional] Licence: MIT License

### 2026-08-17 (score 7, −30)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [security regression] Install scripts: pass → unverified
- [security] Provenance: Provenance check failed: the declared version isn't published, so its provenance can't be verified.
- [security] The scripts that run when this package is installed changed: build_backend
- [functional regression] Dependency health: 1.00 → unverified
- [functional] License: License check failed: no license is declared.
- [functional] Licence: MIT License
- [functional] Package version: 0.9.4 → 0.9.6
- [functional] Package version: 0.9.4 → 0.9.5

### 2026-08-15 (score 37)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/orieg-yaml-workflow/yaml-workflow#diagnostics

## Score history

- 2026-08-23: 37
- 2026-08-22: 22
- 2026-08-21: 22
- 2026-08-20: 37
- 2026-08-19: 22
- 2026-08-18: 7
- 2026-08-17: 7
- 2026-08-16: 37
- 2026-08-15: 37

## Common questions

### What is the YAML Workflow MCP server?

YAML Workflow is an MCP server listed in the public MCP registry as io.github.orieg/yaml-workflow. Expose declarative YAML-defined workflows as MCP tools over stdio. This page covers its PyPI package (yaml-workflow).

### Is the YAML Workflow MCP server safe to use?

YAML Workflow scores 37 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 August 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.

### Is the YAML Workflow MCP server still maintained?

YAML Workflow is still listed as active in the MCP registry. We last reached this channel on 23 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- PyPI project: https://pypi.org/project/yaml-workflow/
- Socket report: https://socket.dev/pypi/package/yaml-workflow
- Repository: https://github.com/orieg/yaml-workflow
- Changelog RSS feed: https://verifymcp.io/servers/orieg-yaml-workflow/yaml-workflow.xml
- Changelog JSON feed: https://verifymcp.io/servers/orieg-yaml-workflow/yaml-workflow.json
- HTML version of this page: https://verifymcp.io/servers/orieg-yaml-workflow/yaml-workflow