Databases

droid.monster

Provides tools for searching, filtering, retrieving, and comparing robot specifications, makers, and attributes from a curated robot database.

1 endpoint7 known toolsFirst detected October 6, 2026Last detected October 6, 2026

ENDPOINT 1

https://api.droid.monster/mcp

No auth detected

MCP server metadata

Name: droid.monster — specs
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Specifications of commercially available robots (cobots, industrial arms, humanoids, quadrupeds, AMRs, grippers and more). Every figure cites the document it came from; quote the source when you use one. Numbers are in each attribute's canonical unit (list_attributes), with the value as the maker published it alongside. A robot with no figure for something is unknown, not zero: say so rather than guess. Robots are referenced as "maker/model" (e.g. "universal-robots/ur20").

Known tools 7

search_robots

Find robots by name, maker or kind of robot.

Inferred read-only

find_robots

Filter robots by published figures, e.

Inferred read-only

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.

Inferred read-only

compare_robots

Two to four robots side by side, one row per figure any of them publishes.

Inferred read-only

list_attributes

The figures we record (the keys find_robots filters on), with canonical units, allowed values, and how many robots publish each.

Potential side effects

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.

Inferred read-only

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.

Inferred read-only

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.droid-monster-specs]
url = "https://api.droid.monster/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "droid-monster-specs": {
      "type": "http",
      "url": "https://api.droid.monster/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: droid-monster-specs
Remote MCP URL: https://api.droid.monster/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": {
    "droid-monster-specs": {
      "url": "https://api.droid.monster/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "droid-monster-specs": {
      "type": "http",
      "url": "https://api.droid.monster/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "droid-monster-specs",
  "transport": "streamable-http",
  "url": "https://api.droid.monster/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

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