ZBS Index What actually exists in applied AI, with the source next to it

mcp server

jobstack-mcp

Unified jobs search over official feeds + ATS boards (USAJOBS, Adzuna, Muse, Greenhouse, Lever...)

Description as published by the maintainer. Source

  • version 1.0.0
  • active
  • retrieval

active — Registry entry last updated 2026-08-01. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.

What this server can do

2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

get_job(id, source)
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. Required: source, id.
search_jobs(limit, offset, remote, sources, keywords, location)
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.

Last successful function declaration observed on . Source: https://jobstack-mcp.vercel.app/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://jobstack-mcp.vercel.app/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
Latest published version 1.0.0 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-08-01 When the registry record was last updated by its maintainer. point in time Model Context Protocol
First listed in the MCP Registry 2026-08-01 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
mcp tools declared 2 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe jobstack-mcp.vercel.app
mcp endpoint status ok The server listed 2 functions when asked. as of probe jobstack-mcp.vercel.app

Where to get it

Also from isaiahdupree

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Tools declared by the MCP server at https://jobstack-mcp.vercel.app/mcp — jobstack-mcp.vercel.app, observed , trust tier 1.
  2. Official MCP Registry — Model Context Protocol, observed , trust tier 1.