network.lucie/sync
REMOTE · SYNC.LUCIE.NETWORK
Check availability, book meetings and find group times — without sharing your calendar.
Available components
Last scanned (20 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1478 tokens (~295/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://sync.lucie.network/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sync.lucie.network | CN=YR2,O=Let's Encrypt,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | 69b4e1d4367b95e5ad25c849dace238f24c |
| SANs: sync.lucie.network | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sync.lucie.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 40414 | 8 | Verified |
| lucie.network. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sync.lucie.network/api/mcp | Verified | 200 | |
| http (plaintext) | http://sync.lucie.network/api/mcp | HTTPS enforced | 308 | https://sync.lucie.network/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
book_group_meeting Book a confirmed meeting across several Lucie hosts at once ~295
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.
| Name | Type | Req | Description |
|---|---|---|---|
| durationMinutes | integer | yes | Meeting length in minutes. Must be one the organizer offers. |
| participantHandles | array | yes | The other participants' @handles, e.g. ["@lucie", "@taylor"]. Each must have a live Lucie booking page. Leading @ optional. |
| reason | string | yes | A short agenda/purpose, shared with everyone on the invite. |
| startAt | string | yes | The exact ISO-8601 `start` copied verbatim from a find_group_times common slot (absolute UTC instant). Do NOT construct it from a wall-clock time. |
| title | string | yes | The meeting title, e.g. "Q3 planning sync". |
No output schema declared.
No examples provided.
book_meeting Book a meeting with a Lucie host ~409
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).
| Name | Type | Req | Description |
|---|---|---|---|
| bookerEmail | string | yes | The booker's email. The confirmation and calendar invite are sent here. |
| bookerName | string | yes | Full name of the person the meeting is for (the booker). |
| durationMinutes | integer | yes | Meeting length in minutes. Must be one the host offers. |
| handle | string | yes | The host's booking handle, e.g. "@alice" or "alice" (the leading @ is optional). |
| reason | string | yes | A short description of why the booker wants to meet (the agenda / purpose). Required — ask the booker for it before booking. Shared with the host alongside the invite. |
| startAt | string | yes | The exact ISO-8601 `start` value copied verbatim from a check_availability slot (an absolute UTC instant, e.g. 2026-07-28T17:00:00Z). Do NOT construct this from a local wall-clock time the booker sai… |
| viewerTimeZone | string | – | The BOOKER's IANA time zone (e.g. America/New_York) — the same one you passed to check_availability. Their confirmation email and reminders are written in this zone, so without it they read the host'… |
No output schema declared.
No examples provided.
check_availability Check a Lucie host's open booking slots ~287
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.
| Name | Type | Req | Description |
|---|---|---|---|
| durationMinutes | integer | – | Desired meeting length in minutes. Must be one the host offers. Defaults to 30 if omitted. |
| from | string | – | ISO-8601 start of the search window. Defaults to now + the host's minimum notice. |
| handle | string | yes | The host's booking handle, e.g. "@alice" or "alice" (from their lucie.network/book/@<handle> link). The leading @ is optional. |
| to | string | – | ISO-8601 end of the search window. Defaults to the host's max-advance horizon. |
| viewerTimeZone | string | – | The booker's IANA time zone, e.g. "Asia/Singapore" or "America/New_York". Pass the booker's own zone so slots are shown in their local time. Defaults to the host's zone if omitted. |
No output schema declared.
No examples provided.
create_group_event Create a group scheduling poll seeded with everyone's common times ~275
Create a Lucie group event (a poll) for several participants, pre-filled with candidate times when everyone is free (the intersection of their availability). Returns a vote link to share: participants pick which proposed times work, and people WITHOUT a Lucie handle can vote manually too. This is a write (creates a poll) but sends no emails and touches no calendars. Confirm the title, participants, and duration with the organizer before creating. Note: agent group scheduling is a Sync Pro feature — the organizer's email must be on Sync Pro (or a Lucie Membership).
| Name | Type | Req | Description |
|---|---|---|---|
| durationMinutes | integer | – | Meeting length in minutes. Defaults to 30. |
| from | string | – | ISO-8601 start of the search window. |
| handles | array | yes | Participants' @handles whose availability seeds the candidate times. The leading @ is optional. |
| organizerEmail | string | yes | The organizer's email. |
| organizerName | string | yes | The organizer's name (shown on the poll). |
| timeZone | string | – | IANA time zone for the poll's displayed times, e.g. "America/New_York". Defaults to UTC. |
| title | string | yes | The meeting title, e.g. "Q3 planning sync". |
| to | string | – | ISO-8601 end of the search window. |
No output schema declared.
No examples provided.
find_group_times Find times that work for a group of Lucie hosts ~212
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 to propose a group time. Times are absolute instants; pass viewerTimeZone so they show in the organizer's local zone.
| Name | Type | Req | Description |
|---|---|---|---|
| durationMinutes | integer | – | Meeting length in minutes. Must be one every participant offers. Defaults to 30. |
| from | string | – | ISO-8601 start of the search window. |
| handles | array | yes | The participants' booking handles, e.g. ["@alice", "@bob"]. The leading @ is optional. |
| to | string | – | ISO-8601 end of the search window. |
| viewerTimeZone | string | – | The organizer's IANA time zone, e.g. "America/New_York". Common times are shown in this zone. Defaults to UTC. |
No output schema declared.
No examples provided.
How do I install the network.lucie/sync MCP server?
network.lucie/sync is a hosted endpoint at https://sync.lucie.network/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sync.lucie.network
claude mcp add --transport http network-lucie-sync 'https://sync.lucie.network/api/mcp'
What is the network.lucie/sync MCP server?
network.lucie/sync is an MCP server listed in the public MCP registry as network.lucie/sync. Check availability, book meetings and find group times, without sharing your calendar. This page covers its hosted endpoint (https://sync.lucie.network/api/mcp).
Is the network.lucie/sync MCP server safe to use?
network.lucie/sync scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the network.lucie/sync MCP server expose?
network.lucie/sync exposes 5 tools: check_availability, book_meeting, find_group_times, create_group_event, book_group_meeting. Their descriptions and schemas cost roughly 1,478 tokens of context every time the server is loaded.
Does the network.lucie/sync MCP server require authentication?
No. We connected to network.lucie/sync without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the network.lucie/sync MCP server still maintained?
network.lucie/sync is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.