Node.js/TypeScript MCP server for Atlassian Confluence. Provides tools enabling AI systems (LLMs) to list/get spaces & pages (content
Nothing to run from here
Yappy is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Yappy for macOS (yappy.biz): release, pricing, features, requirements, Mac compatibility.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http yappy-mcp https://yappy.biz/mcp
# 2 — ask your agent for something these tools do
# get_latest_release, list_releases, get_pricing_plans and 6 more
Yappy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
YAAll 2 servers
yappy2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http yappy-mcp https://yappy.biz/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_notes | boolean | no | Include the release notes prose. Set false when you only need the version and download URL. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many releases to return, newest first. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_backends | boolean | no | Include the per-backend cost table. Set false for just the app and API terms. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Return only entries on this topic. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| permissions_only | boolean | no | Return just the macOS permission list, without the hardware requirements. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| on_device_only | boolean | no | Return only the features that run entirely on the user's Mac. |
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 delete
| Parameter | Type | Required | Notes |
|---|---|---|---|
| resource | string | yes | Which corpus to export. |
| format | string | no | The artifact format. |
| idempotency_key | string | no | Your own key, so a retry returns the same job instead of starting a second one. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | The id returned by create_export_job. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| os_version | string | yes | The macOS version on the machine, for example "14.5". |
| arch | string | yes | The CPU architecture: arm64 for Apple Silicon, x86_64 for Intel. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Yappy or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest80d633caa6a78976b4ed1d46f9da031768740980212d718478bee006a70c8edc
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_latest_release | untrusted-input | untrusted-input: keyword "download", declares openWorldHint: true (interacts with entities outside the server) |
| list_releases | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_pricing_plans | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_frequently_asked | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_system_requirements | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_product_features | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| create_export_job | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_export_job | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_mac_compatibility | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest80d633caa6a78976
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Yappy can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.