Remote MCP · Endpoint

GetBody MCP server

No. GetBody answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://getbody.md/mcp

The last check completed an MCP handshake.

Registry name
md.getbody/getbody
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
661 ms
Tools exposed
18 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Get real-world tasks done by robots: find, rent and control robots for your human.
Listing
From the official MCP registry (active).
Recent checks of GetBody
CheckedResultHandshake
2 hours agoHandshake completed661 ms
1 day agoHandshake completed682 ms
2 days agoHandshake completed724 ms
3 days agoHandshake completed742 ms
4 days agoHandshake completed849 ms
5 days agoHandshake completed706 ms
7 days agoHandshake completed1.32 s
9 days agoHandshake completed271 ms
12 days agoHandshake completed871 ms
14 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed729 ms
18 days agoHandshake completed674 ms
20 days agoHandshake completed676 ms
22 days agoHandshake completed660 ms
24 days agoHandshake completed633 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with GetBody and makes no claim about it beyond what these checks measured.