Lucie MCP server

• Registry namenetwork.lucie/syncverified in the MCP registry

The registry name sits under lucie.network. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools5
• Server calls itselfmcp-typescript server on vercel
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 306 ms.

• Its tools do schedule one-to-one and group calls with lucie sync, but not connect with operators hiring at venture-backed teams; find and filter potential deals as an investor.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• What an agent can do with it1 of 3 use cases
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer286 ms
• Space in an agent's context≈ 2,078 tokensthe definitions of all its tools (5), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• check_availability

  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…

• book_meeting

  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…

• find_group_times

  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…

• create_group_event

  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…

• book_group_meeting

  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…