A-

sync.day

https://sync.day/mcp/mcp
90/100 · MCP Trust Grade · checked 3d ago · MCP 2025-06-18

Is the sync.day MCP server safe to use?

Independent trust grade A- (90/100). No blocking issues found in the static + spec checks. wmcp.sh continuously watches sync.day for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

✓ Watched since 2026-10-26 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 8 tools · Other

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 o

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,

get_event

Read an event: settings, every candidate start key per day (startOptions), who has answered (participants with their start keys; names may repeat), th

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 `identit

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 c

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). Ex

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

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 fr

Spec conformance20%100
Security (OWASP MCP)30%100
Reliability / performance20%92
Tool hygiene15%75
Transparency / provenance15%70

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.
Grade another server

We re-grade sync.day on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Run sync.day? Claim it (free) to get drift alerts and show an independently-verified trust badge. The grade stays free — claiming just ties it to you.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — sync.day grade A-
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade A- · wmcp.sh
[![MCP Trust Grade A-](https://wmcp.sh/mcp/grade/sync.day/badge.svg)](https://wmcp.sh/mcp/grade/sync.day)
<a href="https://wmcp.sh/mcp/grade/sync.day"><img src="https://wmcp.sh/mcp/grade/sync.day/badge.svg" alt="MCP Trust Grade A- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.