jobstack-mcp
Unified jobs search over official feeds + ATS boards (USAJOBS, Adzuna, Muse, Greenhouse, Lever...)
Should I use this
Quality & Safety
Findings (2)
- HIGHTool poisoning patterns detected
- MEDIUMTool description contains suspicious base64-like encoded stringin search_jobs
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"jobstack-mcp": {
"url": "https://jobstack-mcp.vercel.app/mcp"
}
}
}Remote endpoints
https://jobstack-mcp.vercel.app/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢search_jobs(keywords, location, remote, sources, limit, ...)
Search job postings across every configured source and merge the results into one flat Job shape. Fans out in parallel to USAJOBS, Adzuna, Jooble, The Muse, Reed, and the ats engine (Greenhouse/Lever/Ashby/Workable/SmartRecruiters), then merges + sorts by postedDate (newest first) and paginates the combined set. Each Job has id, source, title, company, location, remote, url, description, postedDate, salaryMin, salaryMax, salaryCurrency, department, and employmentType. The response envelope carries meta, the echoed query, sources_requested, an optional sources_errored map, total, count, limit, offset, and results. Use sources= to restrict to specific engines.
Input Schema
{
"type": "object",
"properties": {
"keywords": {
"description": "Free-text search terms (job title, skill, company, etc.). Optional — omit to browse the latest postings.",
"type": "string"
},
"location": {
"description": "Free-text location filter (e.g. \"Washington, DC\" or \"London\"). Applied upstream where the source supports it.",
"type": "string"
},
"remote": {
"description": "Filter to remote roles when true. Only sources that expose an explicit remote signal apply it; others ignore it.",
"type": "boolean"
},
"sources": {
"description": "Comma-separated engine keys to restrict the fan-out to. Any of: usajobs, adzuna, jooble, themuse, reed, ats. Omit for all six.",
"type": "string"
},
"limit": {
"description": "Max results in the merged page, clamped 1-100. Default 20.",
"type": "integer",
"minimum": 1,
"maximum": 100
},
"offset": {
"description": "Zero-based offset into the merged result set for pagination. Default 0.",
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
}
},
"$schema": "http://json-schema.org/draft-07/schema#"
}🟢get_job(source, id)
Fetch one job posting by its source engine and native id, returned as { meta, job } with the same flat Job shape search_jobs yields. The id is the native upstream id as returned by that source in search results (NOT prefixed with the source name). Exception: for source="ats" the id is a composite "board:company:nativeId" string (e.g. "greenhouse:airbnb:7995153") so the lookup can round-trip to the right ATS board. Not every source supports single-job lookup — a search-only source returns a not_supported / not_found error.
Input Schema
{
"type": "object",
"properties": {
"source": {
"type": "string",
"enum": [
"usajobs",
"adzuna",
"jooble",
"themuse",
"reed",
"ats"
],
"description": "The engine that produced the job (matches the Job.source field from search_jobs)."
},
"id": {
"type": "string",
"description": "Native upstream job id as returned by that source. For source=\"ats\", the composite \"board:company:nativeId\" string."
}
},
"required": [
"source",
"id"
],
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence