Remote MCP · Endpoint

GigHQ.ai MCP server

No. GigHQ.ai answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

https://mcp.gighq.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.gighq/gighq
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
100 ms
Tools exposed
34 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Job-search tracker for AI agents: applications, stale follow-ups, skills gaps, H-1B lookup.
Listing
From the official MCP registry (active).
Recent checks of GigHQ.ai
CheckedResultHandshake
17 hours agoHandshake completed100 ms
11 days agoHandshake completed84 ms
12 days agoHandshake completed82 ms
12 days agoHandshake completed87 ms
14 days agoHandshake completed83 ms
15 days agoHandshake completed69 ms
16 days agoHandshake completed85 ms
17 days agoHandshake completed73 ms
18 days agoHandshake completed76 ms
20 days agoHandshake completed98 ms
22 days agoHandshake completed77 ms
25 days agoHandshake completed106 ms

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

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