Yappy documentation
REMOTE · YAPPY.BIZ · SCANNED SEP 22
Yappy macOS docs (yappy.biz): setup, permissions, LLM backends, troubleshooting.
Available components
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 608 tokens (~50/item across 12 items; 3 tools + 9 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Yappy documentation MCP server?
Yappy documentation is a hosted endpoint at https://yappy.biz/docs/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-docs 'https://yappy.biz/docs/mcp'
{
"mcpServers": {
"biz-yappy-yappy-docs": {
"url": "https://yappy.biz/docs/mcp"
}
}
} {
"servers": {
"biz-yappy-yappy-docs": {
"type": "http",
"url": "https://yappy.biz/docs/mcp"
}
}
} [mcp_servers.biz-yappy-yappy-docs] url = "https://yappy.biz/docs/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"biz-yappy-yappy-docs": {
"type": "remote",
"url": "https://yappy.biz/docs/mcp",
"enabled": true
}
}
} openclaw mcp add biz-yappy-yappy-docs --url 'https://yappy.biz/docs/mcp' --transport streamable-http
mcp_servers:
biz-yappy-yappy-docs:
url: "https://yappy.biz/docs/mcp" {
"McpServers": {
"biz-yappy-yappy-docs": {
"Transport": "http",
"Url": "https://yappy.biz/docs/mcp"
}
}
} assistant mcp add biz-yappy-yappy-docs -t streamable-http -u 'https://yappy.biz/docs/mcp'
{
"mcpServers": {
"biz-yappy-yappy-docs": {
"type": "http",
"url": "https://yappy.biz/docs/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +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.
- 17 Sept 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 Sept 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Probed https://yappy.biz/docs/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 | 11044 | 8 | 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/docs/mcp | Verified | 200 | |
| http (plaintext) | http://yappy.biz/docs/mcp | HTTPS enforced | 301 | https://yappy.biz/docs/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 →
get_documentation_page Read a Yappy documentation page ~65
Fetch one full Yappy documentation page as markdown, by slug. Use this after search_documentation when an excerpt is not enough and you need the whole page — for example the complete configuration reference or the full privacy model.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Which page to fetch. |
No output schema declared.
No examples provided.
list_documentation_pages List Yappy documentation pages ~66
List every page in the Yappy documentation with its slug, title, and one-line summary, so you can pick the right one to read instead of guessing a slug.
| Name | Type | Req | Description |
|---|---|---|---|
| include_summaries | boolean | – | Include each page's one-line summary alongside its slug and title. |
No output schema declared.
No examples provided.
search_documentation Search Yappy documentation ~120
Full-text search across Yappy documentation and FAQ. Use this to answer how-to and troubleshooting questions: installing Yappy, granting macOS permissions, a hotkey that does nothing, choosing an LLM backend, configuration keys, personas, or exactly what stays on-device. Results carry an excerpt you can quote and a URL you can cite.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results to return. |
| query | string | yes | What to search for, in plain words. |
| type | string | – | Narrow the search to documentation pages or FAQ entries. |
No output schema declared.
No examples provided.
What is the Yappy documentation MCP server?
Yappy documentation is an MCP server listed in the public MCP registry as biz.yappy/yappy-docs. Yappy macOS docs (yappy.biz): setup, permissions, LLM backends, troubleshooting. This page covers its hosted endpoint (https://yappy.biz/docs/mcp).
Is the Yappy documentation MCP server safe to use?
Yappy documentation 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 documentation MCP server expose?
Yappy documentation exposes 3 tools: search_documentation, get_documentation_page, list_documentation_pages. Their descriptions and schemas cost roughly 251 tokens of context every time the server is loaded.
Does the Yappy documentation MCP server require authentication?
No. We connected to Yappy documentation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Yappy documentation MCP server still maintained?
Yappy documentation is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.