# io.github.DmytroRybka/jobctl

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.5.1
- **Author:** io.github.DmytroRybka
- **License:** Unknown
- **Endpoints:** streamable-http https://app.jobctl.app/mcp
- **Source:** https://jobctl.app
- **Endpoint health:** reachable (last checked 2026-09-13T21:07:44.292Z, 4 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-13T21:07:44.292Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.
**Findings**
- injection-shaped content (note) in the `log_interview` tool: Links to undeclared domains: linkedin.com, company.com

## Tools

11 declared. Observed from a live `tools/list` probe.
- `add_application` — 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 struc
- `list_applications` — List job applications. Filter by view (active = default working set, archive = rejected/withdrawn/no-response), status list, priority, or free-text search in co
- `update_application` — Update fields of an application (get the id from list_applications). Status changes are logged to the timeline automatically. Example: `update_application({id: 
- `add_note` — Append a free-text note to an application timeline — recruiter call summaries, interview instructions, pasted messages. Multiline markdown is fine. Example: `ad
- `log_interview` — 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
- `get_due` — 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.
- `get_planned` — 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. 
- `attach_analysis` — Attach a markdown company analysis (research you produced) to an application. Single document per application — a new call REPLACES the previous one. Max 100000
- `attach_file` — 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 fil
- `attach_interview_file` — 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, 
- `get_application` — 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_a

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"jobctl\": {\n      \"type\": \"http\",\n      \"url\": \"https://app.jobctl.app/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.DmytroRybka%2Fjobctl
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.DmytroRybka%2Fjobctl/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.DmytroRybka%2Fjobctl
- HTML page: https://forgeregistry.com/registry/io.github.DmytroRybka%2Fjobctl
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.