Career Site Jobs Scraper

io.github.catalyst-labs-devPublished by GitHub account catalyst-labs-devv1.0.2Updated Oct 25, 2026

Live jobs from companies you name, 17 ATS, one schema; misses never charged.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote Apify MCP server that pulls live job postings from named companies across 17 applicant tracking systems into one schema.

What you can do
Query live job listings for companies you specify, aggregated across 17 applicant tracking systems (ATS). Receive results in a single normalized schema rather than per-ATS formats. Runs as a hosted Apify MCP endpoint, so the assistant calls it directly over HTTP.
When to use it
Useful when you want an assistant to gather current openings from specific employers' career sites without building separate integrations for each ATS, for example for recruiting research or job-market monitoring.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: an Apify API token sent as an Authorization header in the form Bearer token, or OAuth sign-in with Apify if the client supports it. An Apify account is needed.
Before you install
Requires an Apify API token or Apify OAuth sign-in; treat the token as a secret. The service is hosted by Apify and queries are sent to a third party, which may bill your Apify account for usage (the description states misses are not charged).

Installation

In SourceWeft

  1. Open Career Site Jobs Scraper 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.catalyst-labs-dev%2Fcareer-site-jobs-scraper/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": {
    "career-site-jobs-scraper": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=catalyst-labs/career-site-jobs-scraper"
    }
  }
}

README

This repository has no README.

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

2
  1. v1.0.2LatestOct 25, 2026
  2. v1.0.1Oct 19, 2026

Score

60% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.