Yuva
Customer support inbox: search, read, triage and draft replies to e-mail and chat.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://{yuva_host}/mcp | registry |
|---|---|---|
| Handshake | Endpoint is a template (the URL needs your own values), not checked | our check, 2026-10-12 |
| GitHub stars | 8 | github.com/productdevbook/yuva |
| Last push | 2026-10-12 | GitHub API |
| Licence | AGPL-3.0 | GitHub API |
| Registry version | 0.0.8 · active · updated 2026-10-11 | registry |
| Package | mcpb: https://github.com/productdevbook/yuva/releases/download/v0.0.8/yuva.mcpb | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
Commands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- memory-mcp Persistent memory + git snapshots for Claude Code. Never lose context or code.
- claudia Task management for AI agents with hierarchical tasks, dependencies, sprints, and…
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/io.github.productdevbook/yuva)<a href="https://openforallofus.com/tools/io.github.productdevbook/yuva"><img src="https://openforallofus.com/badge/io.github.productdevbook/yuva.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name io.github.productdevbook/yuva.