Home / MCP registry index / io.github.DmytroRybka/jobctl
jobctl
io.github.DmytroRybka/jobctl in the official MCP registry.
Endpoint https://app.jobctl.app/mcp.
The registry describes it as: Job application tracker for developers - AI agents write over MCP, you review in a dashboard.
We read its 11 tools on 2026-10-22. 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
add_application list_applications update_application add_note log_interview get_due get_planned attach_analysis attach_file attach_interview_file get_application
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-dmytrorybka-jobctl)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.