Remote MCP · Endpoint

HuntBoard MCP server

No. HuntBoard answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://huntboard.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.huntboard/huntboard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
132 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search real, recent job postings from company career pages and ATS boards, scored for fit.
Listing
From the official MCP registry (active).
Recent checks of HuntBoard
CheckedResultHandshake
8 hours agoHandshake completed132 ms
2 days agoHandshake completed88 ms
4 days agoHandshake completed50 ms
5 days agoHandshake completed49 ms
7 days agoHandshake completed66 ms
8 days agoHandshake completed126 ms
9 days agoHandshake completed119 ms
12 days agoHandshake completed94 ms
13 days agoHandshake completed61 ms
15 days agoHandshake completed50 ms
16 days agoHandshake completed53 ms
17 days agoHandshake completed54 ms
18 days agoHandshake completed47 ms
19 days agoHandshake completed36 ms
20 days agoHandshake completed58 ms
21 days agoHandshake completed31 ms
23 days agoHandshake completed72 ms

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

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