JobSweep
REMOTE · JOBSWEEP.WORKS
Search 239k open jobs from 3,519 company career sites. Free tier; an API key raises limits.
Available components
Last scanned (20 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 739 tokens (~123/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Tool “get_coverage” rewrote its description, which is the text the model reads security
- 15 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- “search_companies” reworded the description of “limit” cosmetic
- “search_jobs” reworded the description of “limit” cosmetic
- 14 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://jobsweep.works/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jobsweep.works | CN=YE2,O=Let's Encrypt,C=US | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 59730d3232261f3f4fe067fff9fdd7a78db |
| SANs: *.jobsweep.works, jobsweep.works | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jobsweep.works. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| works. | DS published | 10889 | 8 | Verified |
| jobsweep.works. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jobsweep.works/mcp | Verified | 200 | |
| http (plaintext) | http://jobsweep.works/mcp | HTTPS enforced | 301 | https://jobsweep.works/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_coverage Platform coverage ~102
Which hiring platforms (ATS) are covered and whether they work: status (`live`, `blocked`, `no live deployments`, `no connector`, `no tenants`), career sites, open jobs and last successful crawl. `required` is true for platforms on the challenge list of 78 and false for additional ones. Not for finding jobs; use search_jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| status | – | – | Only platforms with this status; omit for all platforms. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_job Get job details ~67
Get one job in full: plain-text description (truncated to 8000 characters), salary, every source posting it was merged from and their change history. Call after search_jobs with a job_id.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Job `id` from search_jobs. |
Structured output declared, but exposes no named fields.
No examples provided.
index_stats Index size and freshness ~47
Size and freshness of the index: open jobs, postings, career sites, live platforms, last successful crawl and recent crawl success rate. Not for finding jobs; use search_jobs.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_filter_values List filter values ~58
List the values accepted by the `remote` and `employment_type` filters of search_jobs with open job counts, plus top countries (ISO code, name) and companies. Call before search_jobs when you need valid filter values.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_companies Search companies ~78
Find companies by name with their number of open jobs, largest first. Pass a returned name as `company` to search_jobs to list that company's jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum companies to return, 1-50 (1-25 without an API key). |
| q | – | – | Company name contains (case-insensitive). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
search_jobs Search jobs ~274
Search open jobs across all indexed career sites (duplicates merged). Use list_filter_values for valid filter values and get_job for a job's full description. Returns `jobs` (id, title, company, location, remote, employment_type, salary, posted_at, first_seen_at, url, company_url, apply_url) newest or most relevant first, and `next_cursor`. For the next page repeat the call with the same filters and `cursor` set to `next_cursor`; null means the last page.
| Name | Type | Req | Description |
|---|---|---|---|
| company | – | – | Company name contains (case-insensitive). |
| cursor | – | – | `next_cursor` from the previous call with the same filters. |
| employment_type | – | – | Employment type; see list_filter_values for counts. |
| limit | integer | – | Jobs per page, 1-50 (1-25 without an API key). |
| location | – | – | Matches city, region or country text of the job location, e.g. `Berlin` or `Germany`. |
| posted_after | – | – | ISO 8601 timestamp with timezone; jobs posted or first seen after it. |
| q | – | – | Full-text query in web search syntax: quoted phrases, OR, -exclude. Omit to list the newest jobs. |
| remote | – | – | Work mode; see list_filter_values for counts. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the JobSweep MCP server?
JobSweep is a hosted endpoint at https://jobsweep.works/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jobsweep.works
claude mcp add --transport http works-jobsweep-jobsweep 'https://jobsweep.works/mcp'
What is the JobSweep MCP server?
JobSweep is an MCP server listed in the public MCP registry as works.jobsweep/jobsweep. Search 239k open jobs from 3,519 company career sites. Free tier; an API key raises limits. This page covers its hosted endpoint (https://jobsweep.works/mcp).
Is the JobSweep MCP server safe to use?
JobSweep scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the JobSweep MCP server expose?
JobSweep exposes 6 tools: search_jobs, get_job, list_filter_values, search_companies, index_stats, get_coverage. Their descriptions and schemas cost roughly 626 tokens of context every time the server is loaded.
Does the JobSweep MCP server require authentication?
No. We connected to JobSweep without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the JobSweep MCP server still maintained?
JobSweep is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the JobSweep MCP server?
VerifyMCP ran 13 checks on JobSweep, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.