Remote MCP · Endpoint

Offpeak MCP server

No. Offpeak answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://offpeak.fyi/mcp

The last check completed an MCP handshake.

Registry name
io.github.vicentesurraco/offpeak
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
557 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search US jobs by driving commute, pay, and seniority. Save jobs, filters, and searches.
Website
https://offpeak.fyi/
Listing
From the official MCP registry (active).
Recent checks of Offpeak
CheckedResultHandshake
1 hour agoHandshake completed557 ms
1 day agoHandshake completed881 ms
2 days agoHandshake completed388 ms
2 days agoHandshake completed409 ms
4 days agoHandshake completed277 ms
7 days agoHandshake completed204 ms
9 days agoHandshake completed410 ms
12 days agoHandshake completed655 ms
14 days agoHandshake completed1.46 s
16 days agoHandshake completed1.28 s
18 days agoHandshake completed3.20 s
20 days agoHandshake completed1.07 s
22 days agoHandshake completed532 ms
24 days agoHandshake completed265 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.

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