Yappy
REMOTE · YAPPY.BIZ
Yappy for macOS (yappy.biz): release, pricing, features, requirements, Mac compatibility.
Available components
Last scanned (7 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1224 tokens (~87/item across 14 items; 9 tools + 5 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
First indexed and scored.
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 · Probed https://yappy.biz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yappy.biz | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1909d3ad2e25caf6133e9e6fa5ee8979 |
| SANs: yappy.biz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of yappy.biz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| biz. | present | 13117 | 13 | Verified |
| yappy.biz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://yappy.biz/mcp | Verified | 200 | |
| http (plaintext) | http://yappy.biz/mcp | HTTPS enforced | 301 | https://yappy.biz/mcp |
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 →
check_mac_compatibility Check whether a Mac can run Yappy ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arch | string | yes | The CPU architecture: arm64 for Apple Silicon, x86_64 for Intel. |
| os_version | string | yes | The macOS version on the machine, for example "14.5". |
No output schema declared.
No examples provided.
create_export_job Start a Yappy export job ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Which corpus to export. |
No output schema declared.
No examples provided.
get_export_job Poll a Yappy export job ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The id returned by create_export_job. |
No output schema declared.
No examples provided.
get_frequently_asked Get the Yappy FAQ ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | Return only entries on this topic. |
No output schema declared.
No examples provided.
get_latest_release Get the latest Yappy release ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_notes | boolean | – | Include the release notes prose. Set false when you only need the version and download URL. |
No output schema declared.
No examples provided.
get_pricing_plans Get Yappy pricing ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_backends | boolean | – | Include the per-backend cost table. Set false for just the app and API terms. |
No output schema declared.
No examples provided.
get_system_requirements Get Yappy system requirements ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| permissions_only | boolean | – | Return just the macOS permission list, without the hardware requirements. |
No output schema declared.
No examples provided.
list_product_features List Yappy features ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| on_device_only | boolean | – | Return only the features that run entirely on the user's Mac. |
No output schema declared.
No examples provided.
list_releases List Yappy releases ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many releases to return, newest first. |
No output schema declared.
No examples provided.
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.
remote · yappy.biz
claude mcp add --transport http biz-yappy-yappy 'https://yappy.biz/mcp'
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 86 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.