signupgenius-mcp
Related Servers
Alternatives to signupgenius-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Canvas LMS enabling parent observers and students to access courses, assignments, grades, and more. Supports multiple authentication methods including token, OAuth, and a convenient fetchproxy fallback.19661 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server for the Teamup Calendar API, enabling event management, calendar listing, and available slot search.-
- AlicenseNot gradedqualityDmaintenanceMCP server for Canvas LMS with automatic OAuth authentication. Enables interaction with courses, assignments, grades, modules, discussions, quizzes, files, calendar, messaging, and more without manual API token management.183 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for use with msgraph calls to mail, calendar, and files16MIT
- AlicenseAqualityCmaintenanceMCP server for the Simple In/Out APIv4, providing tools for check-in/out statuses, user and group management, and access to beacons, geofences, networks, announcements, and roles.15Apache 2.0
- AlicenseBqualityBmaintenanceMCP server to help manage a WHMCS installation.6245 npm22MIT
TDQS
Scored across 20 tools
The set has clear separation between slot listing, reports, and participant actions, but the list_created_* family (active/expired/all/legacy_get_my_signups) overlaps heavily, with list_created_expired described as an alias of active in session mode. Descriptions mitigate some confusion, but an agent could easily pick the wrong listing tool.
Almost all tools follow a consistent signupgenius_<verb>_<noun> pattern, with list_, get_, report_, add_, claim_, and release_ prefixes making behavior predictable. Minor deviations like legacy_get_my_signups and healthcheck break the strict pattern but remain recognizable.
20 tools is at the heavy end, and several are redundant: list_created_expired, list_created_all, and legacy_get_my_signups overlap with list_created_active, and the three report_* tools partly duplicate slot data covered by list_slots. The core set is useful, but the surface could be trimmed.
The server covers public metadata, slot availability, reports, group management, and participant write actions like RSVP, claim, and release. Obvious gaps remain: no create/update/delete sign-up operations and no remove-group-member or delete-group tools, so organizer workflows have dead ends.