Skip to content

Zovo Shared Checklist MCP server

io.github.theluckystrike/shared-checklisttheluckystrikestreamable-httpv1.0.0Scanned

Make one checklist page that your whole group works through: moving house, wedding prep.

3 tools: 1 can delete or cancel things, 1 change things and 1 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • 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 Shared Checklist MCP server can do

The Zovo Shared Checklist MCP server is published by the GitHub account theluckystrike. It has 3 tools. It can delete or cancel things (1 tool: update_shared_checklist) and create or change data (1 tool: create_shared_checklist). 1 tool only reads.

2 tools bring in text other people can write (create_shared_checklist and update_shared_checklist).

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

Deletes or cancels 1Claude Code: deny
  • update_shared_checklistUse this when the organizer wants to add items, change an item's text, section, assignee or due date, remove items, tick or untick items by number, rename the list, change the note…Reads text others writeNo findings

    Why it is in this group

    • The name "update_shared_checklist" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    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 add items, change an item's text, section, assignee or due date, remove items, tick or untick items by number, rename the list, change the note, or close or reopen the page. Takes the private organizer link. Removing an item also removes its tick history. Does not send messages to anyone.

    Annotations the server declares

    • title: Change, tick or close a checklist
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
    • idempotentHint: false
Changes things 1Claude Code: ask
  • create_shared_checklistUse this when a group needs to work through a list together (moving house, wedding prep, event setup, onboarding a new teammate) and wants one link everyone can tick off.Reads text others writeNo findings

    Why it is in this group

    • The name "create_shared_checklist" 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 a group needs to work through a list together (moving house, wedding prep, event setup, onboarding a new teammate) and wants one link everyone can tick off. Publishes a page and returns a public link to share and a private organizer link. 1-150 items, each with an optional section, assignee first name and due date (YYYY-MM-DD, checked in the given time zone). Total text is limited to 64 KB: plenty for 150 items in English, about 130 items of 140 characters in Chinese, Japanese or Korean. Does not send reminders or notifications. Do not use for a private to-do list nobody else needs to see.

    Annotations the server declares

    • title: Create a shared checklist page
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: false
Only reads 1Show 1 read-only tool
  • show_checklist_resultsUse this when the organizer asks how far along a shared checklist is, what is overdue, who did what, or what is left, for a checklist made with create_shared_checklist.No findings

    Why it is in this group

    • The name "show_checklist_results" says "show": a word for reading.
    Description, as the server wrote it
    Use this when the organizer asks how far along a shared checklist is, what is overdue, who did what, or what is left, for a checklist made with create_shared_checklist. Takes the private organizer link and returns progress by section and by person, overdue and due-today items in the checklist's time zone, open items and recent ticks. Does not change the checklist. Do not use without the organizer link.

    Annotations the server declares

    • title: Show checklist progress
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • 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 write2
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
  • HighThe whole server

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

    Matched text

    https://shared-checklist.zovo.one/mcp: tools/list returned 3 tools to an anonymous client, including update_shared_checklist (destructive), create_shared_checklist (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 shared-checklist https://shared-checklist.zovo.one/mcp
claude mcp add --transport http shared-checklist https://shared-checklist.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__shared-checklist__show_checklist_results"
    ],
    "ask": [
      "mcp__shared-checklist__create_shared_checklist"
    ],
    "deny": [
      "mcp__shared-checklist__update_shared_checklist"
    ]
  }
}

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 shared-checklist. Review it before you use it.

Capability tags behind 2 rules
  • mcp__shared-checklist__create_shared_checklist untrusted-input
  • mcp__shared-checklist__update_shared_checklist 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/shared-checklist/verify?hash=a3111158dffb2a7844737d81e52a52356cae01e851b3f477dd01bd901bcbc72e" | jq -e '.changed == false'

Pinned hash a3111158dffb, from Nov 8, 2026, 02:20 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/shared-checklist/changes.xml

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

Badge

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

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

Zovo Shared Checklist MCP server: questions and answers

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

Is the Zovo Shared Checklist 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 Shared Checklist MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: update_shared_checklist.

Can the Zovo Shared Checklist 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 Shared Checklist MCP server have?

3 tools: 1 destructive, 1 write, 1 read. update_shared_checklist, create_shared_checklist and show_checklist_results.

Does the Zovo Shared Checklist MCP server need sign-in or OAuth?

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

Does the Zovo Shared Checklist 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 Shared Checklist MCP server changed its tools?

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