droid.monster — specs

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as monster.droid/specs and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 6 Oct 2026. Not supplied by the maker.

• search_robots

  Find robots by name, maker or kind of robot. Returns each robot's reference for the other tools, and how many specs we hold for it.

• find_robots

  Filter robots by published figures, e.g. payload at least 20 kg and reach at least 1300 mm, optionally within a category or maker, sorted by a figure. Only robots that publish every filtered figure ca

• get_robot

  Everything we hold on one robot: each spec in its canonical unit, the value as the maker published it, and the document it came from.

• compare_robots

  Two to four robots side by side, one row per figure any of them publishes. A robot that doesn't publish a figure shows null (unknown).

• list_attributes

  The figures we record (the keys find_robots filters on), with canonical units, allowed values, and how many robots publish each. Give a category to see only the figures that apply to it.

• lookup_error_code

  What a robot maker's error code means: its title, the likely causes the maker lists, and a link to the page of the maker's document. Currently Universal Robots and ABB.

• find_parts

  Spare parts that fit a robot, each with the part number, the document that says it fits (the maker's catalogue or manual, or an authorised seller), and the series it is scoped to.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.