pet-nest
Related Servers
Alternatives to pet-nest
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI hosts to join owner-authorized rooms and send, receive, browse, and retry signed posts through a stdio MCP interface, with E2EE room-key delivery handled by the owner's browser.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to control a Live2D desktop pet's expressions and actions via MCP protocol.MIT
- AlicenseNot gradedqualityCmaintenanceEnables local, source-traceable retrieval over prepared chat history and, only with separate authorization, AI-simulated persona conversations through a stdio MCP interface.MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients such as Claude Desktop or Claude Code to drive the local daemon through stdio, listing agents and sessions, running agents, and reporting costs.-

PoYo MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceLocal stdio bridge to the hosted PoYo MCP server, enabling discovery and execution of AI models via chat, generation tasks, and agent skills.1MIT- AlicenseNot gradedqualityCmaintenanceProvides an MCP stdio interface for AI agents to propose tool calls that are validated against task policy, held for human approval when required, executed in a sandboxed Linux environment, and recorded in an audit log.MIT
TDQS
Scored across 4 tools
Each tool targets a fairly distinct area: pet_album reads images, nest_status reads state/receipts, pet_adopt creates a pet, and pet_care performs care actions. The two read tools (pet_album, nest_status) could be slightly confused at first glance, but their resource boundaries are clear from the descriptions.
Three of four tools follow a consistent pet_<verb/noun> snake_case pattern (pet_album, pet_adopt, pet_care). nest_status is a minor deviation with a different prefix, but it's still readable and predictable.
Four tools is on the lean side but each covers a distinct function (read photos, read status, adopt, care), so the count is reasonable for a focused pet-care domain. It is slightly thin but no tool feels redundant.
The surface covers create (adopt), read (status, album), and an action (care), but there is no update, rename, release/remove-pet, or configuration operation. Core happy-path workflows work, yet lifecycle operations like managing or removing an existing pet are missing.