Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

JobsAI

REMOTE · AGENTS.JOBSAI.CZ

Czech AI job board: search jobs, apply for consenting candidates, manage a company's job postings.

Available components

+1 this week 73 Trust /100

Last scanned (17 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Recent critical change

Authorization (15 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1188 tokens (~54/item across 22 items; 22 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage69
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 8% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

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 →

Changelog

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.

  • 21 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Nov 26 +1
    • Authorization: unverified → fail ▼ critical
    • Destructive annotations: All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

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://agents.jobsai.cz/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jobsai.cz CN=YE1,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 5ea2c57cb9e46ee4f2cf9023475b88cbd4d
SANs: *.jobsai.cz, jobsai.cz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 agents.jobsai.cz. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
cz. DS published 20237 13 Verified
jobsai.cz. 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=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https: https://api.mapy.com; font-src 'self' data:; connect-src 'self' https: wss:; frame-src 'self'; worker-src 'self' blob:; manifest-src 'self'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
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://agents.jobsai.cz/v1/mcp Verified 200
http (plaintext) http://agents.jobsai.cz/v1/mcp HTTPS enforced 301 https://agents.jobsai.cz/v1/mcp
MCP tools · 22 exposed · ~1,188 tokens

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 →

Tool Tokens
archive_job ~29

Archive (unpublish) a job posting of the represented company.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

confirm_job_open ~35

Confirm the job is still open: it stays publicly visible for 60 days from now.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

confirm_job_terms ~39

Confirm listed job conditions as stated by the company (renews their evidence).

NameTypeReqDescription
confirmationobjectyes–
jobIdstringyes–

No output schema declared.

No examples provided.

create_job_draft ~99

Create a draft job posting for the represented company. Nothing is public until publish_job.

NameTypeReqDescription
applyModestring––
applyUrlstring––
descriptionCsstringyes–
kindstringyes–
locationKrajstringyes–
remoteOkbooleanyes–
salaryPeriodstring––
salaryRangeobject––
titleCsstringyes–

No output schema declared.

No examples provided.

execute_approved_action ~64

Execute exactly the command the candidate confirmed, once, while the approval is valid.

NameTypeReqDescription
command––Optional: must equal the confirmed command (including the candidate's edits); otherwise approval_mismatch. Same shape as propose_action.command.
proposalIdstringyes–

No output schema declared.

No examples provided.

get_action_proposal ~45

Read the candidate's decision on a proposal: status, the final command including the candidate's edits, and the one-shot approval window.

NameTypeReqDescription
proposalIdstringyes–

No output schema declared.

No examples provided.

get_application_status ~27

Read an application status for the consent-envelope candidate.

NameTypeReqDescription
applicationIdstringyes–

No output schema declared.

No examples provided.

get_employer_job ~44

Get one of the represented company's job postings for editing: full text, salary, verified conditions with revision, editHash and visibility.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

get_job ~34

Get a public Jobsai job detail by id or slug.

NameTypeReqDescription
idstring––
slugstring––

No output schema declared.

No examples provided.

list_applications ~32

List all applications for the consent-envelope candidate.

NameTypeReqDescription
limitinteger––
statusstring––

No output schema declared.

No examples provided.

list_employer_branches ~26

List the represented company's workplaces (branches) for the job conditions workplace field.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_employer_jobs ~55

List the represented company's own job postings (drafts included) with status and public visibility window. Needs a representation envelope.

NameTypeReqDescription
limitinteger––
pageinteger––
statusstring––

No output schema declared.

No examples provided.

propose_action ~128

Propose one concrete candidate action (application, job question, interview decision, requirements update) for the candidate's own confirmation. Nothing runs until the candidate confirms.

NameTypeReqDescription
agentNotestring–Optional plain-text rationale shown to the candidate as untrusted agent text. Omit it or send a string; null is refused.
command–yesNormalized candidate command the human will review. Exactly one actionType variant applies; interviewId exists only on INTERVIEW_ACCEPT / INTERVIEW_DECLINE / INTERVIEW_CANCEL. Field semantics per act…

No output schema declared.

No examples provided.

publish_job ~41

Publish a draft or archived job of the represented company. The company must be verified and the job must have a salary range.

NameTypeReqDescription
jobIdstringyes–

No output schema declared.

No examples provided.

saved_jobs ~38

List, save, or unsave the consent-envelope candidate's bookmarked jobs.

NameTypeReqDescription
actionstring––
jobIdstring––

No output schema declared.

No examples provided.

search_jobs ~57

Search public Jobsai job listings.

NameTypeReqDescription
krajstring––
limitinteger––
occupationstring––
pageinteger––
querystring––
remoteboolean––

No output schema declared.

No examples provided.

stream_matches ~98

Stream new job matches delivered to a candidate by their job alerts. Pass candidate_pseudonym (the consent envelope sub_pseudonym); the candidate must hold an active consent envelope for this agent with matches:read. Without candidate_pseudonym the stream carries no candidate matches.

NameTypeReqDescription
candidate_pseudonymstring––
limit_per_minuteinteger––
query_idstring––
sincestring––

No output schema declared.

No examples provided.

submit_application ~81

Submit an application on behalf of the candidate represented by the consent envelope.

NameTypeReqDescription
coverLetterAiAssistedboolean–Set true when the cover letter was AI-generated (AI Act Art. 50 transparency; shown to the employer).
coverLetterMarkdownstring––
jobIdstringyes–
useExistingCvboolean––

No output schema declared.

No examples provided.

subscribe ~27

Subscribe to application status change notifications for the consent-envelope candidate.

NameTypeReqDescription
applicationIdsarray––

No output schema declared.

No examples provided.

update_job ~95

Edit a job posting of the represented company (optimistic lock by editHash). Editing an active job is public at once and needs employer_jobs:publish. Changing the title or description raises terms.revision and unconfirms all verified conditions; call get_employer_job again before update_job_terms or confirm_job_terms.

NameTypeReqDescription
changesobjectyes–
expectedEditHashstringyes–
jobIdstringyes–

No output schema declared.

No examples provided.

update_job_terms ~67

Set the verified conditions of a job (salary basis, bonuses, shifts, start, training, remote mode, workplace). A stale terms.revision returns facts_changed with reason stale_terms_revision: read the job again.

NameTypeReqDescription
jobIdstringyes–
termsobjectyes–

No output schema declared.

No examples provided.

withdraw_application ~27

Withdraw an application on behalf of the consent-envelope candidate.

NameTypeReqDescription
applicationIdstringyes–

No output schema declared.

No examples provided.

Install

How do I install the JobsAI MCP server?

JobsAI is a hosted endpoint at https://agents.jobsai.cz/v1/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 · agents.jobsai.cz

# add to Claude Code
claude mcp add --transport http cz-jobsai-jobsai 'https://agents.jobsai.cz/v1/mcp'
Common questions

What is the JobsAI MCP server?

JobsAI is an MCP server listed in the public MCP registry as cz.jobsai/jobsai. Czech AI job board: search jobs, apply for consenting candidates, manage a company's job postings. This page covers its hosted endpoint (https://agents.jobsai.cz/v1/mcp).

Is the JobsAI MCP server safe to use?

JobsAI scores 73 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 JobsAI MCP server expose?

JobsAI exposes 22 tools: search_jobs, get_job, submit_application, get_application_status, list_applications, and 17 more. Their descriptions and schemas cost roughly 1,188 tokens of context every time the server is loaded.

Does the JobsAI MCP server require authentication?

No. We connected to JobsAI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the JobsAI MCP server still maintained?

JobsAI 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 JobsAI MCP server?

VerifyMCP ran 13 checks on JobsAI, 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.