# jobctl (remote · app.jobctl.app)

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

- Trust score: 77/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- remote · `app.jobctl.app`: 77/100 (this document), [markdown](https://verifymcp.io/servers/dmytrorybka-jobctl/app.md), [page](https://verifymcp.io/servers/dmytrorybka-jobctl/app)

## Channel facts

- Endpoint: `https://app.jobctl.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1851 tokens (~185/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.dmytrorybka-jobctl]
url = "https://app.jobctl.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dmytrorybka-jobctl": {
      "type": "remote",
      "url": "https://app.jobctl.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dmytrorybka-jobctl --url https://app.jobctl.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dmytrorybka-jobctl:
    url: "https://app.jobctl.app/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dmytrorybka-jobctl": {
      "type": "http",
      "url": "https://app.jobctl.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 75, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 67)

First indexed and scored.

## MCP tools (10)

### `add_application` (~446 tokens)

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 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.

Input parameters:

- `applied_at` (string): ISO date YYYY-MM-DD
- `company` (string)
- `cv_variant` (string): Which CV was sent: DE, EN, AI-focused…
- `location` (string)
- `match_notes` (string): Markdown match assessment: why the candidate fits this role — strengths vs requirements, gaps, level/salary advice, process notes. Save your vacancy analysis here so it is not lost; shown as an expan…
- `next_action` (string): e.g. "follow-up", "thank-you email"
- `next_action_due` (string): ISO date YYYY-MM-DD
- `next_interview_at` (string): ISO datetime, e.g. 2026-07-20T14:00:00+02:00
- `priority` (string): A = top priority
- `raw` (string): Free-form line: "Company, Role, prio A|B|C, due <date>, remote|hybrid|onsite, via <source>, https://…, in <location>, applied <date>"
- `remote` (string)
- `remote_note` (string): e.g. "2 days office"
- `role` (string)
- `salary_asked` (integer): What the candidate asked for — yearly gross EUR as a plain number, e.g. 110000
- `salary_range` (integer): Posting salary range upper bound — yearly gross EUR, plain number
- `salary_range_min` (integer): Posting salary range lower bound — yearly gross EUR, plain number
- `source` (string): LinkedIn, referral, recruiter, Easy Apply…
- `status` (string)
- `url` (string): Link to the job posting

### `list_applications` (~142 tokens)

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 company/role. Example: `list_applications({view: "active"})`, `list_applications({q: "bosch"})`.

Input parameters:

- `limit` (integer)
- `priority` (string)
- `q` (string): Search in company/role
- `status` (string): Comma-separated: started_apply, waiting_referral, applied, waiting, interview, offer, accepted, rejected, no_response, on_hold, withdrawn, archived
- `view` (string)

### `update_application` (~385 tokens)

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: "…", status: "interview", next_action: "prepare system design", next_action_due: "2026-07-20"})`.

Input parameters:

- `applied_at` (string): ISO date YYYY-MM-DD
- `company` (string)
- `cv_variant` (string): Which CV was sent: DE, EN, AI-focused…
- `id` (string, required)
- `location` (string)
- `match_notes` (string): Markdown match assessment: why the candidate fits this role — strengths vs requirements, gaps, level/salary advice, process notes. Save your vacancy analysis here so it is not lost; shown as an expan…
- `next_action` (string): e.g. "follow-up", "thank-you email"
- `next_action_due` (string): ISO date YYYY-MM-DD
- `next_interview_at` (string): ISO datetime, e.g. 2026-07-20T14:00:00+02:00
- `priority` (string): A = top priority
- `remote` (string)
- `remote_note` (string): e.g. "2 days office"
- `role` (string)
- `salary_asked` (integer): What the candidate asked for — yearly gross EUR as a plain number, e.g. 110000
- `salary_range` (integer): Posting salary range upper bound — yearly gross EUR, plain number
- `salary_range_min` (integer): Posting salary range lower bound — yearly gross EUR, plain number
- `source` (string): LinkedIn, referral, recruiter, Easy Apply…
- `status` (string)
- `url` (string): Link to the job posting

### `add_note` (~85 tokens)

Add note

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"})`.

Input parameters:

- `application_id` (string, required)
- `text` (string, required)

### `log_interview` (~270 tokens)

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), 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"})`.

Input parameters:

- `application_id` (string, required)
- `attendees` (array): Who attends, each with an optional profile link
- `links` (array): Related links: prep materials, meeting URL, docs
- `recap` (string): Short recap of what was discussed
- `scheduled_at` (string, required): ISO datetime with offset, e.g. 2026-07-20T14:00:00+02:00
- `status` (string): planned (default) or done

### `get_due` (~40 tokens)

Due actions

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` (~119 tokens)

Planned schedule

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"})`.

Input parameters:

- `range` (string): today (default), tomorrow, or week (today plus the next 6 days)

### `attach_analysis` (~108 tokens)

Attach company 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 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…"})`.

Input parameters:

- `application_id` (string, required)
- `markdown` (string, required): The analysis as markdown

### `attach_file` (~207 tokens)

Attach CV or cover letter

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…"})`.

Input parameters:

- `application_id` (string, required)
- `data_base64` (string, required): Base64-encoded file bytes
- `filename` (string, required)
- `kind` (string, required)
- `mime` (string): Optional; inferred from the filename extension when omitted

### `get_application` (~49 tokens)

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_analysis to replace).

Input parameters:

- `id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dmytrorybka-jobctl/app#diagnostics

## Score history

- 2026-08-04: 77
- 2026-08-03: 77
- 2026-08-02: 76
- 2026-08-01: 76
- 2026-07-31: 75
- 2026-07-30: 70
- 2026-07-29: 69
- 2026-07-28: 69
- 2026-07-27: 68
- 2026-07-26: 67

## Links

- Remote endpoint: https://app.jobctl.app/mcp
- Website: https://jobctl.app/
- Changelog RSS feed: https://verifymcp.io/servers/dmytrorybka-jobctl/app/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dmytrorybka-jobctl/app/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dmytrorybka-jobctl/app