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.

Haystack Jobs

REMOTE · HAYSTACKAPP.IO

Search live jobs from employers' own careers sites in the US, UK, Canada, Australia and Europe.

Available components

71 Trust /100

Last scanned (5 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

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 Security80
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 667 tokens (~166/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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% 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
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 70

    First indexed and scored.

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://haystackapp.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=haystackapp.io CN=WE1,O=Google Trust Services,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA256 2fa604db634ba491133b101c927d9f08
SANs: haystackapp.io
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 haystackapp.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
haystackapp.io. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://haystackapp.io/mcp Verified 200
http (plaintext) http://haystackapp.io/mcp HTTPS enforced 301 https://haystackapp.io/mcp
MCP tools · 4 exposed · ~512 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
application_system_facts ~66

Facts about an application system (ATS) from applications Haystack's AI agent sent: how many fields its forms have, the questions they ask most, and how fast employers on it reply. Without a system, the overall figures.

NameTypeReqDescription
systemstring–The application system.

No output schema declared.

No examples provided.

employer_facts ~95

What Haystack knows about applying to an employer: live roles, the share of applications that got a reply, the median time to the first reply, how many fields its form has and the questions it asks. Pass no company to get the employers most likely to reply to an application.

NameTypeReqDescription
companystring–Employer name, e.g. 'Monzo', 'Stripe'. Leave out for the employers most likely to reply.

No output schema declared.

No examples provided.

get_job ~89

One job's details by its Haystack id: title, employer, location, pay, work mode, skills, what the advert says (no experience, no degree, visa sponsorship), the description, and facts about applying to that employer from Haystack's data (reply rate, time to reply, form questions) when known.

NameTypeReqDescription
job_idstringyesThe job's id from search_jobs.

No output schema declared.

No examples provided.

search_jobs ~262

Search live jobs on Haystack, newest first. Filter by job title words, country, city, remote, and by what the advert says: no experience needed, no degree needed, visa sponsorship offered. Returns up to 20 jobs, each with its link, and an Auto Apply link when Haystack's AI agent can fill in and submit the employer's form.

NameTypeReqDescription
auto_apply_onlyboolean–Only roles Haystack's AI agent can apply to.
citystring–City, e.g. 'London', 'New York', 'Toronto'.
countrystring–Country name or code, e.g. 'United States', 'UK', 'Canada', 'Germany'.
limitinteger––
no_degreeboolean–Only roles whose advert says no degree is needed (or asks for a high school diploma or equivalent).
no_experienceboolean–Only roles whose advert says no experience is needed or training is provided.
querystring–Words in the job title, e.g. 'product manager', 'nurse', 'data analyst'.
remoteboolean–Only remote roles.
visa_sponsorshipboolean–Only roles whose advert says the employer offers visa sponsorship.

No output schema declared.

No examples provided.

Install

How do I install the Haystack Jobs MCP server?

Haystack Jobs is a hosted endpoint at https://haystackapp.io/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 · haystackapp.io

# add to Claude Code
claude mcp add --transport http io-haystackapp-jobs 'https://haystackapp.io/mcp'
Common questions

What is the Haystack Jobs MCP server?

Haystack Jobs is an MCP server listed in the public MCP registry as io.haystackapp/jobs. Search live jobs from employers' own careers sites in the US, UK, Canada, Australia and Europe. This page covers its hosted endpoint (https://haystackapp.io/mcp).

Is the Haystack Jobs MCP server safe to use?

Haystack Jobs scores 71 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 Haystack Jobs MCP server expose?

Haystack Jobs exposes 4 tools: search_jobs, get_job, employer_facts, application_system_facts. Their descriptions and schemas cost roughly 512 tokens of context every time the server is loaded.

Does the Haystack Jobs MCP server require authentication?

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

Is the Haystack Jobs MCP server still maintained?

Haystack Jobs 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.