# Applystead [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/usr-bin-roygbiv/applystead-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/applystead

## Description
Search open jobs from employers' own career sites: roles, companies and posting status.

## Tools
Capabilities this server exposes over MCP:

- **search_jobs** — Matching open jobs, newest first
- **get_company_jobs** — The company (name, ATS, open roles, company page) and its 10 newest jobs
- **check_job_posting** — Whether the posting is `open`, `closed`, `unknown` or `unsupported

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "applystead": {
    "url": "https://applystead.com/mcp"
  }
}
```

## Documentation

## What Applystead MCP server does

Applystead MCP server exposes public job and company data through three read-only MCP tools. The listings come from employers' own career sites and applicant tracking systems, including Greenhouse, Lever, Ashby, Workday, and other supported systems.

Use `search_jobs` to find matching open roles, returned with the newest postings first. Searches can include a text query, a two-letter remote-country code, a company name or slug, an internship or new-grad filter, whether compensation is listed, and a posting-age window. Results are limited to 20 jobs per request, with 10 returned by default.

`get_company_jobs` returns the matched company's name, ATS, company page, open-role information, and its 10 newest jobs. `check_job_posting` accepts an HTTPS job URL and reports one of four states: `open`, `closed`, `unknown`, or `unsupported`.

## How it works

The service is hosted by Applystead rather than run inside the client. Clients send MCP requests to `https://applystead.com/mcp` using Streamable HTTP, and the server returns stateless JSON responses. The data is public, so authentication is not required.

All three operations are read-only and idempotent. Job results link to their Applystead job pages, where the listing includes an Apply with Applystead path. The server does not create applications or modify employer data.

## Setup and configuration

Applystead MCP server needs no local package installation, API key, or sign-in. Add the remote URL to an MCP client that supports Streamable HTTP. In Claude, it can be added as a custom connector with OAuth left empty. In ChatGPT, enable Developer mode, create an app connector, and provide the same URL without authentication.

A generic MCP configuration uses an HTTP server entry with the URL `https://applystead.com/mcp`. Requests can also be tested directly with an MCP JSON-RPC call, such as invoking `search_jobs` with a query and result limit.

## Tools and capabilities

- Search current open roles by text, company, remote country, job type, listed pay, and posting age.
- Retrieve a company's ATS, company page, open-role information, and 10 newest jobs.
- Check a job posting URL against the available listing data.
- Filter search results to postings from the last 1 to 720 hours.
- Limit search responses to 1 to 20 jobs.

## Limitations and notes

Coverage is limited to roles that Applystead publishes from employer career sites and supported applicant tracking systems. A posting check may return `unknown` or `unsupported`, so neither result indicates that a job is open. Search terms are capped at 120 characters, and remote-country filtering requires an ISO two-letter code.

Applystead MCP server provides public listing information only. The README states that requests are not stored, tool arguments are not logged, and responses contain information already shown on Applystead's public job and company pages. The repository's README and configuration files use the MIT License, while the hosted server is operated at the Applystead URL.

_Full upstream README: https://allmcps.com/mcp/applystead/readme_

