# Yappy (remote · yappy.biz)

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

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `yappy.biz`: 85/100 (this document), [markdown](https://verifymcp.io/servers/biz-yappy-yappy/yappy.md), [page](https://verifymcp.io/servers/biz-yappy-yappy/yappy)

## Channel facts

- Endpoint: `https://yappy.biz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/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).
  - Tool/resource definitions use about 1224 tokens (~87/item across 14 items; 9 tools + 5 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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).
  - 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 73/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

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

Yappy is a hosted endpoint at https://yappy.biz/mcp, so there is nothing to install locally. 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 --transport http biz-yappy-yappy 'https://yappy.biz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "biz-yappy-yappy": {
      "url": "https://yappy.biz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "biz-yappy-yappy": {
      "type": "http",
      "url": "https://yappy.biz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.biz-yappy-yappy]
url = "https://yappy.biz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "biz-yappy-yappy": {
      "type": "remote",
      "url": "https://yappy.biz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add biz-yappy-yappy --url 'https://yappy.biz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  biz-yappy-yappy:
    url: "https://yappy.biz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "biz-yappy-yappy": {
      "Transport": "http",
      "Url": "https://yappy.biz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add biz-yappy-yappy -t streamable-http -u 'https://yappy.biz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "biz-yappy-yappy": {
      "type": "http",
      "url": "https://yappy.biz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-20 (score 85, +1)

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

### 2026-09-18 (score 84, +1)

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

### 2026-09-16 (score 83, +1)

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

### 2026-09-14 (score 82, +1)

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

### 2026-09-12 (score 81, +1)

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

### 2026-09-10 (score 80, +1)

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

### 2026-09-07 (score 79, +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-09-05 (score 78, +1)

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

## MCP tools (9)

### `get_latest_release` (~103 tokens)

Get the latest Yappy 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 download Yappy.

Input parameters:

- `include_notes` (boolean): Include the release notes prose. Set false when you only need the version and download URL.

### `list_releases` (~65 tokens)

List Yappy 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.

Input parameters:

- `limit` (integer): How many releases to return, newest first.

### `get_pricing_plans` (~97 tokens)

Get Yappy pricing

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.

Input parameters:

- `include_backends` (boolean): Include the per-backend cost table. Set false for just the app and API terms.

### `get_frequently_asked` (~74 tokens)

Get the Yappy FAQ

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.

Input parameters:

- `topic` (string): Return only entries on this topic.

### `get_system_requirements` (~79 tokens)

Get Yappy 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.

Input parameters:

- `permissions_only` (boolean): Return just the macOS permission list, without the hardware requirements.

### `list_product_features` (~92 tokens)

List Yappy 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 dictation tool.

Input parameters:

- `on_device_only` (boolean): Return only the features that run entirely on the user's Mac.

### `create_export_job` (~146 tokens)

Start a Yappy 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 page at a time. It creates a job and nothing else: no user data is touched and nothing can be deleted.

Input parameters:

- `format` (string): The artifact format.
- `idempotency_key` (string): Your own key, so a retry returns the same job instead of starting a second one.
- `resource` (string, required): Which corpus to export.

### `get_export_job` (~69 tokens)

Poll a Yappy 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.

Input parameters:

- `job_id` (string, required): The id returned by create_export_job.

### `check_mac_compatibility` (~112 tokens)

Check whether a Mac can run Yappy

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.

Input parameters:

- `arch` (string, required): The CPU architecture: arm64 for Apple Silicon, x86_64 for Intel.
- `os_version` (string, required): The macOS version on the machine, for example "14.5".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/biz-yappy-yappy/yappy#diagnostics

## Score history

- 2026-09-20: 85
- 2026-09-19: 84
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 82
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 79
- 2026-09-06: 78
- 2026-09-05: 78
- 2026-09-04: 77
- 2026-09-03: 77
- 2026-09-02: 76
- 2026-09-01: 76
- 2026-08-31: 75
- 2026-08-30: 75
- 2026-08-29: 74
- 2026-08-28: 74
- 2026-08-27: 74
- 2026-08-26: 73
- 2026-08-25: 71

## Common questions

### What is the Yappy MCP server?

Yappy is an MCP server listed in the public MCP registry as biz.yappy/yappy. Yappy for macOS (yappy.biz): release, pricing, features, requirements, Mac compatibility. This page covers its hosted endpoint (https://yappy.biz/mcp).

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

Yappy scores 85 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 Yappy MCP server expose?

Yappy exposes 9 tools: get_latest_release, list_releases, get_pricing_plans, get_frequently_asked, get_system_requirements, and 4 more. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.

### Does the Yappy MCP server require authentication?

No. We connected to Yappy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Yappy MCP server still maintained?

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

## Links

- Remote endpoint: https://yappy.biz/mcp
- Website: https://yappy.biz/
- Changelog RSS feed: https://verifymcp.io/servers/biz-yappy-yappy/yappy.xml
- Changelog JSON feed: https://verifymcp.io/servers/biz-yappy-yappy/yappy.json
- HTML version of this page: https://verifymcp.io/servers/biz-yappy-yappy/yappy