Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

RobotTraining.jobs

REMOTE · ROBOTTRAINING.JOBS

Search open robot training jobs (teleoperation, data collection, AV and drone tests) and their pay.

+3 this week 81 Trust /100

Last scanned (6 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 5 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 690 tokens (~230/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_robot_training_pay" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_robot_training_jobs” rewrote its description, which is the text the model reads security
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://robottraining.jobs/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=robottraining.jobs CN=YR1,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 RSA 2048 SHA256-RSA 640de403a66a025433423abeed0bb9c31ac
SANs: robottraining.jobs, www.robottraining.jobs
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of robottraining.jobs. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
jobs. present 47990 8 Verified
robottraining.jobs. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://js.stripe.com https://platform.twitter.com https://www.googletagmanager.com https://cdn.jsdelivr.net blob: https://pagead2.googlesyndication.com https://*.googlesyndication.com https://partner.googleadservices.com https://www.googletagservices.com https://adservice.google.com https://fundingchoicesmessages.google.com https://*.adtrafficquality.google; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://huggingface.co https://us.aws.cdn.hf.co https://cdn-lfs.huggingface.co https://cdn.jsdelivr.net https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.googletagmanager.com https://pagead2.googlesyndication.com https://*.googlesyndication.com https://*.doubleclick.net https://*.
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://robottraining.jobs/api/mcp Verified 200
http (plaintext) http://robottraining.jobs/api/mcp HTTPS enforced 308 https://robottraining.jobs/api/mcp
MCP tools · 3 exposed · ~534 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_robot_training_market ~103

How many robot training jobs are open right now, how many were listed in the last 7 days, and the open roles by kind of work and by employer (with each employer's slug for search_robot_training_jobs). Optionally scoped to the roles open to applicants in one country.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code (e.g. 'US', 'KE'): count only roles open to applicants in that country.

No output schema declared.

No examples provided.

get_robot_training_pay ~106

What robot training work pays per hour today, by kind of work: the median and the typical range (25th to 75th percentile) of the rates open roles advertise, with how many rates and employers each figure comes from. A rate is shown only when at least three employers advertise it. Name a kind of work to have its figure first.

NameTypeReqDescription
kindstring–Kind of work to answer first, e.g. 'teleoperation'. The other kinds follow.

No output schema declared.

No examples provided.

search_robot_training_jobs ~325

Search the open robot training jobs (paid work piloting, teaching, recording for and testing robots, autonomous vehicles and drones) across about 100 employers and programs such as Tesla, Figure, Waymo, Zipline, micro1 and Claru. Returns each role's title, employer, kind of work, advertised pay, where it is open and a link to apply on RobotTraining.jobs. All filters are optional.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 code (e.g. 'US', 'IN', 'BR'): only roles open to applicants in that country.
kindstring–Kind of work. One of the listed slugs, e.g. 'teleoperation', 'egocentric-wearable', 'av-drone-operator'.
limitinteger–How many roles to return (1 to 25).
min_hourly_usdinteger–Only roles whose advertised hourly ceiling reaches this many US dollars.
platformstring–Employer slug, e.g. 'tesla-optimus', 'waymo', 'micro1'. get_robot_training_market lists them.
querystring–Keywords matched against role titles, e.g. 'teleoperator', 'drone', 'test driver', 'humanoid'.
remote_onlyboolean–Only roles that can be done remotely (from home).
sortstring–'recent' for the newest roles first, 'pay' for the highest advertised pay first. Default: a mix across employers.

No output schema declared.

No examples provided.

Install

How do I install the RobotTraining.jobs MCP server?

RobotTraining.jobs is a hosted endpoint at https://robottraining.jobs/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · robottraining.jobs

# add to Claude Code
claude mcp add --transport http jobs-robottraining-robot-training-jobs 'https://robottraining.jobs/api/mcp'
Common questions

What is the RobotTraining.jobs MCP server?

RobotTraining.jobs is an MCP server listed in the public MCP registry as jobs.robottraining/robot-training-jobs. Search open robot training jobs (teleoperation, data collection, AV and drone tests) and their pay. This page covers its hosted endpoint (https://robottraining.jobs/api/mcp).

Is the RobotTraining.jobs MCP server safe to use?

RobotTraining.jobs scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the RobotTraining.jobs MCP server expose?

RobotTraining.jobs exposes 3 tools: search_robot_training_jobs, get_robot_training_pay, get_robot_training_market. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.

Does the RobotTraining.jobs MCP server require authentication?

No. We connected to RobotTraining.jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RobotTraining.jobs MCP server still maintained?

RobotTraining.jobs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.