# Yaps (mcpb · yaps-mcp-2.0.1.mcpb)

Transcription, subtitles, meeting transcripts, translation, audio conversion, and private memory.

- Trust score: 63/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `yaps-mcp-2.0.1.mcpb`: 63/100 (this document), [markdown](https://verifymcp.io/servers/richawo-yaps/https-github-com-richawo-yaps-mcp-releases-download-v2-0-1-yaps-mcp-2-0-1-mcpb.md), [page](https://verifymcp.io/servers/richawo-yaps/https-github-com-richawo-yaps-mcp-releases-download-v2-0-1-yaps-mcp-2-0-1-mcpb)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/richawo/yaps-mcp/releases/download/v2.0.1/yaps-mcp-2.0.1.mcpb`
- 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**: 23/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 were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 99 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 659 tokens (~82/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Yaps MCP server?

Yaps ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.

- Download bundle: `https://github.com/richawo/yaps-mcp/releases/download/v2.0.1/yaps-mcp-2.0.1.mcpb`

## 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-10-31 (score 63, 0)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 63, 0)

- [functional] Stability: pass → 0.97

### 2026-10-24 (score 63, 0)

- [security] Stability: 0.97 → pass

### 2026-10-23 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

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

## MCP tools (8)

### `yaps_connector_status` (~40 tokens)

Check Yaps connector

Check whether the local Yaps app, CLI, Memory server, sign-in, and account access are ready. Returns no email address or billing identifiers.

### `yaps_features_list` (~24 tokens)

List Yaps features

List local Yaps feature and model readiness without installing or downloading anything.

### `yaps_transcribe_media` (~78 tokens)

Transcribe audio or video

Transcribe one local audio or video file with Yaps and create a new plain-text transcript. Existing files are never replaced.

Input parameters:

- `output_path` (string): Optional absolute destination ending in .txt. Defaults beside the source as '<name> Transcript.txt'.
- `source_path` (string, required): Absolute path to the audio or video file.

### `yaps_generate_subtitles` (~82 tokens)

Generate SRT subtitles

Generate a new timestamped SRT subtitle file from one local audio or video file with Yaps. Existing files are never replaced.

Input parameters:

- `output_path` (string): Optional absolute destination ending in .srt. Defaults beside the source as '<name> Subtitles.srt'.
- `source_path` (string, required): Absolute path to the audio or video file.

### `yaps_transcribe_meeting` (~95 tokens)

Transcribe meeting with speakers

Create a local Yaps meeting transcript with speaker-labelled segments from one audio or video recording.

Input parameters:

- `engine` (string): Use auto unless the user explicitly requests another installed engine.
- `source_path` (string, required): Absolute path to the meeting recording.
- `speakers` (integer): Optional expected speaker count for Sherpa. Omit for MOSS.
- `title` (string): Optional meeting title saved in Yaps.

### `yaps_translate_text` (~75 tokens)

Translate text locally

Translate supplied text with the installed local Yaps translation engine without a hosted translation API.

Input parameters:

- `source_language` (string): Optional source language code when automatic detection is unsuitable.
- `target_language` (string, required): Target language code such as fr, de, es, or ja.
- `text` (string, required): Text to translate.

### `yaps_translate_file` (~121 tokens)

Translate file locally

Translate a local Markdown, text, or SRT file with Yaps and create a new file while preserving the source.

Input parameters:

- `output_path` (string): Optional absolute destination. Defaults beside the source as '<name>.<target-language>.<extension>'.
- `source_language` (string): Optional source language code when automatic detection is unsuitable.
- `source_path` (string, required): Absolute path to a .md, .txt, or .srt file.
- `target_language` (string, required): Target language code such as fr, de, es, or ja.

### `yaps_extract_audio` (~86 tokens)

Extract audio from video

Create an MP3, WAV, or M4A audio-only copy of a local video using deterministic local media conversion, not AI media generation.

Input parameters:

- `format` (string): Audio output format.
- `output_path` (string): Optional absolute destination. Defaults beside the source as '<name> Audio.<format>'.
- `source_path` (string, required): Absolute path to the source video.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/richawo-yaps/https-github-com-richawo-yaps-mcp-releases-download-v2-0-1-yaps-mcp-2-0-1-mcpb#diagnostics

## Score history

- 2026-11-05: 63
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 63
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 63
- 2026-10-29: 63
- 2026-10-28: 63
- 2026-10-27: 63
- 2026-10-26: 63
- 2026-10-25: 63
- 2026-10-24: 63
- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 62
- 2026-10-20: 61
- 2026-10-19: 61
- 2026-10-18: 60
- 2026-10-17: 60
- 2026-10-16: 59
- 2026-10-15: 59
- 2026-10-14: 58
- 2026-10-13: 58
- 2026-10-12: 57
- 2026-10-10: 57
- 2026-10-07: 55
- 2026-10-04: 54
- 2026-10-03: 53
- 2026-10-02: 53

## Common questions

### What is the Yaps MCP server?

Yaps is an MCP server listed in the public MCP registry as io.github.richawo/yaps. Transcription, subtitles, meeting transcripts, translation, audio conversion, and private memory. This page covers its MCPB bundle (https://github.com/richawo/yaps-mcp/releases/download/v2.0.1/yaps-mcp-2.0.1.mcpb).

### Is the Yaps MCP server safe to use?

Yaps scores 63 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 Yaps MCP server expose?

Yaps exposes 8 tools: yaps_connector_status, yaps_features_list, yaps_transcribe_media, yaps_generate_subtitles, yaps_transcribe_meeting, and 3 more. Their descriptions and schemas cost roughly 601 tokens of context every time the server is loaded.

### What licence is the Yaps MCP server under?

Yaps declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/richawo/yaps-mcp
- Changelog RSS feed: https://verifymcp.io/servers/richawo-yaps/https-github-com-richawo-yaps-mcp-releases-download-v2-0-1-yaps-mcp-2-0-1-mcpb.xml
- Changelog JSON feed: https://verifymcp.io/servers/richawo-yaps/https-github-com-richawo-yaps-mcp-releases-download-v2-0-1-yaps-mcp-2-0-1-mcpb.json
- HTML version of this page: https://verifymcp.io/servers/richawo-yaps/https-github-com-richawo-yaps-mcp-releases-download-v2-0-1-yaps-mcp-2-0-1-mcpb