Skip to content

StillOpen remote jobs MCP server

work.stillopen/jobsstillopen.workstreamable-httpv1.0.1Scanned

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

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 6
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the StillOpen remote jobs MCP server can do

The StillOpen remote jobs MCP server is published by stillopen.work, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: check_agent and verify_job), but cannot delete data. 4 tools only read.

6 tools bring in text other people can write (search_jobs, get_job, check_job_status and 3 more); 1 tool can send data out of your system (verify_job).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • check_agentCheck another agent before calling it.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote 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.

    Annotations the server declares

    • title: Is this A2A agent real and working?
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verify_jobIs the job behind this URL still open?Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Verify any job
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • check_job_statusWhether each of up to 100 listings is still open, and on what evidence — in one call.Reads text others writeNo findings

    Why it is in this group

    • The name "check_job_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Check whether listings are still open
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_company_statsWhat 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_company_stats" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: What an employer's listings show
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_jobOne listing in full, including the employer's own ad.Reads text others writeNo findings

    Why it is in this group

    • The name "get_job" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Read one listing
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • search_jobsFind fully-remote job listings, each re-checked against the employer's own job board.Reads text others writeNo findings

    Why it is in this group

    • The name "search_jobs" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search remote jobs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:20 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://stillopen.work/api/v1/mcp: tools/list returned 6 tools to an anonymous client, including check_agent (write), verify_job (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http jobs https://stillopen.work/api/v1/mcp
claude mcp add --transport http jobs https://stillopen.work/api/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jobs__search_jobs",
      "mcp__jobs__get_job",
      "mcp__jobs__check_job_status",
      "mcp__jobs__get_company_stats"
    ],
    "ask": [
      "mcp__jobs__check_agent",
      "mcp__jobs__verify_job"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jobs. Review it before you use it.

Capability tags behind 6 rules
  • mcp__jobs__search_jobs untrusted-input
  • mcp__jobs__get_job untrusted-input
  • mcp__jobs__check_job_status untrusted-input
  • mcp__jobs__get_company_stats untrusted-input
  • mcp__jobs__check_agent untrusted-input
  • mcp__jobs__verify_job untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/work.stillopen/jobs/verify?hash=e4b170dae8302b3de7d6a4a11dc9733fa1584b2b004903d2aeb3223cad61124d" | jq -e '.changed == false'

Pinned hash e4b170dae830, from Nov 18, 2026, 11:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/work.stillopen/jobs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for work.stillopen/jobs
[![Anlyon Radar](https://radar.anlyon.com/badge/work.stillopen/jobs.svg)](https://radar.anlyon.com/servers/work.stillopen/jobs)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

StillOpen remote jobs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the StillOpen remote jobs MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the StillOpen remote jobs MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the StillOpen remote jobs MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the StillOpen remote jobs MCP server have?

6 tools: 2 write, 4 read. check_agent, verify_job, search_jobs, get_job, check_job_status and get_company_stats.

Does the StillOpen remote jobs MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the StillOpen remote jobs MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): verify_job.

Has the StillOpen remote jobs MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.