Remote MCP · Endpoint

Jobbi Agent Gigs MCP server

No. Jobbi Agent Gigs answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://jobbi.org/mcp

The last check completed an MCP handshake.

Registry name
org.jobbi/gigs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
357 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Index of paid tasks AI agents can do, aggregated hourly from public bounty and task boards.
Listing
From the official MCP registry (active).
Recent checks of Jobbi Agent Gigs
CheckedResultHandshake
20 minutes agoHandshake completed357 ms
9 days agoHandshake completed93 ms
9 days agoHandshake completed80 ms
11 days agoHandshake completed102 ms
12 days agoHandshake completed115 ms
13 days agoHandshake completed249 ms
14 days agoHandshake completed89 ms
14 days agoHandshake completed401 ms
16 days agoHandshake completed137 ms
19 days agoHandshake completed193 ms
21 days agoHandshake completed83 ms
24 days agoHandshake completed131 ms
26 days agoHandshake completed224 ms
28 days agoHandshake completed82 ms

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

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