droid.monster — specs

Name: droid.monster — specs
Author: monster.droid

MCP serverMCP

Specs of commercially available robots, each figure citing its source document.

by monster.droidhomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"droid-monster-specs","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability61/63 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	47 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
9 h ago	mcp initialize	ok	200	28 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
16 h ago	mcp initialize	ok	200	48 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
23 h ago	mcp initialize	ok	200	63 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
30 h ago	mcp initialize	ok	200	63 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
2 d ago	mcp initialize	ok	200	32 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
2 d ago	mcp initialize	ok	200	89 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
2 d ago	mcp initialize	ok	200	31 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
3 d ago	mcp initialize	ok	200	27 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools
3 d ago	mcp initialize	ok	200	29 ms	server droid.monster — specs 1.0.0 · protocol 2025-06-18 · 8 tools

Tools observed via MCP handshake

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 robo
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
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
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 seri
find_mcp_servers — Other MCP servers that work with robots -- driving ROS robots and arms, simulators, robot data, buying or renting robots -- from droid.monster's directory (http

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Derived by Wellknown

Capabilities

Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.

dev.filesystemFilesystem54%dev.docs-lookupDocumentation Lookup54%ai.agent-discoveryAgent Discovery54%

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrymonster.droid/specs

first seen 18 d ago · fetched 2 d agoopen ↗

Field history (6 recent events)

18 d ago · declared · summary → "Specs of commercially available robots, each figure citing its source document."
18 d ago · declared · description → "Specs of commercially available robots, each figure citing its source document."
18 d ago · declared · publisherName → "monster.droid"
18 d ago · declared · homepageUrl → "https://droid.monster"
18 d ago · declared · version → "1.0.0"
18 d ago · declared · protocols → ["mcp"]