Skip to content

jobctl MCP server

io.github.DmytroRybka/jobctlDmytroRybkastreamable-httpv0.5.1Scanned

Job application tracker for developers - AI agents write over MCP, you review in a dashboard.

11 tools: 2 can delete or cancel things, 5 change things and 4 only read.

Tools: 2 delete, 0 irreversible, 5 write, 4 read.
  • Reads private data · 3
  • Reads text others write · 1
  • Can send data out · 2
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the jobctl MCP server can do

The jobctl MCP server is published by the GitHub account DmytroRybka. It has 11 tools. It can delete or cancel things (2 tools: attach_analysis and attach_file) and create or change data (5 tools: add_application, update_application, add_note, log_interview and 1 more). 4 tools only read.

3 tools read private data (log_interview, get_planned and get_application); 1 tool brings in text other people can write (log_interview); 2 tools can send data out of your system (add_application and update_application). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 0.5.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Deletes or cancels 2Claude Code: deny
  • attach_analysisAttach a markdown company analysis (research you produced) to an application.No findings

    Why it is in this group

    • The name "attach_analysis" says "attach": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Attach a markdown company analysis (research you produced) to an application. Single document per application — a new call REPLACES the previous one. Max 100000 bytes (~100 KB) of utf-8. The user reads it in the dashboard, e.g. before an interview. Example: `attach_analysis({application_id: "…", markdown: "# Bosch\n\n## Culture…"})`.

    Annotations the server declares

    • title: Attach company analysis
    • readOnlyHint: false
    • destructiveHint: true
  • attach_fileAttach or replace a file on an application so the user sees it in the dashboard: a CV/resume (kind: 'cv') or a cover letter (kind: 'cover_letter').No findings

    Why it is in this group

    • The name "attach_file" says "attach": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Attach or replace a file on an application so the user sees it in the dashboard: a CV/resume (kind: 'cv') or a cover letter (kind: 'cover_letter'). Pass the file bytes as base64 in data_base64. One file per (application, kind) - a new call REPLACES the previous one. Max ~5 MB; pdf/doc/docx/txt/md (MIME is inferred from the filename if you omit it). Call this whenever you generate a tailored CV or cover letter for an application. Example: `attach_file({application_id: "…", kind: "cv", filename: "CV_Cursor.pdf", data_base64: "JVBERi0…"})`.

    Annotations the server declares

    • title: Attach CV or cover letter
    • readOnlyHint: false
    • destructiveHint: true
Changes things 5Claude Code: ask
  • add_applicationTrack a new job application.Can send data outNo findings

    Why it is in this group

    • The name "add_application" says "add": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Track a new job application. Pass either a single `raw` line — `add_application({raw: "Bosch, Tech Lead, prio A, due friday, remote, via LinkedIn"})` — or structured fields (`company` and `role` required then). Returns the created application and possible-duplicate warnings; if duplicates are listed, tell the user instead of creating again.

    Annotations the server declares

    • title: Add application
    • readOnlyHint: false
    • destructiveHint: false
  • add_noteAppend a free-text note to an application timeline — recruiter call summaries, interview instructions, pasted messages.No findings

    Why it is in this group

    • The name "add_note" says "add": a word for a change.
    Description, as the server wrote it
    Append a free-text note to an application timeline — recruiter call summaries, interview instructions, pasted messages. Multiline markdown is fine. Example: `add_note({application_id: "…", text: "Recruiter: team of 5, on-call rotation, offer range 85-95k"})`.

    Annotations the server declares

    • title: Add note
    • readOnlyHint: false
    • destructiveHint: false
  • attach_interview_fileAttach prep material to a specific interview so the user sees it next to that round in the dashboard: the prep document you wrote, the job description, a deck, notes the company se…No findings

    Why it is in this group

    • The name "attach_interview_file" says "attach": a word for a change.
    Description, as the server wrote it
    Attach prep material to a specific interview so the user sees it next to that round in the dashboard: the prep document you wrote, the job description, a deck, notes the company sent. Max 3 files per interview, 20000000 bytes (20 MB) each; pass the bytes as base64. Get interview ids from get_application. Example: `attach_interview_file({application_id: "…", interview_id: "…", filename: "prep-round2.md", data_base64: "IyBQcmVw…"})`.

    Annotations the server declares

    • title: Attach interview prep file
    • readOnlyHint: false
    • destructiveHint: false
  • log_interviewLog an interview for an application (max 10 per application): when it takes place, its status (planned or done), who attends (each with an optional profile link), related links (pr…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "log_interview" says "log": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe description's first sentence says "log" and "meeting": it reads calendars.
    • untrusted-inputThe description's first sentence says "log" and "url": it reads web pages, which anyone can write.

    Findings

    • Warn

      The server marks "log_interview" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "log_interview" says "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Log an interview for an application (max 10 per application): when it takes place, its status (planned or done), who attends (each with an optional profile link), related links (prep materials the company sent, meeting URL), and a short recap of what was discussed. Also keeps the application's next-interview date in sync. Example: `log_interview({application_id: "…", scheduled_at: "2026-07-20T14:00:00+02:00", status: "planned", attendees: [{name: "Anna Weber (HR)", url: "https://linkedin.com/in/annaweber"}], links: [{label: "Prep materials", url: "https://company.com/interview-prep"}], recap: "System design round"})`.

    Annotations the server declares

    • title: Log interview
    • readOnlyHint: false
    • destructiveHint: false
  • update_applicationUpdate fields of an application (get the id from list_applications).Can send data outNo findings

    Why it is in this group

    • The name "update_application" says "update": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Update fields of an application (get the id from list_applications). Status changes are logged to the timeline automatically. Example: `update_application({id: "…", status: "interview", next_action: "prepare system design", next_action_due: "2026-07-20"})`.

    Annotations the server declares

    • title: Update application
    • readOnlyHint: false
    • destructiveHint: false
Only reads 4Show 4 read-only tools
  • get_applicationFull detail of one application: all fields, contacts, recent timeline events, and whether a company analysis is attached (fetch it via the dashboard or attach_analysis to replace).Reads private dataNo findings

    Why it is in this group

    • The name "get_application" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "contact": it reads contacts.
    Description, as the server wrote it
    Full detail of one application: all fields, contacts, recent timeline events, and whether a company analysis is attached (fetch it via the dashboard or attach_analysis to replace).

    Annotations the server declares

    • title: Get application
    • readOnlyHint: true
  • get_dueWhat is burning today: applications with next_action_due today or overdue.No findings

    Why it is in this group

    • The name "get_due" says "get": a word for reading.
    Description, as the server wrote it
    What is burning today: applications with next_action_due today or overdue. Call this when the user asks "what should I do today?" about their job search.

    Annotations the server declares

    • title: Due actions
    • readOnlyHint: true
  • get_plannedWhat is actually SCHEDULED: interviews with their time, attendees and meeting links, plus the actions falling due, for today, tomorrow, or the next seven days.Reads private dataNo findings

    Why it is in this group

    • The name "get_planned" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "meeting": it reads calendars.
    Description, as the server wrote it
    What is actually SCHEDULED: interviews with their time, attendees and meeting links, plus the actions falling due, for today, tomorrow, or the next seven days. Use this whenever the user asks what is planned, what the day or week looks like, or before proposing a time to anyone — get_due only knows action deadlines and is blind to booked interviews. Example: `get_planned({range: "tomorrow"})`.

    Annotations the server declares

    • title: Planned schedule
    • readOnlyHint: true
  • list_applicationsList job applications.No findings

    Why it is in this group

    • The name "list_applications" says "list": a word for reading.
    Description, as the server wrote it
    List job applications. Filter by view (active = default working set, archive = rejected/withdrawn/no-response), status list, priority, or free-text search in company/role. Example: `list_applications({view: "active"})`, `list_applications({q: "bosch"})`.

    Annotations the server declares

    • title: List applications
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__jobctl__log_interview"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://app.jobctl.app/.well-known/oauth-protected-resource
Authorization servers
https://app.jobctl.app
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (2 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.jobctl.app/mcp: tools/list returned 11 tools to an anonymous client, including attach_analysis (destructive), attach_file (destructive), add_application (write), update_application (write), add_note (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "log_interview" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false}; The name "log_interview" says "log": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.5.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http jobctl https://app.jobctl.app/mcp
claude mcp add --transport http jobctl https://app.jobctl.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__jobctl__list_applications",
      "mcp__jobctl__get_due",
      "mcp__jobctl__get_planned",
      "mcp__jobctl__get_application"
    ],
    "ask": [
      "mcp__jobctl__add_application",
      "mcp__jobctl__update_application",
      "mcp__jobctl__add_note",
      "mcp__jobctl__log_interview",
      "mcp__jobctl__attach_interview_file"
    ],
    "deny": [
      "mcp__jobctl__attach_analysis",
      "mcp__jobctl__attach_file"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as jobctl. Review it before you use it.

Capability tags behind 5 rules
  • mcp__jobctl__add_application outbound
  • mcp__jobctl__update_application outbound
  • mcp__jobctl__log_interview private-data, untrusted-input
  • mcp__jobctl__get_planned private-data
  • mcp__jobctl__get_application private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.DmytroRybka/jobctl/verify?hash=ec7e775de4d6b0f51ac97cc4f3c1fdedc40caf2acc2c677e74b88816b1b012eb" | jq -e '.changed == false'

Pinned hash ec7e775de4d6, from Nov 16, 2026, 17:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.DmytroRybka/jobctl/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.DmytroRybka/jobctl
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.DmytroRybka/jobctl.svg)](https://radar.anlyon.com/servers/io.github.DmytroRybka/jobctl)

Source: MCP Registry. Synced Oct 21, 2026, 18:15 UTC.

jobctl MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the jobctl MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the jobctl MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: attach_analysis and attach_file.

Can the jobctl MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the jobctl MCP server have?

11 tools: 2 destructive, 5 write, 4 read. attach_analysis, attach_file, add_application, update_application, add_note, log_interview, attach_interview_file, list_applications and 3 more.

Does the jobctl MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the jobctl MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): add_application and update_application.

Has the jobctl MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.