Remote MCP · Endpoint

AITraining.jobs MCP server

No. AITraining.jobs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aitraining.jobs/api/mcp

The last check completed an MCP handshake.

Registry name
jobs.aitraining/ai-training-jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
94 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search open AI training jobs from 17 platforms and compare advertised hourly pay by kind of work.
Listing
From the official MCP registry (active).
Recent checks of AITraining.jobs
CheckedResultHandshake
1 hour agoHandshake completed94 ms
1 day agoHandshake completed183 ms
2 days agoHandshake completed105 ms
2 days agoHandshake completed173 ms
4 days agoHandshake completed445 ms
6 days agoHandshake completed213 ms
9 days agoHandshake completed93 ms
11 days agoHandshake completed84 ms
14 days agoHandshake completed84 ms
16 days agoHandshake completed92 ms
18 days agoHandshake completed86 ms
20 days agoHandshake completed204 ms
22 days agoHandshake completed81 ms
23 days agoHandshake completed115 ms

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

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 AITraining.jobs and makes no claim about it beyond what these checks measured.