# SignUpSheet.page (remote · signupsheet.page)

Free sign-up sheets, date polls and group cards people join from one link. No accounts, no ads.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `signupsheet.page`: 72/100 (this document), [markdown](https://verifymcp.io/servers/page-signupsheet-signupsheet/signupsheet.md), [page](https://verifymcp.io/servers/page-signupsheet-signupsheet/signupsheet)

## Channel facts

- Endpoint: `https://signupsheet.page/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1533 tokens (~383/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the SignUpSheet.page MCP server?

SignUpSheet.page is a hosted endpoint at https://signupsheet.page/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http page-signupsheet-signupsheet 'https://signupsheet.page/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "page-signupsheet-signupsheet": {
      "url": "https://signupsheet.page/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "page-signupsheet-signupsheet": {
      "type": "http",
      "url": "https://signupsheet.page/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.page-signupsheet-signupsheet]
url = "https://signupsheet.page/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "page-signupsheet-signupsheet": {
      "type": "remote",
      "url": "https://signupsheet.page/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add page-signupsheet-signupsheet --url 'https://signupsheet.page/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  page-signupsheet-signupsheet:
    url: "https://signupsheet.page/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "page-signupsheet-signupsheet": {
      "Transport": "http",
      "Url": "https://signupsheet.page/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add page-signupsheet-signupsheet -t streamable-http -u 'https://signupsheet.page/mcp'
```

### Other

```json
{
  "mcpServers": {
    "page-signupsheet-signupsheet": {
      "type": "http",
      "url": "https://signupsheet.page/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 68, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 63)

First indexed and scored.

## MCP tools (4)

### `create_signup_sheet` (~511 tokens)

Create sign-up sheet

Creates a live online sign-up sheet on SignUpSheet.page where people claim slots from one shared link without an account, and returns the share link and the private organizer link. Use it when the user wants people to sign up for things: dishes for a potluck or class party, volunteer shifts, snack or carpool days, meal train dates, appointment or conference time slots, supplies to bring, classroom helpers. Each slot has a label, an optional date and start/end time, and how many people it needs; full slots get a waitlist and people get a reminder the day before. Not for voting on dates, group cards, ticket sales or paid registration.

Input parameters:

- `chip_in` (object): Optional money collection on the same link. People pledge an amount and pay the organizer directly in the organizer's own payment app; SignUpSheet.page does not hold or transfer money. Include at lea…
- `description` (string): Optional details shown at the top: place, time, what to bring. Plain text; web links are removed.
- `language` (string): Language of the pages and emails people will see. Use the language the user is writing in; 'en' if it is not in the list.
- `one_per_person` (boolean): Allow only one slot per person (checked by email; turns on require_email).
- `organizer_email` (string): Optional. Only an email address the user gave in this conversation. If set, both links are emailed to it so the private organizer link is not lost. Never guess an address.
- `organizer_name` (string): Name shown as the organizer, e.g. 'Dana'. Use the user's name if they gave it; otherwise omit.
- `require_email` (boolean): Ask people for an email when signing up (enables reminders and self-cancel links).
- `show_names` (boolean): Show who signed up to everyone with the link.
- `slots` (array, required): What people can sign up for, in display order.
- `timezone` (string): IANA time zone of the event, e.g. 'America/Chicago' or 'Europe/Madrid'. Needed when dates or times are given (reminders and calendar files use it).
- `title` (string, required): Sheet title, e.g. 'Room 12 Thanksgiving potluck – Nov 20'.

Output parameters:

- `chip_in` (boolean)
- `emailed_links_to` (string|null): Masked address the links are being emailed to, or null.
- `flyer_url` (string): Printable QR-code flyer for the sheet.
- `item_count` (integer)
- `kind` (string)
- `language` (string)
- `organizer_url` (string): Private management link for the person who asked. Left out only when a repeated request returns a sheet whose organizer link went to the organizer email (see organizer_url_note).
- `organizer_url_note` (string)
- `share_url` (string): Public link to send to participants.
- `timezone` (string)
- `title` (string)
- `warnings` (array)

### `create_date_poll` (~333 tokens)

Create date poll

Creates a group scheduling poll on SignUpSheet.page: people open one link and answer yes, maybe or no for each date or time option, and the option that works for most people is highlighted. Returns the share link and the private organizer link, where the organizer can pick the final time and notify everyone who left an email. Use it when the user wants to find a date or time that works for a group, such as a meeting, dinner, reunion, parent night or study session. Not for sign-up slots or opinion polls without dates.

Input parameters:

- `description` (string): Optional details (place, length). Plain text; web links are removed.
- `language` (string): Language of the pages and emails people will see. Use the language the user is writing in; 'en' if it is not in the list.
- `options` (array, required): Date or date-and-time options to vote on. They are shown in date order.
- `organizer_email` (string): Optional. Only an email address the user gave in this conversation. If set, both links are emailed to it so the private organizer link is not lost. Never guess an address.
- `organizer_name` (string): Name shown as the organizer, e.g. 'Dana'. Use the user's name if they gave it; otherwise omit.
- `timezone` (string): IANA time zone of the event, e.g. 'America/Chicago' or 'Europe/Madrid'. Needed when dates or times are given (reminders and calendar files use it).
- `title` (string, required): e.g. 'Book club – November meeting'.

Output parameters:

- `chip_in` (boolean)
- `emailed_links_to` (string|null): Masked address the links are being emailed to, or null.
- `flyer_url` (string): Printable QR-code flyer for the sheet.
- `item_count` (integer)
- `kind` (string)
- `language` (string)
- `organizer_url` (string): Private management link for the person who asked. Left out only when a repeated request returns a sheet whose organizer link went to the organizer email (see organizer_url_note).
- `organizer_url_note` (string)
- `share_url` (string): Public link to send to participants.
- `timezone` (string)
- `title` (string)
- `warnings` (array)

### `create_group_card` (~468 tokens)

Create group card

Creates an online group card on SignUpSheet.page for one person: everyone opens one shared link and writes a message, and the organizer delivers the finished card later by email, on screen or printed. Use it for a farewell, birthday, retirement, thank-you, new baby, get well, sympathy, welcome, wedding, graduation, work anniversary or congratulations card from a team, class or family. It can also collect money for a gift (chip_in): signers pledge an amount and pay the organizer directly. Returns the share link (for signers, not for the recipient) and the private organizer link.

Input parameters:

- `chip_in` (object): Optional money collection on the same link. People pledge an amount and pay the organizer directly in the organizer's own payment app; SignUpSheet.page does not hold or transfer money. Include at lea…
- `language` (string): Language of the pages and emails people will see. Use the language the user is writing in; 'en' if it is not in the list.
- `message_to_signers` (string): Optional note shown to signers, e.g. 'Sign by Friday — we give it at lunch.' Plain text.
- `occasion` (string, required)
- `organizer_email` (string): Optional. Only an email address the user gave in this conversation. If set, both links are emailed to it so the private organizer link is not lost. Never guess an address.
- `organizer_name` (string): Name shown as the organizer, e.g. 'Dana'. Use the user's name if they gave it; otherwise omit.
- `recipient_name` (string, required): Who the card is for, e.g. 'Sarah'.
- `show_messages` (boolean): Let signers see each other's messages before the card is delivered.
- `timezone` (string): IANA time zone of the event, e.g. 'America/Chicago' or 'Europe/Madrid'. Needed when dates or times are given (reminders and calendar files use it).
- `title` (string): Optional; defaults to e.g. 'Farewell card for Sarah' in the chosen language.

Output parameters:

- `chip_in` (boolean)
- `emailed_links_to` (string|null): Masked address the links are being emailed to, or null.
- `flyer_url` (string): Printable QR-code flyer for the sheet.
- `item_count` (integer)
- `kind` (string)
- `language` (string)
- `organizer_url` (string): Private management link for the person who asked. Left out only when a repeated request returns a sheet whose organizer link went to the organizer email (see organizer_url_note).
- `organizer_url_note` (string)
- `share_url` (string): Public link to send to participants.
- `timezone` (string)
- `title` (string)
- `warnings` (array)

### `get_sheet_summary` (~134 tokens)

Get sheet status

Reads the current public status of a SignUpSheet.page sign-up sheet, date poll or group card from its share link: which slots are open or full, poll answers per option, or how many people have signed a card. Use it when the user asks how their sheet, poll or card is going. Takes the public share link (signupsheet.page/s/…); it never returns email addresses or other private details.

Input parameters:

- `share_url` (string, required): The public link, e.g. https://signupsheet.page/s/k3m9x2pq (an 8-character sheet id alone also works).

Output parameters:

- `card` (object)
- `chip_in` (object)
- `closed` (boolean)
- `kind` (string)
- `poll` (object)
- `share_url` (string)
- `slots` (array)
- `title` (string)
- `totals` (object)
- `truncated` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/page-signupsheet-signupsheet/signupsheet#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 63

## Common questions

### What is the SignUpSheet.page MCP server?

SignUpSheet.page is an MCP server listed in the public MCP registry as page.signupsheet/signupsheet. Free sign-up sheets, date polls and group cards people join from one link. No accounts, no ads. This page covers its hosted endpoint (https://signupsheet.page/mcp).

### Is the SignUpSheet.page MCP server safe to use?

SignUpSheet.page scores 72 out of 100 on VerifyMCP. 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 SignUpSheet.page MCP server expose?

SignUpSheet.page exposes 4 tools: create_signup_sheet, create_date_poll, create_group_card, get_sheet_summary. Their descriptions and schemas cost roughly 1,446 tokens of context every time the server is loaded.

### Does the SignUpSheet.page MCP server require authentication?

No. We connected to SignUpSheet.page without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SignUpSheet.page MCP server still maintained?

SignUpSheet.page 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.

## Links

- Remote endpoint: https://signupsheet.page/mcp
- Website: https://signupsheet.page/ai
- Changelog RSS feed: https://verifymcp.io/servers/page-signupsheet-signupsheet/signupsheet.xml
- Changelog JSON feed: https://verifymcp.io/servers/page-signupsheet-signupsheet/signupsheet.json
- HTML version of this page: https://verifymcp.io/servers/page-signupsheet-signupsheet/signupsheet