StillOpen remote jobs

● Active

work.stillopen/jobs

Remote jobs re-checked against each employer's own ATS, with evidence they're still open.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "jobs": {
      "url": "https://stillopen.work/api/v1/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http jobs https://stillopen.work/api/v1/mcp
VS Code
code --add-mcp '{"name":"jobs","type":"http","url":"https://stillopen.work/api/v1/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Other
Version
1.0.1
Registry
active
Published
11/18/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Looks healthy: StillOpen remote jobs is maintained, open source, hosted endpoint answering without a key.

Maintained
Active
Last commit 4 days ago (Nov 18, 2026), 0 open issues.
Official registry
Active
Published as work.stillopen/jobs in the official MCP registry, version 1.0.1.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
Hosted by the publisher
Your client talks to stillopen.work: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 00:07 UTCStatus history & uptime →
● Working489 msprotocol 2025-06-18v1.0.0tools

The endpoint answered the MCP handshake as "stillopen" and listed 6 tools. Answering since Nov 18, 2026.

Context cost ≈ 5.8k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 6 tools.

Tools (6)

  • search_jobs8 params

    Find fully-remote job listings, each re-checked against the employer's own job board. Returns a summary record per role — no job descriptions, because twenty ads would fill your context with roles the reader did not choose. Call `get_job` for the ad once one looks worth reading. Every record carries `evidence_type` and `verified_at`: present those with the listing rather than asserting it is open.

    Show parameters
    • qstringfree text over the title, the skills read from the ad, and the ad body
    • levelstringseniority, read from the title. `unspecified` is the 40% of titles that state none, which is not the same as mid
    • locstringan ISO 3166-1 alpha-2 country code (`de`), a macro region (`emea`), `worldwide` for roles with no stated restriction, or `unspecified`. A country answers 'can I
    • areastringfunctional area, read from the title rather than from the employer's department field
    • companystringa `company_slug` from any record. Not a company name — names collide, and several here belong to two unrelated employers
    • payintegerminimum annual pay. Compared against the top of the published range in the currency published; nothing is converted, and a job board's estimate is excluded
    • limitinteger1-20, default 10
    • cursorstringfrom a previous response's `next_cursor`
  • get_job1 param

    One listing in full, including the employer's own ad. Use it after `search_jobs` rather than instead of it: this returns thousands of characters of advertisement. The id is the number in a listing URL — /job/9620-company-title is 9620. A listing that was folded into another answers under the id you asked for and reports `merged_into`.

    Show parameters
    • idintegerrequiredthe listing id
  • check_job_status1 param

    Whether each of up to 100 listings is still open, and on what evidence — in one call. The most useful tool here: given a link to a role somebody is about to apply for, this is what separates a live posting from a filled one, with a date and a kind of evidence attached. A closed listing reports whether the closure was **observed** (a source was asked and said the posting was gone) or **inferred** (it aged out, which is a guess about the employer rather than an answer from one). This reads evidence already stored: it reports the result of our most recent check, and does not perform a live check against the employer's board at the moment you call it. Two dates come back and they answer different questions: **`verified_at`** is when we last asked the employer's system and it said yes, and it is the one to show a reader; `last_seen_at` is when a source last carried the posting, which happens far more often and is normally the newer of the two. `last_seen_at` being newer is ordinary, not a contradiction. **`status: unknown` means we have never held this id** — it is not-found, not un-checked. The value for 'nothing has proved it gone but no source has carried it lately' is `unconfirmed`.

    Show parameters
    • idsarrayrequiredup to 100 listing ids
  • get_company_stats1 param

    What one employer's listings on this site add up to: how many roles are open, where they hire, what they hire for, and what their listings disclose about pay. Takes a `company_slug` from any search record. Answers only for employers whose board identity we have confirmed, because a page asserting one company's vacancies under another company's name is the failure this gate exists to prevent.

    Show parameters
    • company_slugstringrequireda `company_slug` from any record
  • check_agent1 param

    Check another agent before calling it. Given a domain, returns the open-source a2a-agent-checker's verdict on its A2A Agent Card (`/.well-known/agent-card.json`) and whether its endpoint answers a GetTask probe correctly, plus how many of the last 30 days it was reachable. Agents we already watch are answered from our daily log (`source: watch_log`); otherwise one live check is made (`source: live`): one card fetch and at most one GetTask per binding on the card's own host. It never sends the agent a message. A `fail` verdict means the card or endpoint breaks the A2A v1.0 spec, which includes agents still on the older 0.3 format.

    Show parameters
    • domainstringrequireda domain such as example.com; a pasted URL is reduced to its host
  • verify_job3 params

    Is the job behind this URL still open? Takes a job URL from anywhere. A posting on an employer's ATS that we track is answered from our stored evidence (`matched_by: ats_posting`); any other URL is matched by the company and title in its words (`url_words`) and refused unless exactly one role fits. A URL naming neither, such as a LinkedIn job id, needs `company` and `title` (`company_title`). A supported ATS posting we do not track gets one live check of the employer's own board (`result: checked`, `evidence_type: ats_checked_once`): `not_listed` may also mean a mistyped URL, so never present it as closed. The page itself is never fetched unless it is the employer's ATS. Free allowance of 20 URLs a day per client address, shared with the HTTP endpoint.

    Show parameters
    • urlstringrequiredthe job's URL
    • companystringthe employer, if the URL does not name it
    • titlestringthe job title, if the URL does not name it

Checked by Serverdex with a plain initialize + tools/list call to stillopen.work/api/v1/mcp, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 18, 2026
Stars
0
Forks
0
Last push
Nov 18, 2026
License
MIT

Python

From the README

AI remote job finder, powered by StillOpen A small, dependency-free Python example of the StillOpen API: search fully-remote jobs, re-check each one in a single batch call, and print the evidence that it is still open — not just the listing. Most job data goes stale silently. StillOpen re-reads every listing against the employer's own applicant tracking system (ATS: Greenhouse, Lever, Ashby, Workable, Workday…) and expires it when the employer takes it down. Every record says how it was checked and when. Run it Python 3.9+, standard library only, no API key. --loc takes a country code (de), a region (emea) or worldwide. A country means "can I apply from here", so it includes roles open across a region that contains it. What it calls evidencetype is the field to read: atsverified means the employer's own ATS was re-read and still lists the posting. A closed listing comes back with closure: observed when we saw the employer remove it. Full field reference: stillopen.work/llms.txt and stillopen.work/agents. For AI assistants The same data is an MCP server at https://stillopen.work/api/v1/mcp (tools searchjobs, getjob, checkjobstatus, verify_job, getcompanystats) and an A2A agent. Read-only, no key. Terms The API is free within its published rate limits. Wherever you show StillOpen data, show "Data provided by StillOpen" linked to https://stillopen.work and link each listing to its canonical_url. See stillopen.work/api-terms. This example is MIT licensed.

Read the full README on GitHub →

Remotes

  • streamable-httphttps://stillopen.work/api/v1/mcp

The most-starred Other servers in the index, with their live-check result.

ServerStarsLast pushLive check
Labelhead Artist Momentum114,594Nov 2026Working
World Monitor91,002Nov 2026Needs sign-in
Tldraw51,470Nov 2026Working
OpenSEO28,515Nov 2026Needs sign-in
Windows MCP11,833Nov 2026Local / not checked

StillOpen remote jobs: questions people ask

Is StillOpen remote jobs a remote or a local MCP server?
According to its entry in the official MCP registry, StillOpen remote jobs ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does StillOpen remote jobs need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is StillOpen remote jobs safe to use?
Looks healthy: StillOpen remote jobs is maintained, open source, hosted endpoint answering without a key. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is StillOpen remote jobs still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 18, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 18, 2026.
What tools does StillOpen remote jobs expose?
6 tools as listed by the server itself during the live check, including search_jobs, get_job, check_job_status, get_company_stats, check_agent. The full list with parameters is in the Live check section above.
How do I add StillOpen remote jobs to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Other →

Add the badge to your site

Show visitors that StillOpen remote jobs is listed here — it’s also the link we check for a free listing.

StillOpen remote jobs — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/work-stillopen-jobs?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="StillOpen remote jobs — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![StillOpen remote jobs — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/work-stillopen-jobs?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/work-stillopen-jobs) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/work-stillopen-jobs) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/work-stillopen-jobs)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/work-stillopen-jobs"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/work-stillopen-jobs"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/work-stillopen-jobs"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).