Remote MCP · Endpoint

HirePulse Agent Gateway MCP server

No. HirePulse Agent Gateway answered an MCP handshake 48 minutes ago.

UpLast checked 48 minutes ago

Server URL

https://gethirepulse.xyz/mcp

The last check completed an MCP handshake.

Registry name
io.github.edtool79-collab/hirepulse-gateway
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
231 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
27 tools for company, hiring and commerce data. 10 free calls per agent per day, then USDC on Base.
Listing
From the official MCP registry (active).
Recent checks of HirePulse Agent Gateway
CheckedResultHandshake
48 minutes agoHandshake completed231 ms
10 days agoHandshake completed299 ms
10 days agoHandshake completed273 ms
11 days agoHandshake completed327 ms
12 days agoHandshake completed170 ms
14 days agoHandshake completed182 ms
14 days agoHandshake completed214 ms
15 days agoHandshake completed214 ms
17 days agoHandshake completed328 ms
19 days agoHandshake completed218 ms
21 days agoHandshake completed227 ms
24 days agoHandshake completed158 ms
26 days agoHandshake completed231 ms
28 days agoHandshake completed265 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 HirePulse Agent Gateway and makes no claim about it beyond what these checks measured.