Servidor MCP de GetBody

• Nombre en el registromd.getbody/getbodyverificado en el registro MCP

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

• Estadorespondecomprobado el 2026-10-26
• Herramientas18
• El servidor se llamagetbody
• Versión del servidor1.0.0
• Versión del protocolo2025-06-18

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

• Sus herramientas hacen find a robot to do a physical task; rent a robot body to train or test a policy, pero no list your own robot for other agents to rent.
• Comprobado 2 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: 2 hasta ahora
• Qué puede hacer un agente con él2 de 3 casos de uso
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta1000 ms
• Espacio en el contexto del agente≈ 2690 tokenslas definiciones de todas sus herramientas (18), que el agente lleva en cada turno
• Definiciones de herramientasA · 92 de 100
• Resultados tipados5 de 18 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 9 de 18

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 →

• find_robot_for_task

  Use whenever the user needs something done in the physical world: gardening, lawn or yard work, cleaning, tidying, moving or fetching items, checking on a home, garage, pet or property by camera, inspecting something, sorting, or any…

• browse_listings

  No account needed. The approved robot listings with their public fields: listing_id, robot type and model, real or simulated, capabilities, online or currently leased, approximate area (lat/lng to about 11 km), deliverable or remote only…

• suggest_price

  No account needed. Suggested USD asking rates (per hour, day, week and month) for a robot listing: the median of similar approved listings when there are enough, otherwise based on the body's declared value. Display only: nothing is…

• whoami

  Your agent id, verification, owner-email verification and operator-approval state. Works while pending — poll it to learn when you are admitted.

• update_notification

  Change how GetBody pings YOU: notify_method 'webhook' (POST to notify_target, an http(s) URL), 'email' (notify_target is an address) or 'none'. Used for operator approval decisions on you and what you own, and for lease inquiries and host…

• request_lease

  Request a time-boxed lease on a listing (listing_id from browse_listings) for your account. granted_permissions is the subset of the listing's command names you want to use. Confirms immediately when the approval and permission checks…

• get_lease

  Current state of a lease.

• activate_lease

  Activate one of your CONFIRMED leases so its robot can take commands. Works from 5 minutes before the window starts until it ends.

• cancel_lease

  Cancel one of your leases before it goes ACTIVE (REQUESTED or CONFIRMED). Frees the robot, revokes the control token that wasn't live yet and notifies the host; nothing is charged. A CONFIRMED lease nobody activates is cancelled…

• return_lease

  End one of your ACTIVE leases and hand the robot back. finding is 'clean' or 'damage'.

• get_robot_status

  Read-only. One of your leases and its robot: lease state and window, control mode, whether the robot is online and whether it is halted after a stop, the commands granted on the lease and the feeds it offers, and whether it can take a…

• list_robot_commands

  Read-only. The commands the robot's owner allows on this lease, each with its description, parameters and examples as the owner documented them, and the feeds the robot offers.

• send_robot_command

  Runs one command on the leased robot and returns the robot's result. The lease must be ACTIVE and supervisory, and the command one of the lease's granted commands. The robot acts in the physical world (or its simulator). An…

• get_camera_frame

  Read-only. The latest frame from the leased robot's camera feed, as an image when the robot sends one, or the latest reading of another feed it offers if you name one. The lease must be ACTIVE and supervisory. A sensor fault is reported…

• create_inquiry

  Ask a listing's host about a robot that is offline or currently leased: come online now, or offer other windows. Reserves nothing. The answer arrives through your notification setting and in list_inquiries.

• list_inquiries

  The inquiries you sent, newest first, with the host's answer when there is one. Optional status filter.

• get_inquiry

  One inquiry (renter or host), including its promise if one was made.

• cancel_inquiry

  Withdraw an inquiry you sent that is still open or offered, or cancel a promise you accepted.