Skip to content

sync MCP server

network.lucie/synclucie.networkstreamable-httpv1.0.0Scanned

Check availability, book meetings and find group times — without sharing your calendar.

6 tools: 1 do something that can't be undone, 3 change things and 2 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. 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 MCP server can do

The sync MCP server is published by lucie.network, a domain the MCP Registry verified. It has 6 tools. It can do things that cannot be undone, such as sending, paying or publishing (create_group_event) and create or change data (3 tools: book_meeting, create_trip_sync and book_group_meeting), but cannot delete data. 2 tools only read.

2 tools read private data (check_availability and find_group_times); 6 tools bring in text other people can write (check_availability, book_meeting, find_group_times and 3 more); 1 tool can send data out of your system (create_group_event). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

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, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 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.

6 tools

Can't be undone 1Claude Code: ask
  • create_group_eventCreate a Sync (what Lucie Sync calls a scheduling poll; the app's "Find a time" button, formerly "group event") for a CALL or an IN-PERSON MEETING, where people vote on TIMES.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "create_group_event" says "create": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.
    Description, as the server wrote it
    Create a Sync (what Lucie Sync calls a scheduling poll; the app's "Find a time" button, formerly "group event") for a CALL or an IN-PERSON MEETING, where people vote on TIMES. Use it for "create a sync", "find a time with @sam", "set up coffee with…". For a trip, offsite, conference, retreat or any full-day or multi-day event, where people vote on DAYS, use create_trip_sync instead, not this tool. kind "call" (default) adds a Google Meet link when sent; kind "in_person_meeting" takes `place` and the organizer's `travelMinutes` each way, and only proposes times that leave room for the trip. durationMinutes can be any length up to 480; candidate times come from when every listed @handle is free for that whole length. Call it directly; don't pre-check with check_availability or find_group_times (those are for booking, in fixed lengths). The organizer's own calendar always counts; other participants' count if they have a Lucie @handle, and anyone else just votes on the link, so a missing handle never blocks a poll. Returns a vote link. Creates the poll only: no emails, no calendar writes. Confirm title, participants, kind, place and length with the organizer first. Sync Pro (or a Lucie Membership).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • book_group_meetingConfirm a group meeting at a specific time across several Lucie hosts (by @handle), creating ONE shared Google Calendar event with everyone invited.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.

    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
    Confirm a group meeting at a specific time across several Lucie hosts (by @handle), creating ONE shared Google Calendar event with everyone invited. YOU (the connector's owner) are the organizer and host the event on your calendar — no organizer handle needed. This is a real write: it re-verifies every participant (you included) is free at that instant and refuses if anyone isn't — so it never double-books. Always call find_group_times first and copy an exact common-slot start. Before calling, confirm the time (in each person's zone), the participants, the title, and the reason. Requires you to be on Sync Pro (or a Lucie Membership) via your personal connector; everyone must have a live booking page.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • book_meetingBook a confirmed meeting on a Lucie Sync host's calendar at a specific start time.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.

    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
    Book a confirmed meeting on a Lucie Sync host's calendar at a specific start time. This is a real write: it creates a calendar event and emails both the host and the booker. Always call check_availability first and use one of the open slots it returns. Before calling, (1) show the booker the specific date/time you're about to book — in their own time zone — and get their explicit confirmation, and (2) collect their name, email, AND a brief reason for the meeting (ask for the reason if not given; it's required and shared with the host).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • create_trip_syncCreate a Sync where people vote on DAYS, not times: a trip, offsite, retreat, conference, workshop, or any full-day or multi-day event ("which week works for the Lisbon offsite?", …Reads text others writeNo findings

    Why it is in this group

    • The name "create_trip_sync" 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
    Create a Sync where people vote on DAYS, not times: a trip, offsite, retreat, conference, workshop, or any full-day or multi-day event ("which week works for the Lisbon offsite?", "3-day offsite sometime Jan–Mar", "which day for the workshop?"). Give tripDays (how many days it lasts; 1 for a single full day) and dates: the candidate START days as YYYY-MM-DD, up to 10, any distance ahead. If the user gives a range ("sometime in January"), pick a few sensible start days in it (e.g. one per week, avoiding the user's stated constraints) and confirm them with the user first. Optional place (a city or venue). Returns a vote link; anyone can vote, with or without a Lucie handle. Creates the poll only: no emails, no calendar writes. Sync Pro (or a Lucie Membership) via the personal connector.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • check_availabilityReturn the open meeting slots a Lucie Sync host offers, plus their booking rules (durations offered, minimum notice, how far ahead you can book, buffer between meetings).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "meeting": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Return the open meeting slots a Lucie Sync host offers, plus their booking rules (durations offered, minimum notice, how far ahead you can book, buffer between meetings). Returns only bookable slots and policy — never the host's raw calendar. Use this to find a time before proposing one to the user. Slots are absolute instants (ISO-8601 UTC). Pass the booker's viewerTimeZone so times display in THEIR local zone — the booker should never have to do time-zone math.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • find_group_timesGiven several Lucie hosts (by @handle), return the meeting times when ALL of them are free — the intersection of their availability — for a meeting of the given length.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "find_group_times" says "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "meeting": it reads calendars.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Given several Lucie hosts (by @handle), return the meeting times when ALL of them are free — the intersection of their availability — for a meeting of the given length. Read-only: never books, never exposes anyone's raw calendar (only the shared open slots). Use it before book_group_meeting, to pick a time to BOOK: it only works in lengths every host's booking page offers, and every participant needs a Lucie handle. To create a poll (a Sync) for people to vote on, do NOT use this as a pre-check: call create_group_event (times) or create_trip_sync (days) directly; they handle any length and people without a Lucie handle. Times are absolute instants; pass viewerTimeZone so they show in the organizer's local zone.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: 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.

12 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__sync__create_group_event"
    ]
  }
}

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:16 UTC, unchanged since Nov 13, 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
4
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 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://sync.lucie.network/api/mcp: tools/list returned 6 tools to an anonymous client, including create_group_event (irreversible), book_meeting (write), create_trip_sync (write), book_group_meeting (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 3 to 4

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.

  1. Tools1 added, 5 changed.+1 added~5 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 4.View diff
    • Tools that change things, listed without credentials: 3 to 4

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http sync https://sync.lucie.network/api/mcp
claude mcp add --transport http sync https://sync.lucie.network/api/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__check_availability",
      "mcp__sync__find_group_times"
    ],
    "ask": [
      "mcp__sync__book_meeting",
      "mcp__sync__create_group_event",
      "mcp__sync__create_trip_sync",
      "mcp__sync__book_group_meeting"
    ],
    "deny": []
  }
}

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

Capability tags behind 6 rules
  • mcp__sync__check_availability private-data, untrusted-input
  • mcp__sync__book_meeting untrusted-input
  • mcp__sync__find_group_times private-data, untrusted-input
  • mcp__sync__create_group_event untrusted-input, outbound
  • mcp__sync__create_trip_sync untrusted-input
  • mcp__sync__book_group_meeting 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/network.lucie/sync/verify?hash=6c06ccc4bf1a9ab92d7ad397d28ab8c0f8c75740054ef35e892280fba5ca5d1e" | jq -e '.changed == false'

Pinned hash 6c06ccc4bf1a, from Nov 18, 2026, 22:17 UTC.

Watch

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

https://radar.anlyon.com/servers/network.lucie/sync/changes.xml

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

Badge

Anlyon Radar badge for network.lucie/sync
[![Anlyon Radar](https://radar.anlyon.com/badge/network.lucie/sync.svg)](https://radar.anlyon.com/servers/network.lucie/sync)

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

sync MCP server: questions and answers

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

Is the sync MCP server safe?

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

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the sync MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: create_group_event.

What tools does the sync MCP server have?

6 tools: 1 irreversible, 3 write, 2 read. create_group_event, book_meeting, create_trip_sync, book_group_meeting, check_availability and find_group_times.

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

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

Does the sync MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_group_event.

Has the sync MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.