Jobs Data MCP (SteadyScrape)

Live job postings from employer career sites (Greenhouse, Lever, Ashby, Workday and 10 more ATS) plus keyword and remote-job search. Pay per job returned.

View on glama.ai

Hosted MCP Server

npx add-mcp 'https://mcp.apify.com/?tools=steady-scrape/ats-job-feed,steady-scrape/career-jobs-search,steady-scrape/remote-jobs-api'

Installs into Claude Code, Codex, Cursor and more

Documentation

Overview Discussions Admin

Server Details

Live job postings from 14+ ATS career sites (Greenhouse, Lever, Workday, Ashby and more) plus remote jobs, in one JSON format. Runs on Apify (Apify OAuth or API token).

Ownership verified

TDQS

A3.7/5.0

Scored 2026-11-02 23:35 across 7 tools

Disambiguation3/5

Naming Consistency4/5

Tool Count5/5

Completeness3/5

Available Tools

7 tools

abort-actor-run Abort Actor runA

DestructiveIdempotent

Inspect

Abort an Actor run that is currently starting or running. For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request.

USAGE:

Use when you need to stop a run that is taking too long or misconfigured.

USAGE EXAMPLES:

user_input: Abort run y2h7sK3Wc
user_input: Gracefully abort run y2h7sK3Wc

Name	Required	Description	Default
runId	Yes	The ID of the Actor run to abort.
gracefully	No	If true, the Actor run will abort gracefully with a 30-second timeout.

Output Schema

Name	Required	Description
tip	No	Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runId	Yes	Actor run ID
stats	No	Run statistics
status	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
actorId	Yes	Stable Apify Actor ID from the run record
summary	Yes	Past-tense summary of the run state
exitCode	No	Actor process exit code; populated for terminal states (especially FAILED)
nextStep	Yes	One primary follow-up action with identifiers interpolated
storages	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorName	No	"username/actor-name"
startedAt	No	ISO timestamp when the run started
finishedAt	No	ISO timestamp when the run finished (terminal states only)
statusMessage	No	Pass-through from Apify run.statusMessage
apifyConsoleUrl	No	Personalized Apify Console link to the run; present only for Console sessions

TDQS

A4.1/5.0

Behavior4/5

Conciseness4/5

Completeness4/5

Parameters3/5

Purpose5/5

Usage Guidelines4/5

get-actor-run Get Actor runA

Read-onlyIdempotent

Inspect

Get detailed information about a specific Actor run.

Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.

summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").
nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").
waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.

USAGE:

Use to check the status of a run started by any Actor-running tool.
Pass waitSecs > 0 to block until terminal (or until the cap elapses).

USAGE EXAMPLES:

user_input: Show details of run y2h7sK3Wc
user_input: Wait for run y2h7sK3Wc to finish

Name	Required	Description	Default
runId	Yes	The ID of the Actor run.
waitSecs	No	Maximum seconds to wait for the run to reach a terminal state (SUCCEEDED, FAILED, ABORTED, TIMED-OUT). 0 returns immediately with the current status. Cap: 45. Default: 30.

Output Schema

Name	Required	Description
tip	No	Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runId	Yes	Actor run ID
stats	No	Run statistics
status	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
actorId	Yes	Stable Apify Actor ID from the run record
summary	Yes	Past-tense summary of the run state
exitCode	No	Actor process exit code; populated for terminal states (especially FAILED)
nextStep	Yes	One primary follow-up action with identifiers interpolated
storages	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorName	No	"username/actor-name"
startedAt	No	ISO timestamp when the run started
finishedAt	No	ISO timestamp when the run finished (terminal states only)
statusMessage	No	Pass-through from Apify run.statusMessage
apifyConsoleUrl	No	Personalized Apify Console link to the run; present only for Console sessions

TDQS

A4.1/5.0

Behavior4/5

Conciseness4/5

Completeness5/5

Parameters4/5

Purpose4/5

Usage Guidelines4/5

get-dataset-items Get dataset itemsA

Read-onlyIdempotent

Inspect

Get items (rows) from a dataset — the output/results produced by an Actor run. Returns the rows themselves, not dataset metadata, counts, or a schema. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly. Default limit is 20. Use clean=true to skip empty items and hidden fields.

USAGE:

Use when you need to read data from a dataset (all items or only selected fields).

USAGE EXAMPLES:

user_input: Retrieve results from dataset abc123
user_input: Get only metadata.url and title from dataset username~my-dataset

Name	Required	Description
desc	No	If true, results are returned in reverse order (newest to oldest).
omit	No	Comma-separated list of fields to exclude from results.
clean	No	If true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true.
limit	No	Maximum number of items to return. Default is 20.
fields	No	Comma-separated list of fields to include in results. Fields in output are sorted as specified. Use dot notation for nested objects (e.g. "metadata.url"); the server auto-flattens parent prefixes.
offset	No	Number of items to skip at the start. Default is 0.
flatten	No	Comma-separated list of fields to flatten (e.g. flatten="metadata" turns {"metadata":{"url":"x"}} into {"metadata.url":"x"}). Normally derived automatically from dot-notation in `fields`; specify only as a diagnostic override.
datasetId	Yes	Dataset ID, name (resolved against your own datasets), or full name as username~name.

Output Schema

Name	Required	Description
items	Yes	Dataset items
limit	Yes	Limit used for pagination
offset	Yes	Offset used for pagination
summary	Yes	Summary of the result
nextStep	Yes	One follow-up action with tool name
datasetId	Yes	Dataset ID
itemCount	Yes	Number of items returned
totalItemCount	Yes	Total items in dataset
apifyConsoleUrl	No	Personalized Apify Console link to the dataset; present only for Console sessions

TDQS

A4.1/5.0

Behavior4/5

Conciseness4/5

Completeness4/5

Parameters3/5

Purpose5/5

Usage Guidelines4/5

get-key-value-store-record Get key-value store recordA

Read-onlyIdempotent

Inspect

Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Requires the exact key name. The response preserves the original Content-Encoding; most clients handle decompression automatically.

USAGE:

Use when you need to retrieve a specific record (JSON, text, or binary) from a store.

USAGE EXAMPLES:

user_input: Get record INPUT from store abc123
user_input: Get record data.json from store username~my-store

Name	Required	Description	Default
recordKey	Yes	Key of the record to retrieve.
keyValueStoreId	Yes	Key-value store ID, name (resolved against your own key-value stores), or full name as username~name.

Output Schema

Name	Required	Description
key	Yes	Record key
value	Yes	The stored value (JSON, text, or binary)
summary	Yes	Summary of the result
contentType	No	MIME type of the stored value
keyValueStoreId	Yes	Key-value store ID

TDQS

A4/5.0

Behavior4/5

Conciseness4/5

Completeness5/5

Parameters3/5

Purpose5/5

Usage Guidelines3/5

steady-scrape--ats-job-feed steady-scrape/ats-job-feed

Destructive

Inspect

This tool calls the Actor "steady-scrape/ats-job-feed" and retrieves its output results. Actor description: Career page jobs scraper: every open job from company career sites on Greenhouse, Lever, Ashby, Workday, Oracle HCM, BambooHR, Workable, SmartRecruiters and 6 more ATS, as one JSON feed with salary, location, remote and apply link. New/removed job alerts. $1.50 per 1,000 jobs.

Name	Required	Description	Default
keywords	No	Keep only jobs whose title contains at least one of these words or phrases (case-insensitive substring match, e.g. 'engineer', 'product manager'). Leave empty to keep all titles.
waitSecs	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
companies	Yes	REQUIRED Required. One entry per company career board. The ATS platform is auto-detected from the URL. [Description truncated] Example values: ["https://job-boards.greenhouse.io/stripe","https://jobs.lever.co/spotify","https://jobs.ashbyhq.com/ramp","https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite"\]
locations	No	Keep only jobs with at least one location matching any of these: city, region/state, country name or ISO 3166-1 alpha-2 country code (e.g. 'London', 'California', 'Canada', 'US'). Leave empty for all locations. Combine with 'Remote only' for remote jobs in a given country.
maxRetries	No	How many times to retry a request after HTTP 429, 5xx or a timeout, with exponential backoff. Example values: 4
remoteOnly	No	If true, keep only remote jobs (flagged remote by the ATS, workplace type REMOTE, or 'Remote' in the location).
departments	No	Keep only jobs whose department or team contains any of these (case-insensitive substring, e.g. 'engineering', 'sales', 'marketing'). Workday boards do not expose departments, so this filter removes all Workday jobs when set.
maxConcurrency	No	Maximum number of HTTP requests in flight at once across all boards. The default of 5 is polite and fast enough for most runs. Example values: 5
stateStoreName	No	Name of the key-value store that keeps delivered job IDs for 'Only new jobs'. Runs that share a name share history. Use a different name for each independent feed or alert. Example values: "ats-job-feed-state"	ats-job-feed-state
emitRemovedJobs	No	Only used with 'Only new jobs'. If true, jobs that disappeared from a board since the last run are output as free records with changeType='removed', firstSeenAt and removedDetectedAt. Requires a complete board listing (for Workday: no cap or keyword pre-filter).
excludeKeywords	No	Drop jobs whose title contains any of these words or phrases (case-insensitive substring match, e.g. 'intern', 'senior').
firstRunEmitsAll	No	Only used with 'Only new jobs'. When a board is seen for the first time: true (default) outputs all its current jobs once; false records them silently as a baseline so you only get jobs posted later. Example values: true
postedWithinDays	No	Keep only jobs posted in the last N days (e.g. 7). Jobs without a posted date are kept. Leave empty for any date.
maxJobsPerCompany	No	Maximum number of jobs returned per board, after filters. With 'Only new jobs' it caps new jobs per board per run (held-back jobs come in later runs). Leave empty for no cap. Use a small value (e.g. 10-100) for quick tests and to control cost ($0.0015 per job). On the Apify Free plan, the first 50 job results per account are free while the monthly free pool lasts; after that the normal price applies. Example values: 25
includeDescription	No	If true (default), each job includes the full description as HTML (descriptionHtml) and plain text (descriptionText). Set false for a smaller, faster dataset with metadata only. Example values: true
onlyNewSinceLastRun	No	If true, the Actor remembers which job IDs it already delivered per board (in the named key-value store below) and outputs only jobs not delivered before, marked changeType='new'. Use for scheduled job alerts and change feeds. If false (default), every matching job is returned on every run.

Output Schema

Name	Required	Description
tip	No	Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runId	Yes	Actor run ID
stats	No	Run statistics
status	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
actorId	Yes	Stable Apify Actor ID from the run record
summary	Yes	Past-tense summary of the run state
exitCode	No	Actor process exit code; populated for terminal states (especially FAILED)
nextStep	Yes	One primary follow-up action with identifiers interpolated
storages	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorName	No	"username/actor-name"
startedAt	No	ISO timestamp when the run started
finishedAt	No	ISO timestamp when the run finished (terminal states only)
statusMessage	No	Pass-through from Apify run.statusMessage
apifyConsoleUrl	No	Personalized Apify Console link to the run; present only for Console sessions

steady-scrape--remote-jobs-api steady-scrape/remote-jobs-apiB

Destructive

Inspect

This tool calls the Actor "steady-scrape/remote-jobs-api" and retrieves its output results. Actor description: Remote jobs scraper and API: remote-only jobs straight from employer career sites (Greenhouse, Lever, Ashby, Workday, Workable and more), not job-board reposts. Fully remote vs remote-optional vs hybrid, eligible countries, regions and time zones, only-new mode. $1.50 per 1,000 jobs.

Name	Required	Description	Default
dedupe	No	Merge the same role posted by the same company in several locations into one result (all locations and job IDs are kept). Example values: true
regions	No	Only jobs open to workers in these regions (e.g. 'EMEA', 'Europe', 'LATAM' postings, or any country inside the region).
keywords	No	Job title/department keywords or phrases (any match). Leave empty for all remote jobs. Matched as whole words, e.g. 'software engineer', 'devops', 'customer success'. Example values: ["software engineer","developer"]
stateKey	No	Optional name for the 'only new' memory. Defaults to a hash of the filters.
waitSecs	No	Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
companies	No	Only these companies (name or board slug, partial match).
platforms	No	Only these ATS platforms. Leave empty for all.
seniority	No	Only these seniority levels (derived from the title).
enrichJobs	No	Adds an `enrichment` object to every job: salary range (min/max/currency/period + annualized, from the ATS's structured pay fields or parsed from the description), key skills and tools named in the posting, seniority level, minimum years of experience, work arrangement (from this Actor's remote/hybrid classification), employment type, visa sponsorship (when stated) and a short summary. Reads each returned job live from the employer's board (like full descriptions), so runs are slower. [Description truncated]
maxResults	No	Maximum jobs to return, newest first. Example values: 50
salaryOnly	No	Only jobs where the posting states a salary.
departments	No	Only jobs whose department contains any of these (as reported by the employer).
remoteTypes	No	FULLY_REMOTE = remote job; REMOTE_OPTIONAL = remote possible but the posting also lists offices or says remote-friendly/flexible; HYBRID = some days in an office. Example values: ["FULLY_REMOTE","REMOTE_OPTIONAL"]
jobCategories	No	Only these categories (derived from title and department).
minConfidence	No	high = the ATS remote flag and the location text agree; medium = one clear signal (ATS remote flag, or 'Remote' in the location or title); low = conflicting signals (e.g. ATS says on-site but the title says remote). Example values: "medium"	medium
maxConcurrency	No	Parallel career-site requests when fetching descriptions. Example values: 8
stateStoreName	No	Named key-value store that keeps the 'only new' memory in your account. Example values: "remote-jobs-api-state"	remote-jobs-api-state
workerTimezone	No	Only jobs whose eligible countries/regions/stated hours overlap your time zone. Offset like 'UTC-6', '+5:30', or an IANA zone like 'America/Costa_Rica'.
employmentTypes	No	Only these employment types (when the board states one).
excludeKeywords	No	Skip jobs whose title contains any of these.
workerCountries	No	Only jobs open to workers in these countries. ISO codes or names (US, GB, Germany, 'EU' for all EU members). Worldwide and matching-region jobs are included.
excludeCompanies	No	Skip these companies (e.g. staffing agencies).
firstRunEmitsAll	No	With 'Only new', the first run returns all current matches. Turn off to just record a baseline (no results, no charge) so later runs only alert on new jobs. Example values: true
postedWithinDays	No	Only jobs posted (or first seen by us) in the last N days. Example values: 14
includeDescriptions	No	Fetch each job's live description from the career site. Also refines the remote classification with description cues (hybrid schedules, 'must be located in…', working hours) and drops jobs that have closed.
onlyNewSinceLastRun	No	For scheduled runs: return only jobs not returned by an earlier run with the same filters (or the same state key).
maxTimezoneDiffHours	No	How far (in hours) the job's time-zone range may be from yours. Example values: 3
includeUnspecifiedEligibility	No	Many postings just say 'Remote' without saying where. When a country, region or time-zone filter is set, include those too (check the description).

Output Schema

Name	Required	Description
tip	No	Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runId	Yes	Actor run ID
stats	No	Run statistics
status	Yes	Run status: READY \| RUNNING \| TIMING-OUT \| TIMED-OUT \| ABORTING \| ABORTED \| SUCCEEDED \| FAILED
actorId	Yes	Stable Apify Actor ID from the run record
summary	Yes	Past-tense summary of the run state
exitCode	No	Actor process exit code; populated for terminal states (especially FAILED)
nextStep	Yes	One primary follow-up action with identifiers interpolated
storages	Yes	Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorName	No	"username/actor-name"
startedAt	No	ISO timestamp when the run started
finishedAt	No	ISO timestamp when the run finished (terminal states only)
statusMessage	No	Pass-through from Apify run.statusMessage
apifyConsoleUrl	No	Personalized Apify Console link to the run; present only for Console sessions

TDQS

B3.2/5.0

Behavior3/5

Conciseness4/5

Completeness3/5

Parameters3/5

Purpose4/5

Usage Guidelines2/5

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool update Nov 3, 2026
- Changed steady-scrape--ats-job-feed 3 fields changed
  - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / department / type
```
Previous value: -[
-  "null",
-  "string"
-]New value: +[
+  "string",
+  "null"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / descriptionHtml / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / descriptionText / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
1 tool update Nov 2, 2026
- Changed steady-scrape--remote-jobs-api 10 fields changed
  - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / atsWorkplaceType / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / department / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / eligibilitySource / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / employmentType / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locationText / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locations / items / properties / country / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locations / items / properties / countryCode / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / timezoneSource / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / utcOffsetMax / type
```
Previous value: -[
-  "number",
-  "null"
-]New value: +[
+  "null",
+  "number"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / utcOffsetMin / type
```
Previous value: -[
-  "number",
-  "null"
-]New value: +[
+  "null",
+  "number"
+]
```
1 tool update Nov 2, 2026
- Changed steady-scrape--ats-job-feed 4 fields changed
  - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / department / type
```
Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / descriptionHtml / type
```
Previous value: -"null"New value: +[
+  "string",
+  "null"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / descriptionText / type
```
Previous value: -"null"New value: +[
+  "string",
+  "null"
+]
```
    - added Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / postedOnText
```
Added value: +{
+  "type": "string"
+}
```
2 tool updates Nov 2, 2026
- Changed steady-scrape--career-jobs-search 5 fields changed
  - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / department / type
```
Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locationText / type
```
Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locations / items / properties / city / type
```
Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locations / items / properties / country / type
```
Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locations / items / properties / countryCode / type
```
Previous value: -"string"New value: +[
+  "null",
+  "string"
+]
```
- Changed steady-scrape--remote-jobs-api 2 fields changed
  - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locationText / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
    - changed Output schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / locations / items / properties / region / type
```
Previous value: -"null"New value: +[
+  "null",
+  "string"
+]
```

Related MCP Servers

A license Not graded quality B maintenance Enables searching live job postings pulled directly from 10 applicant-tracking-system APIs — including Greenhouse, Lever, Ashby, Workday, Personio, Recruitee, Teamtailor, Workable, SmartRecruiters and Breezy HR — using just a company website, domain or ATS handle, with filters for keywords, location, remote work and posting date. Also supports multi-company lookups, ATS detection, and stateless "only new since last call" monitoring for scheduled agents. Updated 16 days ago (2026-10-17 19:46 UTC) MIT
simplyapply-jobs-mcp
tsushanth A license A quality C maintenance Enables real-time job search across thousands of companies' open roles from Greenhouse, Lever, Ashby, and SmartRecruiters, with full-text filtering and company-specific queries, no API key required. Updated 2 months ago (2026-08-26 22:08 UTC) 2 MIT
company-jobs-feedofficial
fairquery A license A quality A maintenance Live open jobs from companies' own Greenhouse, Lever and Ashby boards via their official public APIs, with publish-verified dates, age, long-open and repost signals, filters and change tracking. Updated 15 days ago (2026-10-18 16:58 UTC) 5 MIT
ats-jobs-mcp
benkrasin A license Not graded quality F maintenance Enables users to look up a company's open job postings from public Greenhouse, Lever, and Ashby boards, returning them in one normalized shape with filtering by keyword, location, remote status, and posting date. It also identifies which of those three ATSs hosts a given company's board and how many roles are open there. Updated 10 days ago (2026-10-24 05:35 UTC) 24 npm MIT

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.run Ad

Glama MCP Gateway

Add one secure layer between your agents and this server.

Jobs Data MCP (SteadyScrape)

Hosted MCP Server

Documentation

Server Details

TDQS

Available Tools

Output Schema

TDQS

Output Schema

TDQS

Output Schema

TDQS

Output Schema

TDQS

Output Schema

Output Schema

TDQS

Tool Schema Changelog

Related MCP Servers

simplyapply-jobs-mcp

company-jobs-feedofficial

ats-jobs-mcp

Glama MCP Gateway

Resources