Skip to content
HuntBoard logo

HuntBoard MCP server

Which servers in the official MCP registry are HuntBoard's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to HuntBoard

Whose server it is
  • Registry nameai.huntboard/huntboardverified in the MCP registry

The registry name sits under huntboard.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13
  • Stateanswerschecked 2026-10-13
  • Tools4
  • Server calls itselfhuntboard
  • Server version1.1.0
  • Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 110 ms.

Tools it offers4 tools · read 2026-10-13
  • search_jobs

    Find recent job postings that match target job titles in given locations (or remote). Runs HuntBoard's own hunt: SQL narrowing over its index of company career pages and ATS boards, then an AI fit score. Returns up to max_results jobs…

  • get_job

    Full details of one posting HuntBoard has indexed: title, company, location, workplace type, employment type, posted date, source, apply link, whether it is still open, and a description excerpt. Pass the link returned by search_jobs.

  • list_coverage

    The countries, cities, remote-in-country pages and job roles HuntBoard keeps browse pages for, each with its public page URL. Useful to pick locations and titles before searching.

  • subscribe_daily_hunts

    Ask HuntBoard to email the person new job matches every morning for the given titles and locations. Double opt-in: HuntBoard sends a confirmation link to the email address and nothing starts until the person clicks it. Free, one-click…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "huntboard": {
      "type": "http",
      "url": "https://huntboard.ai/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.