Remote MCP · Endpoint

Hire or Automate MCP server

No. Hire or Automate answered an MCP handshake 4 hours ago.

UpLast checked 4 hours 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
3.95 s
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 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
4 hours agoHandshake completed3.95 s
2 days agoHandshake completed171 ms
5 days agoHandshake completed635 ms
7 days agoHandshake completed162 ms
9 days agoHandshake completed140 ms
11 days agoHandshake completed312 ms
13 days agoHandshake completed311 ms
15 days agoHandshake completed361 ms
17 days agoHandshake completed58 ms
18 days agoHandshake completed1.10 s
20 days agoHandshake completed298 ms
21 days agoHandshake completed659 ms
23 days agoHandshake completed276 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.

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.