Skip to content

Zovo Sign-Up Sheet MCP server

io.github.theluckystrike/signup-sheettheluckystrikestreamable-httpv1.0.0Scanned

Sign-up sheets people claim

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Zovo Sign-Up Sheet MCP server can do

The Zovo Sign-Up Sheet MCP server is published by the GitHub account theluckystrike. It has 3 tools. It can create or change data (2 tools: create_signup_sheet and update_signup_sheet), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (create_signup_sheet, show_signup_results and update_signup_sheet).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • create_signup_sheetUse this when the user wants people to claim slots: potluck dishes, volunteer shifts, carpool seats, snack turns.Reads text others writeNo findings

    Why it is in this group

    • The name "create_signup_sheet" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Use this when the user wants people to claim slots: potluck dishes, volunteer shifts, carpool seats, snack turns. It publishes a shared page where each person enters a first name and picks slots; each slot has a capacity and a full slot cannot be taken. Returns a public link to share and a private organizer link. Slots may have dates and times (then give an IANA time_zone). Does not send emails or reminders and does not take payments.

    Annotations the server declares

    • title: Create sign-up sheet
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: false
  • update_signup_sheetUse this when the organizer wants to change a sheet made with create_signup_sheet: add slots, change a slot's label or capacity, remove an empty slot, change the per-person limit, …Reads text others writeNo findings

    Why it is in this group

    • The name "update_signup_sheet" says "update": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Use this when the organizer wants to change a sheet made with create_signup_sheet: add slots, change a slot's label or capacity, remove an empty slot, change the per-person limit, show or hide names, edit the note, or close and reopen sign-ups. Takes the organizer link and only the changes. A capacity cannot go below the people already signed up, and a slot with sign-ups cannot be removed. Does not notify participants.

    Annotations the server declares

    • title: Update sign-up sheet
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: false
Only reads 1Show 1 read-only tool
  • show_signup_resultsUse this when the user asks who signed up, what is still open, or how many spots are left on a sheet made with create_signup_sheet.Reads text others writeNo findings

    Why it is in this group

    • The name "show_signup_results" says "show": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Use this when the user asks who signed up, what is still open, or how many spots are left on a sheet made with create_signup_sheet. Takes the private organizer link and returns each slot with its capacity, spots taken, open spots and names, plus people's notes. Does not work with the public link and does not change the sheet.

    Annotations the server declares

    • title: Show sign-up results
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:23 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://signup-sheet.zovo.one/mcp: tools/list returned 3 tools to an anonymous client, including create_signup_sheet (write), update_signup_sheet (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http signup-sheet https://signup-sheet.zovo.one/mcp
claude mcp add --transport http signup-sheet https://signup-sheet.zovo.one/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__signup-sheet__show_signup_results"
    ],
    "ask": [
      "mcp__signup-sheet__create_signup_sheet",
      "mcp__signup-sheet__update_signup_sheet"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as signup-sheet. Review it before you use it.

Capability tags behind 3 rules
  • mcp__signup-sheet__create_signup_sheet untrusted-input
  • mcp__signup-sheet__show_signup_results untrusted-input
  • mcp__signup-sheet__update_signup_sheet untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/signup-sheet/verify?hash=a468bb27fd41a3f281437a0e5fc5cb5113d84a089746ef2f4a33a9b440ed0ad0" | jq -e '.changed == false'

Pinned hash a468bb27fd41, from Nov 8, 2026, 02:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/signup-sheet/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/signup-sheet
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/signup-sheet.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/signup-sheet)

Source: MCP Registry. Synced Nov 8, 2026, 03:18 UTC.

Zovo Sign-Up Sheet MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Zovo Sign-Up Sheet MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Zovo Sign-Up Sheet MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Zovo Sign-Up Sheet MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Zovo Sign-Up Sheet MCP server have?

3 tools: 2 write, 1 read. create_signup_sheet, update_signup_sheet and show_signup_results.

Does the Zovo Sign-Up Sheet MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Zovo Sign-Up Sheet MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Zovo Sign-Up Sheet MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.