Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.chrischall/signupgenius-mcp

NPM · SIGNUPGENIUS-MCP

SignUpGenius for Claude — sign-ups, slots, groups, and RSVPs. Free accounts or Pro API key.

Available components

0 this week 94 Trust /100

Last scanned (6 hours ago)

Scores higher than 97% of npm servers

Category Productivity and Notes

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 9 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to chrischall/signupgenius-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2998 tokens (~149/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Package version: 2.1.11 → 2.2.0 functional
  • 18 Oct 26 +1
    • Known CVEs: partial → pass ▲ security
    • Dependency health: partial → 1.00 functional
  • 17 Oct 26 +1
    • Stability: 0.93 → pass security
  • 16 Oct 26 −2
    • Stability: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Known CVEs: pass → partial ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Dependency health: 1.00 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Dependency health: 1.00 → partial functional
    • Stability: pass → 0.93 functional
    • Package version: 2.1.10 → 2.1.11 functional
  • 14 Oct 26 +45
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Schema quality: 121 → 140 ▼ functional
    • Tool coverage: 72% → 88% ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Package version: 2.1.6 → 2.1.10 functional
  • 13 Oct 26 0
    • Package version: 2.1.6 → 2.1.10 functional
  • 12 Oct 26 −45
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 2.1.6 → 2.1.10 functional
  • 4 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/signupgenius-mcp@2.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo chrischall/signupgenius-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/chrischall/signupgenius-mcp/.github/workflows/release-please.yml@refs/heads/main
Rekor log index 3691540589
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:fb0b876b4eb231131caa1f786ef2e938f21c1358178a4429e8f629a3370c716e2aeca8c8913ebe6291467b66ee96b13a2cecd228a1138b000ba64710c

Background: How many MCP packages publish verified provenance →

Dependencies 9 packages
Packages resolved 9
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~2,998 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
signupgenius_add_group_member ~244

Add a person to one of your SignUpGenius groups by email address (first/last name optional). WRITES DATA: the person may start receiving the group's sign-up invitations, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call sends nothing and returns the preview (group, email, name) and a confirmToken, and only a repeat call with the same arguments plus that token adds them — show the preview to the user and get their approval first (MCP_CONFIRM_MODE).

NameTypeReqDescription
confirmTokenstring–ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se…
emailaddressstringyesEmail of the member to add to the group.
firstnamestring––
groupIdintegeryes–
lastnamestring––

No output schema declared.

No examples provided.

signupgenius_claim_slot ~451

Claim (sign up for) a slot on a slot-based SignUpGenius sheet. WRITES DATA the organizer sees, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call writes nothing and returns the preview (sheet, slot, identity) and a confirmToken, and only a repeat call with the same arguments plus that token submits — show the preview to the user and get their approval first (MCP_CONFIRM_MODE). Signs up as the signed-in account by default: omit firstname/lastname/email unless the user is signing up someone else (e.g. a family member). A supplied identity that differs from the account is allowed but flagged in the preview (identityDiffersFromAccount) — point it out to the user. For Yes/No/Maybe headcount sheets use signupgenius_rsvp instead.

NameTypeReqDescription
commentstring–Optional comment shown to the organizer.
confirmTokenstring–ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se…
customFieldsarray–Answers to the sheet's required custom questions. Read the required set from signupgenius_get_public_signup.customFields — omitting a required field makes the server reject the claim.
emailstring–Optional. Defaults to the signed-in account's email.
firstnamestring–Optional. Defaults to the signed-in account's first name. Supply it only to sign up someone else (e.g. a family member); the preview then flags identityDiffersFromAccount.
lastnamestring–Optional. Defaults to the signed-in account's last name.
quantityinteger–Spots to take. Default 1.
slotitemidintegeryesThe slot to claim. Get this from signupgenius_list_slots.
urlstringyesSign-up URL or slug.

No output schema declared.

No examples provided.

signupgenius_get_group_member ~64

Get detailed info for a group member (address, phone, email) when the member has provided it via a sign-up.

NameTypeReqDescription
groupIdintegeryes–
memberIdintegeryescommunitymemberid returned by signupgenius_list_group_members.

No output schema declared.

No examples provided.

signupgenius_get_profile ~61

Get the SignUpGenius profile of the authenticated user (name, email, member ID, subscription level). Useful as a first call to confirm credentials. Key mode hits /v2/k/user/profile; session mode hits /v3/member/profile.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

signupgenius_get_public_signup ~192

Look up a SignUpGenius sign-up by its public URL or slug (e.g. `https://www.signupgenius.com/go/<urlid>-<signupid>-<vanity>`). Returns the real sheet metadata: title, description, organization, category, creator + contact email, timezone, created/modified dates, whether it is an RSVP or slot-based sheet, and which custom fields a participant must supply to sign up. Requires NO SignUpGenius auth and works for sheets the user did not create. Use signupgenius_list_slots for the actual dates/times and availability — this tool returns metadata only.

NameTypeReqDescription
urlstringyesEither a full SignUpGenius sign-up URL (e.g. https://www.signupgenius.com/go/<slug>) or just the slug. The slug looks like `<hex>-<signupid>[-<vanity>]`.

No output schema declared.

No examples provided.

signupgenius_healthcheck ~105

Resolves the credential the way real tools do, then makes one authenticated request to api.signupgenius.com. Reports which source supplied the credential, whether api.signupgenius.com accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a api.signupgenius.com-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

signupgenius_legacy_get_my_signups ~64

Session mode only. Returns the same sign-up listing the SignUpGenius wizard sees (via /SUGboxAPI.cfm?go=t.getMySignups). Use when you want fuller data than signupgenius_list_created_* provides.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

signupgenius_list_created_active ~47

List sign-ups created by the authenticated user. In session mode this returns the full list (active + expired) — filter on enddate client-side if you need only active.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

signupgenius_list_created_all ~26

List ALL sign-ups created by the authenticated user (active and expired).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

signupgenius_list_created_expired ~40

Alias of signupgenius_list_created_active in session mode (v3 returns active + expired together). Filter on enddate client-side.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

signupgenius_list_group_members ~56

List members of a SignUpGenius group (basic info: name, email, memberid).

NameTypeReqDescription
groupIdintegeryesGroup ID returned by signupgenius_list_groups.
sortstring––

No output schema declared.

No examples provided.

signupgenius_list_groups ~44

List groups created by the authenticated user. Returns groupid, title, and member count for each group.

NameTypeReqDescription
sortstring–Sort order for group results.

No output schema declared.

No examples provided.

signupgenius_list_invited ~114

List sign-ups the user has been invited to. view: "brief" answers one line per sign-up (title — date — status).

NameTypeReqDescription
viewstring–"full" (default) returns SignUpGenius's listing verbatim; "brief" returns one line per sign-up — title — <start date as YYYY-MM-DD, or "no date"> — <status> — inside the untrusted-data envelope's dat…

No output schema declared.

No examples provided.

signupgenius_list_signedupfor ~116

List sign-ups the user has personally signed up for. view: "brief" answers one line per sign-up (title — date — status).

NameTypeReqDescription
viewstring–"full" (default) returns SignUpGenius's listing verbatim; "brief" returns one line per sign-up — title — <start date as YYYY-MM-DD, or "no date"> — <status> — inside the untrusted-data envelope's dat…

No output schema declared.

No examples provided.

signupgenius_list_slots ~226

List every SLOT on a SignUpGenius sign-up — date, day of week, start/end time, title, location, capacity, how many spots are filled vs still available, and who has already signed up (with the quantity each entry consumes). Accepts a sign-up URL, slug, or numeric id. Requires NO auth and works for sheets the user did NOT create, which is exactly the case the Pro signupgenius_report_* tools cannot serve (they are key-only AND owner-scoped). This is the right tool for "what is still open?".

NameTypeReqDescription
includeParticipantsboolean–Fetch the name + quantity of everyone already signed up (default true). Costs one extra request per slot row; set false for a fast availability-only view.
onlyAvailableboolean–Return only slots that still have room. Default false (return all).
urlstringyesA SignUpGenius sign-up URL, its slug (`<urlid>-<signupid>[-<vanity>]`), or just the numeric sign-up id.

No output schema declared.

No examples provided.

signupgenius_release_slot ~320

Withdraw (give up) a slot the user previously signed up for. WRITES DATA — this removes a real sign-up, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call removes nothing and returns the preview (sheet, slot, whose entry) and a confirmToken, and only a repeat call with the same arguments plus that token withdraws — show the preview to the user and get their approval first (MCP_CONFIRM_MODE).

NameTypeReqDescription
confirmTokenstring–ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se…
itemMemberIdintegeryesThe sign-up entry to withdraw — `participants[].item_member_id` from signupgenius_list_slots. This is the wizard's `imid`.
memberIdinteger–Optional. The signed-in member id is resolved automatically; supplying a DIFFERENT one is rejected, because this tool only withdraws the current user's own sign-up.
slotitemidintegeryesThe slot the entry sits in (`slotitemid` from the same signupgenius_list_slots row). Used to verify afterwards that the entry actually disappeared.
urlstringyesSign-up URL or slug.

No output schema declared.

No examples provided.

signupgenius_report_all ~110

Full report for a sign-up: every slot plus the participant who claimed it (with custom-question answers when present). Requires SIGNUPGENIUS_USER_KEY (Pro subscription) — session mode is not supported for reports — AND only covers sheets the key-holder created. For slot dates, times and availability on ANY sign-up (including sheets the user did not create) prefer signupgenius_list_slots, which needs no auth.

NameTypeReqDescription
signupIdintegeryesSign-up ID (signupid).

No output schema declared.

No examples provided.

signupgenius_report_available ~102

Report for a sign-up restricted to slots that are still open/empty. Requires SIGNUPGENIUS_USER_KEY (Pro subscription) — session mode is not supported for reports — AND only covers sheets the key-holder created. For slot dates, times and availability on ANY sign-up (including sheets the user did not create) prefer signupgenius_list_slots, which needs no auth.

NameTypeReqDescription
signupIdintegeryesSign-up ID (signupid).

No output schema declared.

No examples provided.

signupgenius_report_filled ~102

Report for a sign-up restricted to slots that have already been filled. Requires SIGNUPGENIUS_USER_KEY (Pro subscription) — session mode is not supported for reports — AND only covers sheets the key-holder created. For slot dates, times and availability on ANY sign-up (including sheets the user did not create) prefer signupgenius_list_slots, which needs no auth.

NameTypeReqDescription
signupIdintegeryesSign-up ID (signupid).

No output schema declared.

No examples provided.

signupgenius_rsvp ~514

RSVP to a SignUpGenius sign-up (the Yes/No/Maybe-style sheets, including invitations from family/friends). WRITES DATA the organizer sees, so it asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call sends nothing and returns the preview (sheet, response, head counts, identity) and a confirmToken, and only a repeat call with the same arguments plus that token submits — show the preview to the user and get their approval first (MCP_CONFIRM_MODE). Responds as the signed-in account by default: omit firstname/lastname/email unless the user is responding for someone else. A supplied identity that differs from the account is allowed but flagged in the preview (identityDiffersFromAccount) — point it out to the user. Refuses when the signed-in member already has a response on the sheet (it can only ADD a response, so a second one would double-count) — change an existing answer in the SignUpGenius web UI. Slot-based sign-ups (e.g. "claim the 3pm slot") are NOT handled here — use signupgenius_claim_slot for those.

NameTypeReqDescription
adultsinteger–Adult guest count. Defaults to 1 for yes/maybe, 0 for no.
childreninteger–Child guest count. Defaults to 0.
commentstring–Optional comment shown to the sign-up owner.
confirmTokenstring–ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has se…
emailstring–Optional. Defaults to the signed-in account's email.
firstnamestring–Optional. Defaults to the signed-in account's first name. Supply it only to respond for someone else (e.g. a family member); the preview then flags identityDiffersFromAccount.
lastnamestring–Optional. Defaults to the signed-in account's last name.
responsestringyesRSVP response. Maps to the wizard's Yes / No / Maybe buttons.
urlstringyesSignUpGenius sign-up URL (https://www.signupgenius.com/go/<slug>) or just the slug.

No output schema declared.

No examples provided.

Install

How do I install the io.github.chrischall/signupgenius-mcp server?

io.github.chrischall/signupgenius-mcp runs locally as an npm package, launched with npx -y signupgenius-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · signupgenius-mcp

# add to Claude Code
claude mcp add chrischall-signupgenius-mcp -- npx -y signupgenius-mcp
Common questions

What is the io.github.chrischall/signupgenius-mcp server?

io.github.chrischall/signupgenius-mcp is listed in the public MCP registry as io.github.chrischall/signupgenius-mcp. SignUpGenius for Claude, sign-ups, slots, groups, and RSVPs. Free accounts or Pro API key. This page covers its npm package (signupgenius-mcp).

Is the io.github.chrischall/signupgenius-mcp server safe to use?

io.github.chrischall/signupgenius-mcp scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.chrischall/signupgenius-mcp server expose?

io.github.chrischall/signupgenius-mcp exposes 20 tools: signupgenius_get_profile, signupgenius_healthcheck, signupgenius_list_groups, signupgenius_list_group_members, signupgenius_get_group_member, and 15 more. Their descriptions and schemas cost roughly 2,998 tokens of context every time the server is loaded.

Is the io.github.chrischall/signupgenius-mcp server still maintained?

io.github.chrischall/signupgenius-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.chrischall/signupgenius-mcp server under?

io.github.chrischall/signupgenius-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.