Remote MCP · Endpoint

JOBFLOW MCP server

No. JOBFLOW answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agents.kulalabs.ch/api/mcp

The last check completed an MCP handshake.

Registry name
ch.kulalabs.agents/jobflow
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
913 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Existing trade and field-service flow for AI agents, request to paid job. Free intent.match first.
Listing
From the official MCP registry (active).
Recent checks of JOBFLOW
CheckedResultHandshake
1 hour agoHandshake completed913 ms
2 days agoHandshake completed2.17 s
5 days agoHandshake completed768 ms
7 days agoHandshake completed825 ms
9 days agoHandshake completed754 ms
11 days agoHandshake completed585 ms
13 days agoHandshake completed523 ms
15 days agoHandshake completed754 ms
17 days agoHandshake completed563 ms
19 days agoHandshake completed739 ms
20 days agoHandshake completed453 ms
22 days agoHandshake completed648 ms
23 days agoHandshake completed593 ms
25 days agoHandshake completed290 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 JOBFLOW and makes no claim about it beyond what these checks measured.