jopp
REMOTE · JOPP.AI
Search open jobs in Switzerland and Liechtenstein and read jopp job briefs.
Available components
Last scanned (1 hour ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 859 tokens (~171/item across 5 items; 5 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://jopp.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jopp.ai | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 96ee38db6fbcb76134c9bab26164e16 |
| SANs: jopp.ai, *.jopp.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jopp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| jopp.ai. | absent | 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 |
| x-frame-options | DENY |
| referrer-policy | same-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://jopp.ai/mcp | Verified | 200 | |
| http (plaintext) | http://jopp.ai/mcp | HTTPS enforced | 301 | https://jopp.ai/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 →
fetch Fetch a job ~36
The full text of one job by its id from search, as a readable document.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The job id from search. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_job Get a job ~53
Full details of one job by its id from search_jobs: facts, salary, description (usually a jopp brief) and the link to the original advert.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The job id from search_jobs. |
| Name | Type | Req | Description |
|---|---|---|---|
| advantageLanguages | array | yes | – |
| applyUrl | string | yes | The original advert: the employer's or source's page to read it in full and apply. |
| category | – | yes | – |
| company | string | yes | – |
| contractType | – | yes | – |
| description | string | yes | Markdown. Usually jopp's brief, a factual summary of the advert; the original advert at applyUrl is authoritative. |
| education | string|null | yes | Lowest education the advert asks for. |
| experience | string|null | yes | Years of experience the advert asks for. |
| id | string | yes | – |
| industry | string|null | yes | – |
| isAgency | boolean | yes | – |
| language | – | yes | Language of title and description. |
| lastSeenAt | string|null | yes | ISO date jopp last saw the advert online. |
| leadership | – | yes | – |
| locations | array | yes | – |
| offerKind | – | yes | – |
| publishedAt | string|null | yes | – |
| requiredLanguages | array | yes | – |
| role | – | yes | – |
| salary | – | yes | "stated" comes from the advert. "estimated" is a jopp estimate of the yearly salary at 100 % workload and is not from the advert. |
| seniority | – | yes | – |
| start | string|null | yes | An ISO date, "immediately" or "by_agreement". |
| status | string | yes | – |
| title | string | yes | – |
| url | string | yes | The job on jopp.ai. |
| withJoppAccount | object | yes | What a person can do with this job after signing in to jopp. |
| workMode | – | yes | – |
| workload | string|null | yes | – |
No examples provided.
list_categories List job categories ~56
jopp's occupation categories and their roles, for the category and role filters of search_jobs. Pass a category key to get its roles with typical job titles.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A category key to list its roles in detail. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | yes | – |
No examples provided.
search Search jobs (simple) ~48
Keyword search over open jobs in Switzerland; returns ids, titles and links. search_jobs offers filters and more fields.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Keywords, e.g. "Pflegefachfrau Bern". |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
search_jobs Search jobs in Switzerland ~416
Search open jobs in Switzerland and Liechtenstein by keywords and filters. Only jobs whose advert is still online are returned. Lehrstellen are listed only with segment apprenticeships. Returns up to 20 jobs per page, newest first for filter-only searches; keyword searches rank by relevance, favouring recent adverts and mixing companies. Use get_job for a job's full description.
| Name | Type | Req | Description |
|---|---|---|---|
| advertLanguages | array | – | Language the advert is written in. |
| cantons | array | – | Two-letter canton codes (ZH, BE, VD, GE, …) or LI for Liechtenstein. |
| category | string | – | A category key from list_categories. |
| contractTypes | array | – | Not for segment apprenticeships. |
| cursor | string | – | nextCursor of a previous search_jobs result; the other arguments are then ignored. |
| excludeAgencies | boolean | – | Leave out recruitment agencies. |
| limit | integer | – | – |
| publishedWithinDays | – | – | – |
| query | string | – | Keywords matched against job title, company and description, with German word forms (e.g. "Pflegefachfrau", "Software Engineer Python"). All words must match; use OR between alternatives, "quotes" fo… |
| requiredLanguages | array | – | Only jobs that require all of these languages. |
| role | string | – | A role key from list_categories; requires its category. |
| salaryStated | boolean | – | Only jobs whose advert states a salary. |
| segment | string | – | jobs (default): regular jobs and internships. apprenticeships: only Lehrstellen (Swiss vocational apprenticeships, Berufslehre). A search lists one of the two, never both. |
| seniorities | array | – | – |
| workModes | array | – | – |
| workloadMax | integer | – | Highest workload in percent of full time (10–100). |
| workloadMin | integer | – | Lowest workload in percent of full time (10–100). |
| Name | Type | Req | Description |
|---|---|---|---|
| nextCursor | string|null | yes | Pass as cursor for the next page; null at the end. |
| results | array | yes | – |
| searchUrl | string | yes | The same search on jopp.ai. |
| total | number | yes | How many open jobs match. |
No examples provided.
How do I install the jopp MCP server?
jopp is a hosted endpoint at https://jopp.ai/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 · jopp.ai
claude mcp add --transport http ai-jopp-jobs 'https://jopp.ai/mcp'
What is the jopp MCP server?
jopp is an MCP server listed in the public MCP registry as ai.jopp/jobs. Search open jobs in Switzerland and Liechtenstein and read jopp job briefs. This page covers its hosted endpoint (https://jopp.ai/mcp).
Is the jopp MCP server safe to use?
jopp scores 83 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 jopp MCP server expose?
jopp exposes 5 tools: search_jobs, get_job, list_categories, search, fetch. Their descriptions and schemas cost roughly 609 tokens of context every time the server is loaded.
Does the jopp MCP server require authentication?
No. We connected to jopp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the jopp MCP server still maintained?
jopp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.