Remote MCP · Endpoint

Physical AI Jobs MCP server

No. Physical AI Jobs answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://www.physicalai.jobs/mcp

The last check completed an MCP handshake.

Registry name
jobs.physicalai/physical-ai-jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
539 ms
Tools exposed
4 tools
Uptime, last 30 days
78.6% from 14 checks
Described by its publisher as
Find robotics, humanoid and embodied AI jobs from PhysicalAI.jobs.
Listing
From the official MCP registry (active).
Recent checks of Physical AI Jobs
CheckedResultHandshake
35 minutes agoHandshake completed539 ms
9 days agoHandshake completed491 ms
10 days agoHandshake completed509 ms
11 days agoHandshake completed485 ms
12 days agoHandshake completed472 ms
14 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed517 ms
19 days agoHandshake completed505 ms
21 days agoHandshake completed464 ms
24 days agoHandshake completed552 ms
26 days agoHandshake completed545 ms
28 days agoHandshake completed506 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 31.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Physical AI Jobs and makes no claim about it beyond what these checks measured.