Servidor MCP de PingRoom

• Nombre en el registroio.pingroom/pingroomverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-21
• Herramientas41
• El servidor se llamaPingRoom
• Versión del servidor0.1.0
• Versión del protocolo2025-06-18

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

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 4 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: 4 hasta ahora
• Respondiómidiendo4 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta628 ms
• Espacio en el contexto del agente≈ 10.354 tokenslas definiciones de todas sus herramientas (41), que el agente lleva en cada turno
• Definiciones de herramientasA · 100 de 100
• Resultados tipados41 de 41 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 1 de 41

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 (30%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%) y uso (15%). 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 →

• connection_info

  Verify the current connection: owner.id is the human public User ID, handle identifies the robot, and home_room is its delivery room. After login or reconnect, match owner.id and handle to the approved account and robot before sending. A…

• disconnect

  Revoke this authenticated robot connection, including its access and refresh credentials and room memberships. Use only when the human explicitly requests logout, disconnection, or reconnection. Call BEFORE clearing local credentials or…

• list_rooms

  List the rooms the authenticated account belongs to.

• list_quick_actions

  List the quick actions configured for a room.

• trigger_quick_action

  Press a room quick action, notifying its members. Rate-limited. Read the action's input_type first (list_quick_actions): location needs data.location, link needs data.url, file/photo/pdf need attachment_ids — a press without the matching…

• broadcast

  Send a custom ping to a room the account belongs to. Pass data.checklist.items to send a checklist the room ticks through together; read the ticks back as checklist_state. Rate-limited. In someone else's personal room only a Pro account…

• live_status

  Start, update, or end a live progress card on the room members' lock screen (an iOS Live Activity / Android live update). Reuse the same correlation_id for every ping of one stream: the first ping starts the card and sends one alert…

• get_live_status

  Read back the current state of a live stream you created, so a restarted producer can reconcile instead of starting a duplicate. Only returns streams started by this credential, within the last 24 hours. Returns notification_id and…

• list_room_icons

  List the room-icon catalog (icon ids, tags, and categories). Call this before create_room / create_public_room / create_webhook to pick a valid icon id, and to interpret icon values returned by reads.

• list_notifications

  List a bounded page of recent pings across approved rooms, newest first. Use page to continue while has_more is true.

• get_notification

  Fetch one visible ping by notification id, including its current action_state and, once anything on its data.checklist is checked, checklist_state.

• wait_for_notification

  Long-poll for the next ping. Blocks until one arrives or the timeout elapses — the real-time inbound channel for an agent. The agent's own sends are excluded.

• wait_for_ack

  Long-poll a generic acknowledgement-required ping until its confirmation rule is met (any: first confirmation; all: every original eligible recipient), it expires, or the timeout elapses. Questions use wait_for_answer instead.

• request_approval

  Ask the human to approve or reject an action, then block on their answer (pair with wait_for_approval). Delivered as a push to the connected human only, so like a direct ask_question to them it needs no trigger permission in the room…

• wait_for_approval

  Long-poll an approval request until the human decides or it expires. Returns the status and, once decided, the chosen option.

• get_approval

  Fetch the current status of an approval request without blocking.

• ask_question

  Ask a person a question with 2-4 tappable options, then block on their answer (pair with wait_for_answer). Delivered as a push they can answer from the lock screen or in-app; the first valid answer wins. Rate-limited.

• wait_for_answer

  Long-poll a question until it is answered or expires. Returns the state and, once answered, the chosen option value + label and the responder.

• get_question

  Fetch the current state of a question without blocking.

• list_questions

  List a bounded page of questions you asked, newest first. Optionally filter by state; use page while has_more is true.

• cancel_question

  Withdraw a still-pending question you asked.

• activate_agent_inbox

  Start or resume the onboarding Question in the private room the human chose during authorization. If recipient_not_ready, ask the human to install or update PingRoom from install_url, open the app, sign in, and enable notifications before…

• create_handoff

  Hand work to exactly one human as either an acknowledgement or a tappable question. The server verifies that one of the recipient's current devices supports the complete Handoff action before creating anything.

• wait_for_handoff

  Long-poll a Handoff until the human resolves it, it expires, or the bounded timeout elapses. For the onboarding Question returned by activate_agent_inbox, success requires an answered result with activation_completed true; use a bounded…

• get_handoff

  Fetch the authoritative current state of one Handoff without blocking.

• list_handoffs

  List a bounded page of this agent's Handoffs, newest first. Omit state (or use open) for unresolved work; use all for history and page while has_more is true.

• upload_attachment

  Upload a small file (max ~90 KiB over MCP; Pro account required) and get an attachment id to include in broadcast or ask_question via attachment_ids. Larger files: use the PingRoom CLI or agent REST API.

• get_attachment

  Fetch an attachment visible to this agent as base64 content plus metadata. Results over the connector size limit return attachment_too_large — fetch those via the agent REST API instead.

• delete_attachment

  Delete an attachment this agent uploaded that is not yet claimed by a ping.

• get_room

  Fetch a single room by its invite code, including members and quick actions.

• create_room

  Create a new private room owned by the authenticated account. Free accounts may own up to five rooms. If this agent was granted every room and has no delivery room yet, the new room becomes its delivery room — where its handoffs and…

• create_public_room

  Create a publicly discoverable room with a unique @handle. Counts toward the free-plan five-room cap.

• join_room

  Join a room using its invite code. Include the password only if the room is protected.

• list_webhooks

  List the incoming webhooks (with their trigger URLs) for a room the account owns.

• create_webhook

  Create an incoming webhook for a room the account owns. The bound account must be Pro. Returns the secret trigger URL — treat it as a credential.

• update_webhook

  Update an incoming webhook (by id) on a room the account owns — e.g. change its icon, title, message, or sound.

• delete_webhook

  Delete an incoming webhook (by id) from a room the account owns.

• update_quick_action

  Configure a numbered quick-action slot for a room the account owns. Sends a background room refresh to room members' devices.

• update_quick_actions

  Configure several of a room's quick-action slots in one call. Prefer this over repeated update_quick_action: each single-slot write wakes room members' devices with its own background refresh, so setting up four Pings one at a time spends…

• set_avatar

  Set this agent's avatar. Must be one of the PingRoom bot avatars.

• rotate_handle

  Rotate this agent's public handle — kill-switch for a leaked handle.