_ registry / mcp + a2a streamable-http · checked 1h ago

geppetto-robot-directory

https://geppettorobotdirectory.com

Registry code: e006a037659b76a3

api record

Query the world's robot directory - 812 robots across 30 categories and 319 brands. Tools: search_robots (by category, brand, price, use case), get_robot and get_robot_full (complete specs), compare_robots (side-by-side diff), get_category, and get_job_automation_risk (robot displacement scores for 240+ professions - data available nowhere else). All reads public, no auth.

from a public catalogue that lists it, not from the operator

endpoint
https://geppettorobotdirectory.com/functions/mcpServer
door code
2572d7055c36d142
protocol
streamable-http ·2025-06-18
authentication
bearer
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is geppetto-robot-directory live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is geppetto-robot-directory free to use?
Yes — the hub reached it with no key and no payment.
What tools does geppetto-robot-directory have?
10 tools: get_dataset, get_component_category, get_supplier, get_job_automation_risk, get_robot, compare_robots, get_category, search_datasets, ….
Is geppetto-robot-directory safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 99.1%· all time 99.1%

latency
431ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 546 checks · signed record
  • unknown → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
iot & hardware robotics
used for
  • search robots by category or price
  • get a robot's specs
  • compare two robots
  • get automation risk for a profession
takes → gives
text → data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 10 tools
2 open 8 never probed 2 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_robots reads open 14h ago

    Search Geppetto's directory of 830+ robots by category, brand, price range, or use case. Returns robot name, slug, category, brand, price range, and key specs.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Search term, category, or use case. Examples: humanoid, robot vacuum, lawn mower, cobot"
    },
    "category": {
      "type": "string",
      "description": "Robot category slug. Options: humanoid, cleaning, lawn, aerial, medical, security, agricultural, delivery, industrial, companion, educational, inspection"
    },
    "maxPrice": {
      "type": "number",
      "description": "Maximum price in USD"
    }
  }
}
    arguments 17 lines
  • search_suppliers open 11h ago

    Search Geppetto's directory of 140+ robot hardware component suppliers by component category, country, or keyword. Returns name, slug, component category, country, public-listing/stock code, and bottleneck risk.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text search over supplier name and component description"
    },
    "country": {
      "type": "string",
      "description": "Country the supplier is in, as a full name or ISO-2 code: China/CN, Japan/JP, Germany/DE, United States/US, Switzerland/CH, Taiwan/TW, Sweden/SE, Australia/AU"
    },
    "component": {
      "type": "string",
      "description": "Component category slug, e.g. reducers, motors, sensors"
    }
  }
}
    arguments 17 lines
  • get_dataset unknown never probed

    Get the full record for a specific robot training dataset by slug: specs, license, access type, collection method, citation, and source links.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Dataset slug e.g. droid, open-x-embodiment, ego4d, aloha-bimanual"
    }
  }
}
    arguments 12 lines
  • get_component_category unknown 11h ago

    Get a robot hardware component category (a 'part' type) by slug, with its supply-chain analysis and full supplier list: bottleneck risk, China concentration, supplier counts, and each supplier.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category_slug"
  ],
  "properties": {
    "category_slug": {
      "type": "string",
      "description": "Component category slug: reducers, motors, sensors, screws, hand-units, actuators, bearings, materials, castings, intelligence, pcbs, assemblies, data, periphery, other"
    }
  }
}
    arguments 12 lines
  • get_supplier unknown 11h ago

    Get the full record for a specific robot hardware supplier by slug: components supplied, OEM relationships, country, public-listing and stock code, bottleneck risk, and sources.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Supplier slug e.g. harmonic-drive-systems, leaderdrive, nabtesco, catl"
    }
  }
}
    arguments 12 lines
  • get_job_automation_risk reads unknown 8h ago

    Get the Geppetto Robot Impact Score (0-100) for any profession. Composite of task-automation research (35%, the Oxford Frey and Osborne score), IFR robot deployment (30%), an academic-consensus score (20%, the average of the Oxford score and the OECD risk band), and robot density (15%). The O*NET-SOC code is a cross-reference only, not a scoring input. Higher means more automation pressure on the occupation.

    mcp-tool

    {
  "type": "object",
  "required": [
    "profession_slug"
  ],
  "properties": {
    "profession_slug": {
      "type": "string",
      "description": "Profession slug e.g. warehouse-picker-packer, nurse-routine-monitoring, delivery-driver-last-mile, long-haul-truck-driver"
    }
  }
}
    arguments 12 lines
  • get_robot reads unknown 14h ago

    Get full specs and details for a specific robot by its slug. Returns all specifications, price, brand, description, features, and direct URL.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Robot slug e.g. agility-robotics-digit, roborock-s8-maxv-ultra, unitree-g1"
    }
  }
}
    arguments 12 lines
  • compare_robots reads unknown 19h ago

    Compare two robots side by side on specs, price, and capabilities. Returns a comparison URL and key differences.

    mcp-tool

    {
  "type": "object",
  "required": [
    "robot_a",
    "robot_b"
  ],
  "properties": {
    "robot_a": {
      "type": "string",
      "description": "First robot slug"
    },
    "robot_b": {
      "type": "string",
      "description": "Second robot slug"
    }
  }
}
    arguments 17 lines
  • get_category reads unknown 14h ago

    Get all robots in a specific category with specs and prices. Returns the full list of active robots in that category from the Geppetto directory.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category_slug"
  ],
  "properties": {
    "category_slug": {
      "type": "string",
      "description": "Category slug e.g. humanoid, cleaning, lawn, aerial, medical, security, agricultural, delivery, industrial, companion, educational, inspection"
    }
  }
}
    arguments 12 lines
  • search_datasets unknown never probed

    Search Geppetto's directory of 1,000+ robot training datasets by platform, modality, license, or commercial-use. Returns name, slug, platforms, sensor modalities, episode count, hours, license, access type, and URL.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Free-text search over dataset name, description, and source"
    },
    "license": {
      "type": "string",
      "description": "License identifier, e.g. apache-2.0, cc-by-4.0, mit"
    },
    "category": {
      "type": "string",
      "description": "Dataset type: real-robot, human-video, or sim"
    },
    "modality": {
      "type": "string",
      "description": "Sensor modality, e.g. rgb, depth, tactile, imu, lidar, force-torque"
    },
    "embodiment": {
      "type": "string",
      "description": "Robot platform used to collect the data, e.g. unitree-g1, franka, aloha, humanoid"
    },
    "commercialUse": {
      "type": "boolean",
      "description": "If true, only datasets cleared for commercial use"
    }
  }
}
    arguments 29 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e006a037659b76a3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e006a037659b76a3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e006a037659b76a3/badge.svg)](https://brick.blue/agent/e006a037659b76a3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
0
failed
1
success rate
0%
median latency
289ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.