# Syncday App Sync Day MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.syncday-app%2Fsync-day
Registry id: `mcp-registry/io.github.syncday-app/sync-day`
Status: live (checked 2026-10-27T02:41:10.995Z)

## Verdict

Syncday App Sync Day MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 1014 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (96/100) across 8 tools, costing an agent about 2,953 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 1014 ms | 20% of MCP servers |
| p95 handshake latency | 3303 ms | — |
| Checks in 30 days | 4,898 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 6 min | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 8 | — |
| Tool-list size for an agent | ~2,953 tokens | 46% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "syncday-app-sync-day-mcp-server": {
      "type": "http",
      "url": "https://sync.day/mcp/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http syncday-app-sync-day-mcp-server https://sync.day/mcp/mcp
```

## Tools (8)

- `create_event`: 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 cand
- `decide_time`: 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_
- `get_event`: 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 s
- `parse_event_text`: 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
- `remove_participant`: 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_even
- `submit_availability`: 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
- `update_event`: Organiser only: change any event settings (same fields and rules as create_event; omitted fields keep their current value; endDate wins over days). Existing pic
- `vote_time`: 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_av

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.