ATS Job Pulse: Company Jobs & Hiring Signals

io.github.edtool79-collabPublished by GitHub account edtool79-collabv1.2.0Updated Oct 27, 2026

Open jobs and hiring changes for any company, from its domain. Runs on Apify.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Apify-hosted MCP tool that turns a company domain into its open jobs and hiring-change signals from the company's own ATS job board.

What you can do
  • Look up a company's open jobs by domain or board slug, with automatic detection of Greenhouse, Lever, Ashby, Workable, Recruitee and SmartRecruiters boards
  • Get a per-company hiring summary: total and remote jobs, salary coverage, department, location and technology breakdowns
  • Compare runs to flag jobs as new, existing or closed, and return only changes when asked
  • Filter jobs by title keywords, departments, locations, technologies or remote-only, and cap or shrink output for small context windows
  • Read per-job details such as title, department, location, remote flag, posted date, published salary range, detected technologies and apply URL
When to use it
Useful for recruiting, sales or market research questions about who is hiring, for what roles, and what changed since the last check across one or many companies. It fits agents that need compact, structured hiring data rather than browsing career pages.
Requirements
A remote MCP endpoint at mcp.apify.com with this Apify Actor enabled; no local install. Authentication is required: an Apify API token sent as a Bearer token in the Authorization header, or OAuth sign-in on first connection. A free Apify account is enough to start, but runs are billed per company.
Before you install
Usage is paid: $0.05 per successfully processed company, while companies not found are free, so costs grow with the number of domains queried. The Apify API token is a credential and should be kept private. Results are limited to six ATS platforms; Workday, iCIMS, Taleo and in-house career sites are reported as not found. A bare slug can match a different company with the same name, so prefixed slugs are safer.

Installation

In SourceWeft

  1. Open ATS Job Pulse: Company Jobs & Hiring Signals in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.edtool79-collab%2Fats-job-pulse/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ats-job-pulse-company-jobs-hiring-signal": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=hirepulse/ats-job-pulse"
    }
  }
}

README

[ATS Job Pulse logo]

ATS Job Pulse — company jobs & hiring signals for AI agents

Who is hiring, for what, and what changed since yesterday?

ATS Job Pulse is a hosted tool (an Apify Actor) that takes a company domain and returns the company's open jobs plus a compact hiring summary, straight from the company's own job board. It works as an MCP tool for Claude, Cursor and other AI agents, and as a plain HTTP API.

  • Auto-detects the job board from a domain: Greenhouse, Lever, Ashby, Workable, Recruitee, SmartRecruiters
  • Hiring signals: open jobs, new and closed jobs since the last run, breakdown by department, location and technology
  • Per job: title, department, location, remote flag, salary range (when published), posted date, technologies, apply URL
  • Small output on demand: filters and a summary-only mode sized for an agent's context window
  • Pay per company: $0.05 per successfully processed company. Companies that are not found are free

➡️ Run it: https://apify.com/hirepulse/ats-job-pulse

Use it from an AI agent (MCP)

Add the Apify MCP server with this tool enabled to your MCP client:

json
{  "mcpServers": {    "ats-job-pulse": {      "url": "https://mcp.apify.com/?actors=hirepulse/ats-job-pulse"    }  }}

The first connection opens a browser window to sign in to Apify (a free account is enough to start).

Then ask, for example:

  • "How many open jobs does stripe.com have, and in which departments?"
  • "Which of ramp.com, linear.app and notion.so opened new engineering roles since the last check?"
  • "Does figma.com hire for Kubernetes or LLM skills? Show salary ranges."
  • "List remote data-engineering jobs at these ten companies."

Use it over HTTP

bash
curl -X POST "https://api.apify.com/v2/acts/hirepulse~ats-job-pulse/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \  -H "Content-Type: application/json" \  -d '{"companies": ["stripe.com", "linear.app"], "output_mode": "summary_only"}'

Input

Only companies is required. See examples/ for ready-to-use inputs.

FieldDefaultDescription
companiesrequiredDomains (stripe.com) or board slugs (stripe). Prefix to force an ATS: greenhouse:stripe, lever:spotify, ashby:linear, workable:huggingface, recruitee:bunq, smartrecruiters:BoschGroup.
output_modejobs_and_summaryjobs_and_summary, summary_only (smallest) or jobs_only.
track_difftrueFlag each job NEW / EXISTING / CLOSED versus the previous run.
state_iddefault_stateName of the saved history. Runs sharing a state_id are compared.
only_changesfalseReturn only NEW and CLOSED jobs.
title_keywords, departments, locations, technologiesKeep jobs matching any of the given values.
remote_onlyfalseKeep remote jobs only.
max_jobs_per_company0Cap on job records per company (0 = no limit).
extract_tech_keywordstrueDetect technologies in job titles and descriptions.

Output

Two kinds of records, told apart by record_type.

company_summary — one per company:

json
{  "record_type": "company_summary",  "company_domain": "linear.app",  "ats_type": "ashby",  "total_active_jobs": 31,  "remote_jobs": 31,  "jobs_with_salary": 12,  "is_first_run": false,  "new_jobs": 2,  "closed_jobs": 1,  "new_job_titles": ["Senior Product Engineer", "Enterprise Account Executive"],  "closed_job_titles": ["Support Specialist"],  "jobs_by_department": { "GTM": 15, "Product": 13, "Operations": 3 },  "top_locations": { "North America": 19, "Europe": 8 },  "top_technologies": { "React": 8, "TypeScript": 8, "GraphQL": 7 }}

job — one per job posting:

json
{  "record_type": "job",  "company_domain": "ramp.com",  "ats_type": "ashby",  "job_id": "…",  "title": "Security Engineer, Cloud",  "department": "Engineering",  "location": "New York, NY",  "is_remote": false,  "posted_date": "2026-09-03T13:30:34+00:00",  "salary": "$211.4K - $290.6K",  "apply_url": "https://jobs.ashbyhq.com/ramp/…",  "detected_technologies": ["AWS", "Kubernetes", "Python", "Terraform"],  "status": "NEW"}

Limitations

  • Companies on other systems (Workday, iCIMS, Taleo, in-house career sites) are reported as not found and are not charged.
  • Salary is returned as the employer published it and is not normalized. Many postings state no range.
  • SmartRecruiters publishes no job description in its listing, so technologies there come from the job title only.
  • A bare slug can occasionally match a different company with the same name on another ATS. Use a prefix (lever:acme) to be exact.

Support

Questions and bug reports: open an issue here, or use the Issues tab on the Actor page.

Source: README.md at commit 69d2959

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.0LatestOct 14, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Signals integrations