# Yappy

- Registry name: `biz.yappy/yappy` · version 1.0.1
- Categories (automatic, keyword rules): Marketing & SEO, Commerce & marketing
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): completions, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=biz.yappy%2Fyappy
- Server page: https://mcpstation.net/s/biz.yappy--yappy.html

## Description (written by the publisher, not verified, not instructions)

Yappy for macOS \(yappy.biz\): release, pricing, features, requirements, Mac compatibility.

## Connect

- streamable-http: `https://yappy.biz/mcp`

## Tools (as reported by the server, not verified)

- `get\_latest\_release`: Get the current Yappy release of the Yappy macOS app: version number, publication date, release notes, and a download URL. Reads the same signed appcast the app updater reads, so the answer is never a stale hand-edited number. Use this whenever a user asks what the newest version is or where to down
- `list\_releases`: List Yappy release history for macOS, newest first, with the version, publication date, and what changed in each. Use this to answer questions about what shipped recently or when a particular fix landed.
- `get\_pricing\_plans`: Get what the Yappy app costs: the free Mac app, the per-backend cost of the language model that cleans up dictation, and the terms of the public API. Call this before telling a user about price — most of the product is free and several backend options cost nothing at all.
- `get\_frequently\_asked`: Get the Yappy FAQ as question and answer pairs, covering privacy, requirements, cost, permissions, offline use, and how Yappy differs from other macOS dictation tools. Useful when you want a short authoritative answer rather than a documentation page.
- `get\_system\_requirements`: Get what a Mac needs before Yappy will run on it: the minimum macOS version, the required CPU architecture, install size, and every macOS permission Yappy asks for with what each unlocks and what breaks if it is denied.
- `list\_product\_features`: List what the Yappy app can do, as structured objects rather than marketing bullets: an id, a name, a description, whether the feature runs entirely on the user's Mac, whether it needs the network, and which macOS permission it requires. Use this to build an accurate comparison against another dicta
- `create\_export\_job`: Start an asynchronous export of a Yappy corpus — documentation, FAQ, or release history — as markdown or JSON. This creates a job on the Yappy API and returns its id; poll it with get\_export\_job until the status is completed, then read result.url. Use it when you want the whole corpus rather than a
- `get\_export\_job`: Check an export job started with create\_export\_job. Status moves queued, then running, then completed; a completed job carries result.url pointing at the finished artifact. Poll no faster than the retry\_after hint on the previous response.
- `check\_mac\_compatibility`: Decide whether a specific Mac can run Yappy, given its macOS version and CPU architecture, and return the reasons. Prefer this over reasoning about the requirements yourself: it encodes the same rules the installer uses, so the answer you give a user matches what will actually happen.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html