Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Yaps

MCPB · YAPS-MCP-2.0.1.MCPB

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

0 this week 63 Trust /100

Last scanned (26 minutes ago)

Scores higher than 98% of MCPB servers

Category Documents and Files

Trust breakdown (7 categories)

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 Security23
  • 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 were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 99 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 659 tokens (~82/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 31 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 0
    • Stability: 0.97 → pass security
  • 23 Oct 26 +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.

  • 21 Oct 26 +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.

  • 19 Oct 26 +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.

  • 17 Oct 26 +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.

  • 15 Oct 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.

Diagnostics

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 mcpb/https://github.com/richawo/yaps-mcp/releases/download/v2.0.1/yaps-mcp-2.0.1.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~601 tokens

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 →

Tool Tokens
yaps_connector_status ~40

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

yaps_extract_audio ~86

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

NameTypeReqDescription
formatstring–Audio output format.
output_pathstring–Optional absolute destination. Defaults beside the source as '<name> Audio.<format>'.
source_pathstringyesAbsolute path to the source video.

No output schema declared.

No examples provided.

yaps_features_list ~24

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

yaps_generate_subtitles ~82

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

NameTypeReqDescription
output_pathstring–Optional absolute destination ending in .srt. Defaults beside the source as '<name> Subtitles.srt'.
source_pathstringyesAbsolute path to the audio or video file.

No output schema declared.

No examples provided.

yaps_transcribe_media ~78

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

NameTypeReqDescription
output_pathstring–Optional absolute destination ending in .txt. Defaults beside the source as '<name> Transcript.txt'.
source_pathstringyesAbsolute path to the audio or video file.

No output schema declared.

No examples provided.

yaps_transcribe_meeting ~95

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

NameTypeReqDescription
enginestring–Use auto unless the user explicitly requests another installed engine.
source_pathstringyesAbsolute path to the meeting recording.
speakersinteger–Optional expected speaker count for Sherpa. Omit for MOSS.
titlestring–Optional meeting title saved in Yaps.

No output schema declared.

No examples provided.

yaps_translate_file ~121

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

NameTypeReqDescription
output_pathstring–Optional absolute destination. Defaults beside the source as '<name>.<target-language>.<extension>'.
source_languagestring–Optional source language code when automatic detection is unsuitable.
source_pathstringyesAbsolute path to a .md, .txt, or .srt file.
target_languagestringyesTarget language code such as fr, de, es, or ja.

No output schema declared.

No examples provided.

yaps_translate_text ~75

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

NameTypeReqDescription
source_languagestring–Optional source language code when automatic detection is unsuitable.
target_languagestringyesTarget language code such as fr, de, es, or ja.
textstringyesText to translate.

No output schema declared.

No examples provided.

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.

mcpb · yaps-mcp-2.0.1.mcpb

Download bundle

The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.

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.