Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

HuntBoard

REMOTE · HUNTBOARD.AI

Search real, recent job postings from company career pages and ATS boards, scored for fit.

Available components

0 this week 85 Trust /100

Last scanned (11 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 645 tokens (~161/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Oct 26 +1
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 77. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 67. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://huntboard.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=huntboard.ai CN=WE1,O=Google Trust Services,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA256 14fbda345fcf8de80ea2350519921389
SANs: huntboard.ai, www.huntboard.ai, *.www.huntboard.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of huntboard.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
huntboard.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://huntboard.ai/mcp Verified 200
http (plaintext) http://huntboard.ai/mcp HTTPS enforced 301 https://huntboard.ai/mcp
MCP tools · 4 exposed · ~476 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_job ~72

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.

NameTypeReqDescription
urlstringyesThe job link as returned by search_jobs.

No output schema declared.

No examples provided.

list_coverage ~44

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_jobs ~212

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 scored 7-10 with title, company, location, link, source and a one-line reason.

NameTypeReqDescription
exclude_locationsarray–Location fragments to drop.
exclude_titlesarray–Title fragments to drop, e.g. ["Manager", "QA"].
locationsarray–Cities, regions or countries, e.g. ["Tel Aviv", "Israel"]. Optional only when remote_ok is true.
max_resultsinteger–How many jobs to return, 1-50.
remote_okboolean–Also include remote roles open to the given locations (or global remote roles).
titlesarrayyesTarget job titles, e.g. ["Backend Engineer", "Platform Engineer"]. Parentheticals are stripped and head phrases matched.

No output schema declared.

No examples provided.

subscribe_daily_hunts ~148

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 unsubscribe in every email. Only call this when the person explicitly asked for daily emails and gave their own address.

NameTypeReqDescription
emailstringyesThe person's own email address.
exclude_locationsarray––
exclude_titlesarray––
locationsarray–Cities, regions or countries. Optional only when remote_ok is true.
remote_okboolean–Also include remote roles.
titlesarrayyesTarget job titles.

No output schema declared.

No examples provided.

Install

How do I install the HuntBoard MCP server?

HuntBoard is a hosted endpoint at https://huntboard.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · huntboard.ai

# add to Claude Code
claude mcp add --transport http ai-huntboard-huntboard 'https://huntboard.ai/mcp'
Common questions

What is the HuntBoard MCP server?

HuntBoard is an MCP server listed in the public MCP registry as ai.huntboard/huntboard. Search real, recent job postings from company career pages and ATS boards, scored for fit. This page covers its hosted endpoint (https://huntboard.ai/mcp).

Is the HuntBoard MCP server safe to use?

HuntBoard scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the HuntBoard MCP server expose?

HuntBoard exposes 4 tools: search_jobs, get_job, list_coverage, subscribe_daily_hunts. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.

Does the HuntBoard MCP server require authentication?

No. We connected to HuntBoard without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the HuntBoard MCP server still maintained?

HuntBoard is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.