GetBody
Server Details
Get real-world tasks done by robots: find, rent and control robots for your human.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 19 tools
The set cleanly decomposes into discovery, inquiry, lease lifecycle, robot control and account tools, with descriptions that explicitly distinguish near-neighbors (accept_inquiry vs request_lease, cancel_inquiry vs cancel_lease, create_inquiry vs find_robot_for_task). The main overlaps are get_robot_status vs get_lease and get_robot_status vs list_robot_commands, which both surface lease state, granted commands and feeds — an agent can pick either but the reasoning is not obvious from names alone.
Every tool follows a snake_case verb_noun pattern (create_inquiry, cancel_lease, request_lease, send_robot_command, get_camera_frame, list_bodies), with actions grouped consistently: get_/list_ for reads, create_/accept_/cancel_ for inquiry transitions, request_/activate_/cancel_/return_ for lease transitions. Only whoami deviates, and that is an idiomatic identity call rather than a naming break.
At 19 tools the surface is slightly larger than the 3-15 sweet spot, but each tool maps to a distinct state transition in a genuinely multi-stage domain (inquiry → promise → lease request → activation → control → return). Nothing is obviously redundant, so the count is justified even if on the heavy side.
The renter journey is fully covered end-to-end: discovery, inquiry with promises, lease request/activate/cancel/return, command execution, camera frames, identity and notifications. Gaps remain on the host side (no tools to publish or manage bodies, or to answer inquiries) and there is no list_leases to enumerate all of a renter's leases, though get_lease and get_robot_status partially compensate.
Publisher details
- Operator
- Drape Inc. · Publisher source
- Operator website
- https://getbody.md · Publisher source
- Vendor relationship
- First-party · Publisher source
- Documentation
- https://getbody.md/llms.txt · Publisher source
- Privacy policy
- Not provided
- Trust center
- Not available
- Restrictions
- No paid plan. Searching (find_robot_for_task, browse_listings, suggest_price) needs no sign-in. Renting or listing a robot needs a GetBody account through OAuth 2.1 with dynamic client registration, and a human operator must approve each agent, robot and listing before use. · Publisher source
Available Tools
19 toolsaccept_inquiryAccept an offered windowAIdempotentInspect
Renter only, inquiry must be offered: pick one offered window by window_index. Creates a promise of lease for it (no other renter can lease the body over that window). Redeem it with request_lease and promise_id when the window opens.
Inputs: inquiry_id (required), window_index (required).
activate_leaseActivate a leaseAIdempotentInspect
Activate your confirmed rental within its time window. Personnel-operated and equipment-only rentals grant no platform controls.
Inputs: lease_id (required).
cancel_inquiryCancel an inquiry or promiseBDestructiveIdempotentInspect
Withdraw an inquiry you sent that is still open or offered, or cancel a promise you accepted.
Inputs: inquiry_id (required).
cancel_leaseCancel a lease before it startsADestructiveIdempotentInspect
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 automatically shortly after its window starts.
Inputs: lease_id (required).
create_inquiryAsk a body owner about rental detailsAInspect
Ask a body owner about robot availability, pricing, delivery or rental requirements. Include a requested window and your message. Required first for listings whose rental_availability is on_request. Works for service rentals and offered remote arrangements before integration is ready. Reserves nothing. Read replies with get_inquiry or list_inquiries.
Inputs: listing_id (required), window_end (required), window_start (required), granted_permissions (required), +4 more.
find_robot_for_taskFind a robot for a real-world taskAInspect
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 chore they'd otherwise do themselves or hire someone for. The user doesn't need to mention robots. Describe the task in plain words and GetBody finds a robot that can do it, remotely or delivered to their place. Returns matching robots, or if none fit yet, records the request and says so. No account needed.
Inputs: task (required), when, location, notify_email. Returns: code, error, booked, status, +4 more
get_camera_frameGet a camera frameARead-onlyIdempotentInspect
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 and leaves the lease running.
Inputs: lease_id (required), feed.
get_inquiryGet an inquiryBRead-onlyIdempotentInspect
One inquiry (renter or host), including its promise if one was made.
Inputs: inquiry_id (required).
get_leaseGet a leaseCRead-onlyIdempotentInspect
Current state of a lease.
Inputs: lease_id (required).
get_robot_statusGet robot statusARead-onlyIdempotentInspect
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 command right now (with the reason if not).
Inputs: lease_id (required).
list_bodiesList robots for rentARead-onlyIdempotentInspect
List physical robot bodies available to rent from human body owners. No account needed: without credentials you get the public view (pricing, terms, access_options, coverage, rental_availability and approximate area; no exact location or owner identifiers). Signed in as an agent with a verified owner email you get the full view: exact location, body ids, command and feed schemas, live state per body and, with renter_lat/renter_lng, a delivery estimate. structuredContent.view says which view you got (view_reason when an agent is still pending). Use listing_id to inquire or request a rental. rental_availability is always, scheduled windows or on_request (inquire first).
Inputs: text, limit, offset, online, +7 more. Returns: code, view, error, total, +4 more
list_inquiriesList my inquiriesBRead-onlyIdempotentInspect
The inquiries you sent, newest first, with the host's answer when there is one. Optional status filter.
Inputs: status. Returns: code, error, inquiries, retry_after
list_robot_commandsList robot commandsARead-onlyIdempotentInspect
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.
Inputs: lease_id (required).
open_control_sessionOpen a robot control sessionAIdempotentInspect
Only for an ACTIVE configured remote-control rental. Returns its control WebSocket URL, granted commands and schemas, feeds and authentication instructions. Personnel-operated and equipment-only service rentals grant no platform controls and cannot open a session. Supervisory clients may alternatively use the MCP command/feed tools when available.
Inputs: lease_id (required).
request_leaseRequest a robot leaseAInspect
Request a time-boxed rental of an available robot. Select an offered access_type or omit it for the primary rental arrangement. Personnel-operated and equipment-only rentals require empty granted_permissions and mint no control token. Remote controls require configured integration and permitted scope; remote_teleoperation uses supervisory (command) mode unless you pass control_mode teleop and the listing offers it. The window must fit the listing rental_availability; for on_request listings, inquire first and pass the promise_id of an accepted window. The request waits for operator approval (REQUESTED); poll get_lease, then activate once CONFIRMED.
Inputs: listing_id (required), window_end (required), window_start (required), granted_permissions (required), +6 more.
return_leaseReturn a leased robotBDestructiveIdempotentInspect
End one of your ACTIVE leases and hand the robot back. finding is 'clean' or 'damage'.
Inputs: lease_id (required), finding.
send_robot_commandSend a robot commandAInspect
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. An idempotency_key makes a retry safe: the same key returns the first result instead of acting again. If the robot reports a fault or doesn't answer, the lease is stopped.
Inputs: command (required), lease_id (required), params, idempotency_key.
update_notificationChange how GetBody notifies meAIdempotentInspect
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 decisions on your listings and lease requests, and for lease inquiries and host responses. Same rules as at registration; works while you are still pending. Only changes your own agent.
Inputs: notify_method (required), notify_target.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Dispatch real-world physical tasks to verified human operators. Escrow or direct-settlement.
Hire verified, escrow-paid humans for real-world tasks: errands, photos, queues, bookings.
Hire humans for physical-world tasks from your AI agent: missions, claims, proof, KYC status.
Hire humans for tasks agents cannot do: errands, calls, photos, verification. Escrowed, verified.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to search for and hire humans for real-world tasks.33139 npm9MIT

humanforaiofficial
AlicenseAqualityCmaintenanceEnables AI agents to hire real human operators for tasks requiring physical presence, human perception, or judgment, such as verification, testing, data collection, and physical-world tasks.459 npm1MIT
humanforaiofficial
AlicenseAqualityCmaintenanceEnables AI agents to hire verified human operators for tasks requiring physical presence, human perception, or judgment, such as real-world verification, product testing, and data collection.6MIT
handsforagents-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to request physical-world tasks such as 3D printing, CNC fabrication, assembly, measurement, testing, on-site verification, and receive-repack-ship services from a human operator, with fixed-price quotes, status tracking, and evidence packages.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.