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.19527 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.43 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.6239 npm20MIT
TDQS
Scored across 20 tools
The tool set has clear overlap: signupgenius_list_created_active, signupgenius_list_created_expired, and signupgenius_list_created_all all list sign-ups created by the user, with the expired variant explicitly documented as an alias of active in session mode. signupgenius_legacy_get_my_signups also returns a similar listing, adding further confusion. While other tools (rsvp vs claim_slot, reports vs list_slots) are well-separated, these four listing tools create real ambiguity for an agent.
All tools follow a consistent prefix (signupgenius_) and snake_case verb_noun pattern (e.g., list_groups, get_profile, claim_slot). The naming is predictable and descriptive. Minor deviations like 'healthcheck' (noun as verb) and the long 'list_created_all' suffix are acceptable, but the overall pattern is strong.
20 tools is on the higher end of the scale (16-25 feels heavy). The server covers a broad domain—profiles, groups, sign-up listings, reports, slots, and participation actions—so the count is not egregious, but some tools are redundant (list_created_* variants) and could be consolidated. It's borderline appropriate.
The tool surface covers core workflows: authentication verification, group management (list, members, add), sign-up listing (created/invited/signed up), reporting, slot availability, and participation (RSVP, claim, release). However, notable gaps exist: no tool to remove a group member, no creation/update/delete of sign-ups, and reports are limited to key-holders only. Agents can work around most gaps but may hit dead ends for group removal or sign-up management.