mcp-server-sensory
Related Servers
Alternatives to mcp-server-sensory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Raspberry Pi peripheral bus access, enabling AI agents to interact with CAN, I2C, SPI, UART, and GPIO directly through natural language.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for VoidSend enabling AI agents to send and receive end-to-end encrypted messages.6 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that enables an AI agent to display rich Markdown content on a physical monitor connected to a headless Linux device via a Textual/Rich TUI.1-
- FlicenseNot gradedqualityDmaintenanceMCP server for the mimOE AI Agent, enabling on-device tools like device discovery, network insight, and persistent note storage via natural language.-
- AlicenseNot gradedqualityAmaintenanceMCP server enabling real-time communication, task delegation, and acknowledgment among multiple AI agents through a single local endpoint.304 npm5MIT
- FlicenseAqualityDmaintenanceMCP server that gives AI agents a live, tmux-backed messaging mesh for instant message delivery without polling.7-
TDQS
Scored across 14 tools
Tools are mostly distinct by format and action, but 'braille_binary_grid' and 'braille_punchcard' both generate patterns with some overlap, and 'transcode' is vague. Overall, agents can usually differentiate.
Naming follows a consistent snake_case pattern and typically starts with the sensory type (e.g., braille_, morse_, sstv_), except for 'transcode' and 'reflux_decode'. The pattern is not strictly verb_noun but is predictable.
With 14 tools covering three sensory formats plus a transcode utility, the count is well-scoped and each tool serves a clear purpose. Not too few or too many.
The set covers Braille and Morse encoding/decoding well, but SSTV lacks a standalone decode tool (only a composite pipeline via reflux_decode). Other sensory formats are omitted, leaving minor gaps.