Remote MCP · Endpoint

Level MCP server

No. Level answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://jobsbylevel.com/mcp

The last check completed an MCP handshake.

Registry name
com.jobsbylevel/level-jobs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
336 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free, read-only access to job listings rated by AI level, from Little AI to Builds AI.
Website
https://jobsbylevel.com/developers
Listing
From the official MCP registry (active).
Recent checks of Level
CheckedResultHandshake
56 minutes agoHandshake completed336 ms
1 day agoHandshake completed130 ms
2 days agoHandshake completed656 ms
5 days agoHandshake completed214 ms
8 days agoHandshake completed315 ms
10 days agoHandshake completed429 ms
12 days agoHandshake completed176 ms
14 days agoHandshake completed310 ms
16 days agoHandshake completed328 ms
18 days agoHandshake completed345 ms
20 days agoHandshake completed122 ms
22 days agoHandshake completed129 ms
23 days agoHandshake completed301 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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