# Yappy

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

- name: biz.yappy/yappy
- version: 1.0.1
- connection class: R0 (autonomous)
- trust: 79/100 flags: no-repository
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/biz.yappy%2Fyappy
- tools: https://api.protogrid.dev/v1/servers/biz.yappy%2Fyappy/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 99
- freshness: 85
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-97% ~updated-56d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 9 of 9 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,512 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 9, about 1,512 tokens to load them all
- tool set hash: 0f73b33662db61424012fd4f28195611
- badge: [![protogrid quality](https://protogrid.dev/badge/biz.yappy/yappy.svg)](https://protogrid.dev/servers/biz.yappy/yappy)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://yappy.biz/mcp (streamable-http, auth none, reachable true, uptime30d 0.974359)

## Packages

_none_

## Tools (9)

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