Skip to content

sync-day MCP server

io.github.syncday-app/sync-daysyncday-appstreamable-httpv1.0.0Scanned

Free no-signup group scheduling; share a link and rank times by who's free.

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

Tools: 1 delete, 0 irreversible, 6 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • 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 sync-day MCP server can do

The sync-day MCP server is published by the GitHub account syncday-app. It has 8 tools. It can delete or cancel things (1 tool: remove_participant) and create or change data (6 tools: create_event, parse_event_text, submit_availability, update_event and 2 more). 1 tool only reads.

1 tool brings in text other people can write (parse_event_text).

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 21, 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.

8 tools

Deletes or cancels 1Claude Code: deny
  • remove_participantOrganiser only: remove one participant by name (the oldest row with that name when it repeats), together with their vote.No findings

    Why it is in this group

    • The name "remove_participant" says "remove": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Organiser only: remove one participant by name (the oldest row with that name when it repeats), together with their vote. Requires the adminKey from create_event.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Changes things 6Claude Code: ask
  • create_eventCreate a sync.day availability poll and get its share link.No findings

    Why it is in this group

    • The name "create_event" says "create": a word for a change.
    Description, as the server wrote it
    Create a sync.day availability poll and get its share link. Candidate days run from startDate to endDate (inclusive; or give days instead). Each day offers candidate START times from hourFrom, every startStepMinutes, as long as start + durationMinutes <= hourTo. Returns slug, public url (share this), adminUrl and adminKey (keep private; needed for update_event / remove_participant). Example: 周六周日下午聚餐 3 小时 -> {title:'周末聚餐', startDate:'2026-09-05', endDate:'2026-09-06', hourFrom:13, hourTo:18, durationMinutes:180, startStepMinutes:60}.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • decide_timeOrganiser only: settle on a start time (locks availability picking and voting; the page shows 已定).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Organiser only: settle on a start time (locks availability picking and voting; the page shows 已定). Pass start=null to reopen. Requires the adminKey from create_event.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • parse_event_textTurn a natural-language sentence (Chinese works best) into create_event input using sync.day's AI parser.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    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
    Turn a natural-language sentence (Chinese works best) into create_event input using sync.day's AI parser. Does NOT create anything; review the result, then call create_event. Example: '下周六或周日下午聚餐,大概 3 小时'.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • submit_availabilitySave (or replace) one person's availability: the candidate start keys they can make, from get_event.startOptions.No findings

    Why it is in this group

    • The name "submit_availability" says "submit": a word for a change.
    Description, as the server wrote it
    Save (or replace) one person's availability: the candidate start keys they can make, from get_event.startOptions. The person is identified by `identity`, not by name: the same identity later overwrites the same row (and can rename it), a different identity with the same name is a second participant. Keys outside the event's start options are rejected. Returns the updated ranking.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • update_eventOrganiser only: change any event settings (same fields and rules as create_event; omitted fields keep their current value; endDate wins over days).No findings

    Why it is in this group

    • The name "update_event" says "update": a word for a change.
    Description, as the server wrote it
    Organiser only: change any event settings (same fields and rules as create_event; omitted fields keep their current value; endDate wins over days). Existing picks are kept; those no longer valid starts are just hidden.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • vote_timeApproval voting: set every start one person accepts (replaces their earlier approvals; an empty list clears them).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Approval voting: set every start one person accepts (replaces their earlier approvals; an empty list clears them). The voter is the `identity` used in submit_availability and must have at least one start saved. Only keys listed in get_event.voteOptions are accepted; the error lists the current options otherwise. Rejected once the organiser decided. Example: {slug:'calm-otter-4821', identity:'3f9a1c77b2e04d5e8a61f0c9d2b7e415', starts:['2026-09-05T15:00','2026-09-06T10:00']}. `start` is shorthand for a single-item `starts`.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • get_eventRead an event: settings, every candidate start key per day (startOptions), who has answered (participants with their start keys; names may repeat), the top 10 start times by head-c…No findings

    Why it is in this group

    • The name "get_event" says "get": a word for reading.
    Description, as the server wrote it
    Read an event: settings, every candidate start key per day (startOptions), who has answered (participants with their start keys; names may repeat), the top 10 start times by head-count (ranked), the starts EVERYONE with picks can make with their votes (voteOptions), each person's vote (votes) and decidedStart. No key needed.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

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 write1
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 20, 2026, 19:11 UTC, unchanged since Oct 22, 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
7
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 7 tools that change things (1 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://sync.day/mcp/mcp: tools/list returned 8 tools to an anonymous client, including remove_participant (destructive), create_event (write), parse_event_text (write), submit_availability (write), update_event (write) and 2 more

    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 sync-day https://sync.day/mcp/mcp
claude mcp add --transport http sync-day https://sync.day/mcp/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__sync-day__get_event"
    ],
    "ask": [
      "mcp__sync-day__create_event",
      "mcp__sync-day__parse_event_text",
      "mcp__sync-day__submit_availability",
      "mcp__sync-day__update_event",
      "mcp__sync-day__vote_time",
      "mcp__sync-day__decide_time"
    ],
    "deny": [
      "mcp__sync-day__remove_participant"
    ]
  }
}

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 sync-day. Review it before you use it.

Capability tags behind 1 rule
  • mcp__sync-day__parse_event_text 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.syncday-app/sync-day/verify?hash=4d53ade9db10ab4455987057c952b85939dbbe53d64e2b0cf4120bcb498f37ad" | jq -e '.changed == false'

Pinned hash 4d53ade9db10, from Nov 21, 2026, 04:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.syncday-app/sync-day/changes.xml

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

Badge

Anlyon Radar badge for io.github.syncday-app/sync-day
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.syncday-app/sync-day.svg)](https://radar.anlyon.com/servers/io.github.syncday-app/sync-day)

Source: MCP Registry. Synced Oct 21, 2026, 18:50 UTC.

sync-day MCP server: questions and answers

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

Is the sync-day MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 7 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 sync-day MCP server delete data?

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

Can the sync-day 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 sync-day MCP server have?

8 tools: 1 destructive, 6 write, 1 read. remove_participant, create_event, parse_event_text, submit_availability, update_event, vote_time, decide_time and get_event.

Does the sync-day MCP server need sign-in or OAuth?

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

Does the sync-day MCP server send data to outside services?

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

Has the sync-day MCP server changed its tools?

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