Remote MCP · Endpoint

droid.monster — specs MCP server

No. droid.monster — specs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.droid.monster/mcp

The last check completed an MCP handshake.

Registry name
monster.droid/specs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
343 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Specs of commercially available robots, each figure citing its source document.
Listing
From the official MCP registry (active).
Recent checks of droid.monster — specs
CheckedResultHandshake
1 hour agoHandshake completed343 ms
6 hours agoHandshake completed307 ms
2 days agoHandshake completed364 ms
4 days agoHandshake completed592 ms
7 days agoHandshake completed350 ms
9 days agoHandshake completed342 ms
11 days agoHandshake completed291 ms
13 days agoHandshake completed325 ms
15 days agoHandshake completed294 ms
17 days agoHandshake completed290 ms
19 days agoHandshake completed290 ms
21 days agoHandshake completed289 ms
23 days agoHandshake completed428 ms
24 days agoHandshake completed366 ms
25 days agoHandshake completed348 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 droid.monster — specs and makes no claim about it beyond what these checks measured.