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.

Physical AI Jobs

REMOTE · WWW.PHYSICALAI.JOBS

Find robotics, humanoid and embodied AI jobs from PhysicalAI.jobs.

0 this week 85 Trust /100

Last scanned (18 hours ago)

Scores higher than 90% of remote servers

Reachable. Last reached 7 Nov 2026.

Category Project Management

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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 704 tokens (~176/item across 4 items; 4 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 77% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Nov 26 +62
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 1 Nov 26 −62
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 2 Oct 26 0
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 2 Sept 26 0

    First indexed and scored.

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 7 Nov 2026 · Probed https://www.physicalai.jobs/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=physicalai.jobs CN=YE2,O=Let's Encrypt,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA384 51cba8a4e0e8794e76224b0be72a9fc61f0
SANs: *.physicalai.jobs, physicalai.jobs
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.physicalai.jobs. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
jobs. DS published 47990 8 Verified
physicalai.jobs. No DS 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.physicalai.jobs/mcp Verified 200
http (plaintext) http://www.physicalai.jobs/mcp HTTPS enforced 301 https://www.physicalai.jobs/mcp
MCP tools · 4 exposed · ~667 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_job ~66

Retrieve additional sanitized public details for one PhysicalAI.jobs listing. Use this after search_jobs or latest_jobs when the user wants more information. The result links back to PhysicalAI.jobs and never exposes a hidden employer ATS URL.

NameTypeReqDescription
id–yesStable public job ID returned by PhysicalAI.jobs.
NameTypeReqDescription
canonical_urlstringyes–
categoryobject|null––
companyobject|null––
descriptionstring|null––
employment_typestring|null––
idintegeryes–
locationobject|null––
location_typestring|null––
open_urlstringyes–
published_atstring|null––
remoteboolean––
salaryobject|null––
slugstring|null––
summarystring|null––
tagsarray––
titlestring|nullyes–

No examples provided.

latest_jobs ~235

Find the newest current Physical AI, robotics, humanoid, embodied AI, autonomy, manipulation, perception and controls jobs on PhysicalAI.jobs. Use this for recent-job or jobs-since-a-date questions.

NameTypeReqDescription
categorystring–Public PhysicalAI.jobs category slug or name.
companystring–PhysicalAI.jobs company slug or company name.
countrystring–Country name, country slug, or two-letter country code.
currencystring–V1 salary thresholds use normalized annual USD compensation.
cursorstring–Opaque next_cursor returned by a previous call with identical filters.
employment_typestring––
limitinteger––
locationstring–Location text such as California, Taipei, or San Carlos.
min_salaryinteger–Minimum comparable annual salary in USD.
remoteboolean–True for remote-only results; false for onsite or hybrid results.
sincestring–Only jobs published at or after this ISO 8601 date-time.
tagsarray–Public PhysicalAI.jobs specialty/tag slugs or names.
NameTypeReqDescription
countintegeryes–
jobsarrayyes–
next_cursorstring|null––

No examples provided.

search_companies ~86

Search public PhysicalAI.jobs company profiles and optionally restrict results to companies that currently have public live jobs. Use this for questions about robotics, humanoid or embodied AI companies and who is hiring.

NameTypeReqDescription
cursorstring–Pagination token returned by a previous call with identical filters.
hiring_onlyboolean––
limitinteger––
querystring––
NameTypeReqDescription
companiesarrayyes–
countintegeryes–
next_cursorstring|null––

No examples provided.

search_jobs ~280

Search current robotics, humanoid, embodied AI and Physical AI roles from PhysicalAI.jobs by keyword, specialty, company, location, remote status and compensation. Use this when a user wants to discover or shortlist relevant jobs.

NameTypeReqDescription
categorystring–Public PhysicalAI.jobs category slug or name.
companystring–PhysicalAI.jobs company slug or company name.
countrystring–Country name, country slug, or two-letter country code.
currencystring–V1 salary thresholds use normalized annual USD compensation.
cursorstring–Opaque next_cursor returned by a previous call with identical filters.
employment_typestring––
limitinteger––
locationstring–Location text such as California, Taipei, or San Carlos.
min_salaryinteger–Minimum comparable annual salary in USD.
querystring–Keywords or specialty, for example robotics controls, humanoid, perception, or VLA.
remoteboolean–True for remote-only results; false for onsite or hybrid results.
sincestring–Only jobs published at or after this ISO 8601 date-time.
sortstring–Use salary_desc only when comparing jobs with usable compensation data.
tagsarray–Public PhysicalAI.jobs specialty/tag slugs or names.
NameTypeReqDescription
countintegeryes–
jobsarrayyes–
next_cursorstring|null––

No examples provided.

Install

How do I install the Physical AI Jobs MCP server?

Physical AI Jobs is a hosted endpoint at https://www.physicalai.jobs/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 · www.physicalai.jobs

# add to Claude Code
claude mcp add --transport http jobs-physicalai-physical-ai-jobs 'https://www.physicalai.jobs/mcp'
Common questions

What is the Physical AI Jobs MCP server?

Physical AI Jobs is an MCP server listed in the public MCP registry as jobs.physicalai/physical-ai-jobs. Find robotics, humanoid and embodied AI jobs from PhysicalAI.jobs. This page covers its hosted endpoint (https://www.physicalai.jobs/mcp).

Is the Physical AI Jobs MCP server safe to use?

Physical AI Jobs scores 85 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 Physical AI Jobs MCP server expose?

Physical AI Jobs exposes 4 tools: search_jobs, get_job, latest_jobs, search_companies. Their descriptions and schemas cost roughly 667 tokens of context every time the server is loaded.

Does the Physical AI Jobs MCP server require authentication?

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

Is the Physical AI Jobs MCP server still maintained?

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

What did VerifyMCP test on the Physical AI Jobs MCP server?

VerifyMCP ran 13 checks on Physical AI Jobs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.