A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Sync Day is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
Free no-signup group scheduling; share a link and rank times by who's free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http sync-day-mcp https://sync.day/mcp/mcp
# 2 — ask your agent for something these tools do
# create_event, parse_event_text, get_event and 5 more
Sync Day costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SAAll 1 server
syncday-app1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http sync-day-mcp https://sync.day/mcp/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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: 周六周日下
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Event name, max 60 chars. e.g. 周末聚餐, Team sync |
| question | string | no | Optional prompt shown to participants, max 200 chars. e.g. 哪天晚上有空？ |
| startDate | string | yes | First candidate day, YYYY-MM-DD. e.g. 2026-09-05 |
| endDate | string | no | Last candidate day, inclusive, YYYY-MM-DD (same as startDate for a single day; at most 21 days). Give this or days; endDate wins when both are set. |
| days | integer | no | Number of consecutive days from startDate (1-21); alternative to endDate. |
| hourFrom | integer | yes | Earliest hour of each day (0-23). e.g. 9 |
| hourTo | integer | yes | End of each day's window, exclusive (1-24), must be > hourFrom. e.g. 22 |
| durationMinutes | yes | Event length in minutes. One of 30, 60, 90, 120, 180, 240, 480. | |
| startStepMinutes | no | Gap between candidate start times in minutes: 30 or 60 (default 60). |
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 小时'.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | One sentence describing the event, max 300 chars. |
| today | string | no | Reference date for relative words like 明天/下周, YYYY-MM-DD. Defaults to today in Asia/Shanghai. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Event slug from the URL, e.g. calm-otter-4821 (sync.day/calm-otter-4821) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Event slug from the URL, e.g. calm-otter-4821 (sync.day/calm-otter-4821) |
| identity | string | yes | Random secret for this person that you generate and keep per person, 16-256 chars (e.g. 32 hex chars; NOT a plain user id or name, since anyone who guesses it can act as them). Same identity = same pa |
| name | string | yes | Display name, 1-20 chars, may repeat. e.g. 小明 |
| starts | array | yes | Start keys like 2026-09-05T14:00. Empty array clears this person's picks. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Event slug from the URL, e.g. calm-otter-4821 (sync.day/calm-otter-4821) |
| name | string | yes | Exact participant name to remove. |
| adminKey | string | yes | Organiser key returned by create_event (the ?key= part of adminUrl). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Event slug from the URL, e.g. calm-otter-4821 (sync.day/calm-otter-4821) |
| adminKey | string | yes | Organiser key returned by create_event (the ?key= part of adminUrl). |
| title | string | no | Event name, max 60 chars. e.g. 周末聚餐, Team sync |
| question | string | no | Optional prompt shown to participants, max 200 chars. e.g. 哪天晚上有空？ |
| startDate | string | no | First candidate day, YYYY-MM-DD. e.g. 2026-09-05 |
| endDate | string | no | Last candidate day, inclusive, YYYY-MM-DD (same as startDate for a single day; at most 21 days). Give this or days; endDate wins when both are set. |
| days | integer | no | Number of consecutive days from startDate (1-21); alternative to endDate. |
| hourFrom | integer | no | Earliest hour of each day (0-23). e.g. 9 |
| hourTo | integer | no | End of each day's window, exclusive (1-24), must be > hourFrom. e.g. 22 |
| durationMinutes | no | Event length in minutes. One of 30, 60, 90, 120, 180, 240, 480. | |
| startStepMinutes | no | Gap between candidate start times in minutes: 30 or 60 (default 60). |
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:'3f9a1
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Event slug from the URL, e.g. calm-otter-4821 (sync.day/calm-otter-4821) |
| identity | string | yes | Random secret for this person that you generate and keep per person, 16-256 chars (e.g. 32 hex chars; NOT a plain user id or name, since anyone who guesses it can act as them). Same identity = same pa |
| starts | array | no | All start keys this person accepts (from get_event.voteOptions); [] clears their approvals |
| start | string | no | Shorthand for starts: [start] |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Event slug from the URL, e.g. calm-otter-4821 (sync.day/calm-otter-4821) |
| adminKey | string | yes | Organiser key returned by create_event (the ?key= part of adminUrl). |
| start | yes | A candidate start key of the event (normally one of voteOptions), or null to reopen. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Sync Day or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digeste4e608331551ccdcafa3ab9091f80c549e76b5733c74b18a6a0ab9fee721250b
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| create_event | state-write | state-write: declares readOnlyHint: false |
| parse_event_text | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_event | no tags | |
| submit_availability | state-write | state-write: declares readOnlyHint: false |
| remove_participant | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| update_event | state-write | state-write: declares readOnlyHint: false |
| vote_time | state-write | state-write: declares readOnlyHint: false |
| decide_time | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digeste4e608331551ccdc
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Sync Day can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.