Yappy documentation MCP server
biz.yappy/yappy-docsyappy.bizstreamable-httpv1.0.1Scanned
Yappy macOS docs (yappy.biz): setup, permissions, LLM backends, troubleshooting.
3 tools: 3 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Yappy documentation MCP server can do
The Yappy documentation MCP server is published by yappy.biz, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools bring in text other people can write (search_documentation, get_documentation_page and list_documentation_pages).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
get_documentation_pageFetch one full Yappy documentation page as markdown, by slug.Reads text others writeNo findings
Why it is in this group
- The name "get_documentation_page" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Read a Yappy documentation page
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_documentation_pagesList 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.Reads text others writeNo findings
Why it is in this group
- The name "list_documentation_pages" says "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: List Yappy documentation pages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
search_documentationFull-text search across Yappy documentation and FAQ.Reads text others writeNo findings
Why it is in this group
- The name "search_documentation" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search Yappy documentation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:31 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://yappy.biz/.well-known/oauth-protected-resource
- Authorization servers
- https://yappy.biz
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http yappy-docs https://yappy.biz/docs/mcpclaude mcp add --transport http yappy-docs https://yappy.biz/docs/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__yappy-docs__search_documentation",
"mcp__yappy-docs__get_documentation_page",
"mcp__yappy-docs__list_documentation_pages"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as yappy-docs. Review it before you use it.
Capability tags behind 3 rules
- mcp__yappy-docs__search_documentation untrusted-input
- mcp__yappy-docs__get_documentation_page untrusted-input
- mcp__yappy-docs__list_documentation_pages untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/biz.yappy/yappy-docs/verify?hash=c6fde49b264fb78d9c48ad8da54d4d68071db6076426e4b216aaece245396c28" | jq -e '.changed == false'Pinned hash c6fde49b264f, from Nov 12, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/biz.yappy/yappy-docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/biz.yappy/yappy-docs)Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.
Yappy documentation MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Yappy documentation MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Yappy documentation MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Yappy documentation MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Yappy documentation MCP server have?
- 3 tools: 3 read. search_documentation, get_documentation_page and list_documentation_pages.
Does the Yappy documentation MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Yappy documentation MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Yappy documentation MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.