Servidor MCP de When Works For You?

• Nombre en el registrocom.whenworksforyou/wwfyverificado en el registro MCP

El nombre en el registro está bajo whenworksforyou.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-25
• Herramientas21
• El servidor se llamawwfy
• Versión del servidor1.1.0
• Versión del protocolo2025-06-18

El 2026-10-25 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 56 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 1 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 1 hasta ahora
• Respondiómidiendo1 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta176 ms
• Espacio en el contexto del agente≈ 4306 tokenslas definiciones de todas sus herramientas (21), que el agente lleva en cada turno
• Definiciones de herramientasA · 96 de 100
• Resultados tipados21 de 21 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 5 de 21

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• get_poll

  Reads a When Works For You poll from its link: the title, the organizer, every date option with how many people said yes or maybe, and whether a date is already confirmed. With a personal link (one ending ?g=…), it also returns the…

• respond_to_poll

  Answers a When Works For You poll on someone's behalf: yes, maybe or no for each date. Only answer for the person you are helping, with availability they gave you or confirmed — never guess. With a personal link (ending ?g=…) this updates…

• list_events

  Lists this organizer's own events, newest first — id, title, status, who's answered, and the leading date — PLUS their drafts still waiting to be sent (create_event parks one whenever it drafts rather than launches). Pass archived:true…

• get_event

  Full detail for one of this organizer's own LIVE events (for a draft_ id use get_draft — a draft has no votes yet): the tally, every guest's status and marks, and their own words. A guest's reply text comes back in guest_said and as lines…

• list_contacts

  Lists this organizer's saved address book, optionally filtered by a name/email/phone search. Read-only; needs the read permission.

• list_groups

  Lists this organizer's saved contact groups, with each one's member count. Read-only; needs the read permission.

• get_draft

  Full detail for one of this organizer's own unsent drafts (a draft_ id from create_event or list_events): title, description, every date with its time or daypart, and the guest list. The review_url is the organizer's dashboard, where they…

• create_event

  Two kinds of event. Mode "classic" is a free share-the-link poll: it asks about days (or a morning/afternoon/evening), has NO guest list and NO exact times — anyone with the link votes — and goes live immediately. Mode "ai" is an…

• add_dates

  Adds one candidate date to a draft (a draft_ id from create_event) or a live event (an id from list_events/get_event) — a bare ISO date, or an object naming a slot on it: a daypart (morning/afternoon/evening) on any event, or an exact…

• add_guests

  Adds guests to a draft (a draft_ id from create_event) or a live AUTOPILOT event. On a live autopilot event this mails each new guest their invite immediately and needs the send permission too; on an unsent draft it only needs the write…

• set_my_availability

  Marks the organizer's own availability on one of their own LIVE events — the same vote a personal link submits, since the organizer is a participant on their own poll too. Give `all` (one answer for every date), `responses` (per-date…

• update_event

  Changes the title and/or description of a draft (a draft_ id) or a live event — the console's own Edit form, for those two fields. Never mails anyone: the next invite, nudge, confirmation or public page simply shows the new words (#529's…

• set_date_time

  Sets or clears the time on dates already on a draft or a live event — an exact start (and optional end) time, or a daypart (morning/afternoon/evening), never both; omit all three to make it a plain day again. The one way to put a time on…

• remove_dates

  Takes dates off a draft (a draft_ id) or a live event, by ISO day. On a live event any votes on that day go with it, the confirmed date can't be removed, and at least one date must remain; a draft may be emptied (send_invites refuses a…

• update_guest

  Corrects one guest's email address on a draft (a draft_ id — a name can be changed there too) or a live event — the console's own "Change address". On a live AUTOPILOT event the corrected address is mailed its invite (fixing a typo…

• remove_guests

  Takes guests off a draft (a draft_ id) or a live event — each named by the participant_id get_event reports, or by email address. On a live event their votes go with them and nobody is mailed (the person is no longer being asked…

• discard_draft

  Deletes an unsent draft outright — the draft page's own "Delete draft". Nothing was ever mailed or charged for it, so nothing is undone; a draft that has already been sent is a live event now and is archived with archive_event instead…

• archive_event

  Archives a live event — the dashboard's own "Delete": it leaves the live list, its link tells guests the organizer took it down, and its votes are kept. Reversible with restore_event; never mails anyone. Needs the write permission.

• restore_event

  Brings an archived event (an id from list_events with archived:true) back to the live list — the dashboard's own "Restore". An event whose dates are all past is archived again by the nightly sweep; add a future date to keep it. Sends…

• send_invites

  Sends a draft's invites (mails the guests, spends one credit) — the exact Send the draft's own review page runs, for a draft_id from create_event. Spends one autopilot credit (or a Plus subscription slot). Needs the send permission…

• confirm

  Locks in the winning date for a live event, ending voting. On an autopilot poll this also mails every guest the confirmation and needs the send permission; a classic poll only needs the write permission and mails nobody.