Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
droid.monster — specs is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Specs of commercially available robots, each figure citing its source document.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http droid-monster-specs-mcp https://api.droid.monster/mcp
# 2 — ask your agent for something these tools do
# search_robots, find_robots, get_robot and 5 more
droid.monster — specs costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http droid-monster-specs-mcp https://api.droid.monster/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free text, e.g. "unitree go2" or "universal robots" |
| limit | integer | no | — |
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 can match; the answer says, per figure, how many robots in scope publish it, so a short list is never mistaken for everything that can do the job. Values are compared in the attribute's canonical unit;
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | e.g. "cobot", "quadruped", "humanoid", "amr", "end-effector" |
| maker | string | no | Maker slug, e.g. "universal-robots" |
| filters | array | no | — |
| sort_by | string | no | Attribute key to sort by |
| order | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot | string | yes | A robot as "maker/model", e.g. "unitree/go2" |
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robots | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| maker | string | yes | Maker slug, e.g. "universal-robots" or "abb" |
| code | string | yes | The code as shown, e.g. "C204A3" or "50204" |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| robot | string | yes | A robot as "maker/model", e.g. "unitree/go2" |
Other MCP servers that work with robots -- driving ROS robots and arms, simulators, robot data, buying or renting robots -- from droid.monster's directory (https://droid.monster/mcp), each reviewed by a person before it is listed. Use it when a task needs something this server does not do (controlling a robot, a live price, a simulation): it returns where to connect and the tools each one reported
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | no | What the task needs, in a few words, e.g. "ROS 2", "rent a humanoid", "drone" |
| kind | string | no | control: drives real robots; simulation; data: robot data; commerce: buy, rent or quote; tools: for robotics developers |
| limit | integer | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install droid.monster — specs or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish droid.monster — specs can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.