signupgenius-mcp
Related Servers
Alternatives to signupgenius-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceMCP 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.19291 npmMIT
- FlicenseNot gradedqualityCmaintenanceMCP server for the Teamup Calendar API, enabling event management, calendar listing, and available slot search.-
- AlicenseNot gradedqualityCmaintenanceMCP 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.4,639 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.6262 npm24MIT
TDQS
Scored across 20 tools
Most tools have distinct purposes, but signupgenius_list_created_active, signupgenius_list_created_expired, and signupgenius_list_created_all are nearly identical in session mode (expired is an alias of active), causing real confusion about which to call. The three report_* tools overlap but are differentiated by filters, and list_slots vs report_available is clarified in descriptions, but the created-list redundancy drags the score down.
Nearly all tools use a consistent snake_case verb_noun pattern with the same signupgenius_ prefix. Minor deviations exist, such as signupgenius_legacy_get_my_signups (legacy prefix, 'my' instead of 'created') and signupgenius_healthcheck (noun-only), but the overall pattern is predictable and readable.
20 tools is on the heavy side for this domain, and several tools are redundant aliases or near-duplicates (three list_created_* variants plus a legacy alternative). While a few extra tools for different auth modes and report filters are justified, the set feels inflated rather than tightly scoped.
The surface covers core lifecycle operations: viewing sign-ups, slots, groups, and reports; claiming/releasing slots; RSVPing; and adding group members. Gaps like removing a group member, updating an RSVP, or creating a sign-up exist, but the most common agent workflows are supported, and some limitations are explicitly documented.