ai.dinglebear/yarr
Yarr MCP
Is the Yarr MCP server down? No. It is up and needs network, probed 2026-10-27.
Self-hosted media fleet operations across Sonarr, Radarr, Plex, and related apps over MCP and CLI.
needs network probed 2026-11-15 · unchanged since 2026-10-27
MCP error -32000: Connection closed yarr: getaddrinfo EAI_AGAIN api.github.com yarr: binary is not installed; postinstall may have failed
- Run it
- npx -y @dinglebear/yarr@2.2.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/dinglebear-ai/yarr
- Website
- https://github.com/dinglebear-ai/yarr
- Registry
- active, updated 2026-08-04 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Tailscale RMCP ai.dinglebear/tailscale-rmcp · not found
- UniFi RMCP ai.dinglebear/unifi-rmcp · not found
- Unraid RMCP ai.dinglebear/unraid · needs env
- Unraid RMCP ai.dinglebear/unraid-rmcp · not found
- Yarr MCP ai.dinglebear/yarr-mcp · not found
- YTDL RMCP ai.dinglebear/ytdl-rmcp · not found
- doublespeed — Xcode as an API ai.doublespeed/mcp · alive
- dxpert.ai — industrial AI-readiness & UNS agents ai.dxpert/mcp · alive
Servers that mention yarr.
- io.github.shaozhengkun123/yarrow · alive
- Yarrow io.github.ant588362/yarrow · alive
- I Ching io.github.pipeworx-io/i-ching · alive
- kdbx io.github.yarrasys/kdbx · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-27 06:51 | needs network | ||||
| 2026-10-20 06:39 | needs env |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.