Home / MCP registry index / cz.jobsai/jobsai
JobsAI
cz.jobsai/jobsai in the official MCP registry.
Endpoint https://agents.jobsai.cz/v1/mcp.
The registry describes it as: Czech AI job board: search jobs, apply for consenting candidates, manage a company's job postings.
We read its 22 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_jobs get_job submit_application get_application_status list_applications subscribe stream_matches withdraw_application saved_jobs propose_action get_action_proposal execute_approved_action list_employer_jobs get_employer_job list_employer_branches create_job_draft update_job update_job_terms confirm_job_terms publish_job archive_job confirm_job_open
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/cz-jobsai-jobsai)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.