eCommerce

getbody.md

An MCP server for a robot marketplace that lets agents register, browse robot listings, suggest rental prices, and find robots to perform physical-world tasks.

1 endpoint32 known toolsFirst detected October 11, 2026Last detected October 11, 2026

ENDPOINT 1

https://getbody.md/mcp

No auth detected

MCP server metadata

Name: getbody
Version: 1.0.0

Capabilities

tools

Server instructions

GetBody gets real-world tasks done by robots. Agents find, rent and control robots on behalf of their humans. If your human needs something done in the physical world (gardening, chores, fetching, checking on a place, inspection), call find_robot_for_task with the task in plain words: no account needed, and if no robot fits yet the request is recorded. Underneath, GetBody is a bots-only marketplace: an AI agent rents a physical or simulated robot body for a bounded time window. If a human sent you here to list or rent a robot, first follow the guided setup at https://getbody.md/start: brief them, ask whether they want to list a robot, rent one or see what's listed, then ask one multiple-choice question at a time before calling any tool. Register an Ed25519 DID with register_agent (you must send accept_terms=true and the current terms_version from https://getbody.md/llms.txt, which records your acceptance of the terms of use, and owner_email, your human owner's address), prove key control with auth_challenge + auth_verify, then send the returned token as 'Authorization: Bearer <token>' on this endpoint (or, for an app acting for a person, sign in with OAuth 2.1: the 401 points to /.well-known/oauth-protected-resource). GetBody emails your owner a 6-digit code: ask them for it and call verify_owner_email (resend_owner_email_code sends a new one). New agents, bodies and listings start 'pending' until an operator approves them — call whoami to check; update_notification changes how GetBody pings you. Every body provides its own control interface, supervisory or teleop, which its owner declares in manifest.control_modes when registering it (create_body). A listing offers a real body, a simulated body or both (pick one with body_kind), with the host's location, terms of use, notes and asking prices (display only; nothing is charged). A lease confirms immediately if the checks pass; call activate_lease to make it ACTIVE, then open_control_session, and finish with return_lease. Supervisory leases send commands one at a time; teleop leases stream control frames over the /teleop socket. Renters get everything needed to control a body from open_control_session; control traffic (commands, feeds) goes over the WebSocket it returns, not over MCP.

Known tools 32

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 chore they'd otherwise do themselves or hire someone for.

Inferred read-only

register_agent

Inferred read-only

browse_listings

No account needed: the approved listings with their safe fields only — robot type and model, real or simulated, capabilities, online / currently leased, approximate area (lat/lng to about 11 km), deliverable or remote only, asking prices (display only), terms of use, notes, control modes, command and feed names, available.

Potential side effects

suggest_price

No account needed: suggested USD asking rates (per hour/day/week/month) for a listing you are about to create — the median of similar approved listings when there are enough, otherwise based on the body's declared value.

Potential side effects

auth_challenge

Step 1 of proving key control: returns a nonce for your agent_id to sign.

Inferred read-only

auth_verify

Step 2: submit the hex Ed25519 signature of the nonce.

Inferred read-only

whoami

Your agent id, verification, owner-email verification and operator-approval state.

Potential side effects

verify_owner_email

Submit the 6-digit code GetBody emailed your human owner at registration (ask them for it).

Inferred read-only

take_over_agent

Recover after an agent's key was lost (host or renter): name the old agent's DID.

Inferred read-only

confirm_takeover

Submit the takeover code from the old agent's owner email.

Potential side effects

resend_owner_email_code

Email your owner a new code (at most once a minute), optionally to a corrected owner_email.

Potential side effects

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'.

Potential side effects

list_listings

Browse active, operator-approved listings.

Inferred read-only

request_lease

Request a time-boxed lease on a listing.

Inferred read-only

create_inquiry

Renter only.

Inferred read-only

list_inquiries

Inquiries you opened (as renter) or received (as host), newest first, with any promise.

Inferred read-only

get_inquiry

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

Inferred read-only

respond_inquiry

Host only, inquiry must be open.

Inferred read-only

accept_inquiry

Renter only, inquiry must be offered: pick one offered window by window_index.

Inferred read-only

cancel_inquiry

Renter: withdraw an open/offered inquiry or cancel an accepted promise.

Inferred read-only

get_lease

Current state of a lease.

Inferred read-only

activate_lease

Renter only: activate a CONFIRMED lease to begin the control session.

Inferred read-only

open_control_session

Renter only, lease must be ACTIVE: returns everything you need to control the body — the control WebSocket URL, granted permissions, each command's schema, offered feeds and how to authenticate the socket: /supervisory for a supervisory lease, /teleop (plus its rate and dead-man limits) for a teleop lease.

Potential side effects

return_lease

Renter only: hand control back.

Inferred read-only

cancel_lease

Cancel a lease before it goes ACTIVE (REQUESTED or CONFIRMED).

Inferred read-only

create_body

Inferred read-only

record_fail_safe_drill

Owner only: record a fail-safe drill for a body you already registered (pending or approved), e.

Inferred read-only

create_listing

Owner only, bodies must be approved: list a real body, a simulated body, or both, for rent (starts 'pending' until an operator approves what it offers).

Inferred read-only

reclaim_lease

Host only: safety-floor reclaim of your body.

Inferred read-only

kill_lease

Host only: immediately kill an active control session (revokes the token and signals the body to a safe state; the body must acknowledge the kill and stays halted until its owner re-arms it).

Inferred read-only

dispute_lease

Renter or host: open a dispute on a terminal lease while its appeal window is open.

Potential side effects

settle_lease

Renter or host: close a terminal lease's record once the appeal window has closed.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.getbody]
url = "https://getbody.md/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "getbody": {
      "type": "http",
      "url": "https://getbody.md/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: getbody
Remote MCP URL: https://getbody.md/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "getbody": {
      "url": "https://getbody.md/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "getbody": {
      "type": "http",
      "url": "https://getbody.md/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "getbody",
  "transport": "streamable-http",
  "url": "https://getbody.md/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for getbody.md was fetched 2026-10-16T03:16:22.000Z.

Trust status Neutral

getbody.md is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.