mcp-banshee
Related Servers
Alternatives to mcp-banshee
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables compatible assistants to record and track parcel or visitor arrivals, acknowledge them, retrieve handoff instructions, complete or cancel handoffs, check home status, and toggle quiet mode through MCP tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables mixed-schedule families to coordinate quiet hours, meals, chores, calendar events, nudges, and wake briefings through an MCP client such as a living-room Alexa+ Show simulator.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables sending push notifications to phones and other devices from any MCP client, with tools for validating users, listing sounds, checking limits, and managing emergency receipts.MIT
- AlicenseNot gradedqualityBmaintenanceEnables an Alexa+ console to check suspicious calls for coercion, arbitrate simulated household emergencies with reversible safety actions, and compile timestamped insurance claim dossiers over a self-hosted Streamable HTTP MCP endpoint.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to send notifications through a local relay, inspect events and deliveries, and check whether alerts actually reached configured channels. It also provides prompts and a contract resource for building scripts, monitors, and pollers.25 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to alert users locally by playing a notification sound and showing a system banner when a task finishes or attention is needed, with support for custom sounds and multiple MCP clients.259 npmMIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: dispatch_alert performs an action (notify) while list_couriers is a read-only lookup. There is no plausible way to confuse them, and the descriptions reinforce the boundary.
Both names follow a clean verb_noun pattern (dispatch_alert, list_couriers). The convention is predictable and unambiguous.
Two tools is thin for a functional server; the surface is essentially a single action plus a supporting lookup. It is not egregiously wrong for a whimsical notification utility, but it borders on under-scoped.
Core dispatch is covered, but there is no way to manage the courier roster (add/remove/configure), no delivery status or history, and no visibility into what severity values exist. Agents can perform the primary action but hit dead ends for lifecycle management.