Remote MCP · Endpoint

Hire or Automate MCP server

No. Hire or Automate answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://hire.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/hire
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
328 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Split a job into work AI can do now, work AI drafts for a person to approve, and work for a person.
Listing
From the official MCP registry (active).
Recent checks of Hire or Automate
CheckedResultHandshake
44 minutes agoHandshake completed328 ms
3 days agoHandshake completed289 ms
13 days agoHandshake completed154 ms
13 days agoHandshake completed319 ms
15 days agoHandshake completed159 ms
15 days agoHandshake completed158 ms
17 days agoHandshake completed319 ms
18 days agoHandshake completed222 ms
18 days agoHandshake completed171 ms
20 days agoHandshake completed164 ms
22 days agoHandshake completed3.95 s
25 days agoHandshake completed171 ms
27 days agoHandshake completed635 ms
29 days agoHandshake completed162 ms

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

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