Mooi MCP server

• Registry namefyi.mooi/mooiverified in the MCP registry

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

• Stateanswerschecked 2026-11-03
• Tools18
• Server calls itselfMooi
• Server version1.0.0
• Protocol version2025-06-18

On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 177 ms.

• Its tools do every use case we checked: propose and vote on dates across group calendars; choose a restaurant and city by group vote; record decisions and reopen them after changes.
• Checked on 2 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: 2 so far
• What an agent can do with it3 of 3 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer360 ms
• Space in an agent's context≈ 4,642 tokensthe definitions of all its tools (18), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 18 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 18 of 18

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 →

• create_event

  Create an event and register its host. Supply a random UUID requestId and reuse it for uncertain retries, including across HTTP/MCP clients. Give personalUrl only to the host; share the plain url with invitees. Email is required for event…

• get_event

  Read the event, dates, availability, questions, decisions and activity. Emails are private and never returned.

• join_event

  Register yourself or the person you represent, with their email. Set emailAccess to whether your agent can monitor that inbox. Do not register other people without their permission.

• update_event

  Update the title, description, timezone, location or event status. Agents may select and confirm the current proposed plan without per-step human approval; confirmation requires a proposed date. Humans may veto later: set status to…

• update_participant

  Change your display name, agent, email monitoring mode or email notification preference. Reading and cursor acknowledgements do not trigger emails.

• propose_date

  Add a date option with ISO 8601 start and end including UTC offset. The event timezone controls display. Check accessible calendars and propose suitable options autonomously; do not claim unverified availability as certain.

• remove_date

  Remove a proposed date. A confirmed date must first be changed or the event reopened.

• set_availability

  Set or change your yes/maybe/no response to one or more proposed dates. Check accessible calendars and respond autonomously without asking for approval for each vote; use maybe for uncertainty. Change responses when the human vetoes or…

• ask_question

  Ask a question or create a poll. Use kind city first, then restaurant with parentId pointing to the city question. Empty options allow an open discussion.

• add_poll_option

  Add an option to an open question, such as a city or restaurant.

• vote

  Replace your votes on a question. Choose all acceptable options; an empty array clears your votes. Agents may vote and revise votes autonomously using known preferences and reasonable stated assumptions. Reopen decided questions with…

• decide_question

  Record the current choice of city, restaurant or other detail, or reopen a question. Agents may decide using the group’s responses and discussion without separate human approval. State unresolved assumptions; do not claim unanimous human…

• add_comment

  Post a message or answer a question. questionId attaches it to that discussion. Returns a direct comment link.

• get_changes

  Fetch changes strictly after sinceVersion. Save nextVersion only after processing. Read-only: never emails participants. Poll every 300 seconds if you cannot monitor email.

• acknowledge_changes

  Record that you have read changes up to a version. Does not send email or create a new change.

• set_channels

  Set where the group communicates. These are labels for participants’ agents, not credentials or automatic integrations. Agents prepare updates and use their own authorized messaging tools.

• get_channel_update

  Build a linked message for WhatsApp, Signal or email, excluding already-recorded deliveries. Only send when shouldSend is true. This does not send anything. Send with your authorized channel connector and record delivery afterwards.

• record_channel_update

  Record a successful external message delivery. Only call after your channel confirms the message was sent. Does not trigger more emails.