Remote jobs re-checked against each employer's own ATS, with evidence they're still open.
Maintained bystillopen.work(verified)Also a maintainer?
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
a domain such as example.com; a pasted URL is reduced to its host
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http jobs https://stillopen.work/api/v1/mcp
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.
| Argument | Type | Description |
|---|---|---|
| domain* | string | a domain such as example.com; a pasted URL is reduced to its host |
{
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "a domain such as example.com; a pasted URL is reduced to its host"
}
},
"additionalProperties": false
}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`.
| Argument | Type | Description |
|---|---|---|
| ids* | array | up to 100 listing ids |
{
"type": "object",
"required": [
"ids"
],
"properties": {
"ids": {
"type": "array",
"items": {
"type": "integer"
},
"maxItems": 100,
"minItems": 1,
"description": "up to 100 listing ids"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| company_slug* | string | a `company_slug` from any record |
{
"type": "object",
"required": [
"company_slug"
],
"properties": {
"company_slug": {
"type": "string",
"description": "a `company_slug` from any record"
}
},
"additionalProperties": false
}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`.
| Argument | Type | Description |
|---|---|---|
| id* | integer | the listing id |
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"minimum": 1,
"description": "the listing id"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| q | string | free text over the title, the skills read from the ad, and the ad body |
| loc | string | an 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 apply from here', so it includes roles open across a region containing it and roles open worldwide; a record's `locations` may therefore not name the country |
| pay | integer | minimum 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 |
| area | string | functional area, read from the title rather than from the employer's department field |
| level | string | seniority, read from the title. `unspecified` is the 40% of titles that state none, which is not the same as mid |
| limit | integer | 1-20, default 10 |
| cursor | string | from a previous response's `next_cursor` |
| company | string | a `company_slug` from any record. Not a company name — names collide, and several here belong to two unrelated employers |
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "free text over the title, the skills read from the ad, and the ad body"
},
"loc": {
"type": "string",
"description": "an 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 apply from here', so it includes roles open across a region containing it and roles open worldwide; a record's `locations` may therefore not name the country"
},
"pay": {
"enum": [
40000,
60000,
80000,
100000,
120000,
150000,
200000
],
"type": "integer",
"description": "minimum 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"
},
"area": {
"enum": [
"consulting",
"content",
"customer",
"design",
"engineering",
"finance",
"healthcare",
"legal",
"operations",
"people",
"product",
"sales_marketing"
],
"type": "string",
"description": "functional area, read from the title rather than from the employer's department field"
},
"level": {
"enum": [
"junior",
"mid",
"senior",
"lead",
"manager",
"head",
"unspecified"
],
"type": "string",
"description": "seniority, read from the title. `unspecified` is the 40% of titles that state none, which is not the same as mid"
},
"limit": {
"type": "integer",
"maximum": 20,
"minimum": 1,
"description": "1-20, default 10"
},
"cursor": {
"type": "string",
"description": "from a previous response's `next_cursor`"
},
"company": {
"type": "string",
"description": "a `company_slug` from any record. Not a company name — names collide, and several here belong to two unrelated employers"
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| url* | string | the job's URL |
| title | string | the job title, if the URL does not name it |
| company | string | the employer, if the URL does not name it |
{
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"description": "the job's URL"
},
"title": {
"type": "string",
"description": "the job title, if the URL does not name it"
},
"company": {
"type": "string",
"description": "the employer, if the URL does not name it"
}
},
"additionalProperties": false
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 18, 2026.