jobctl

REMOTE · APP.JOBCTL.APP · SCANNED AUG 3

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

Available components

+9 this week 77 77 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security89

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
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. View diagnostics → Pass
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability66

AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage88

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
63% of tool parameters carry a description.Partial

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · app.jobctl.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +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.
1 Aug 26 +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.
31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +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.
28 Jul 26 +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.
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 67

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://app.jobctl.app/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=app.jobctl.app	CN=Amazon RSA 2048 M01,O=Amazon,C=US	14 Jul 2026	27 Jan 2027	RSA 2048	SHA256-RSA	e5a890c018b296998ff507167e0632a
SANs: app.jobctl.app, 18hd4a9bb6ay368o83bnqttsuo5z62m.app.jobctl.app
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA)	CN=Amazon Root CA 1,O=Amazon,C=US	23 Aug 2022	23 Aug 2030	RSA 2048	SHA256-RSA	77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA)	CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US	25 May 2015	31 Dec 2037	RSA 2048	SHA256-RSA	67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

DNSSEC insecure

Validation of app.jobctl.app. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
app.	present	23684	8	Verified
jobctl.app.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer realm="jobctl", resource_metadata="https://app.jobctl.app/.well-known/oauth-protected-resource"

Bearer realm="jobctl", resource_metadata="https://app.jobctl.app/.well-known/oauth-protected-resource"

Protected resource metadata

Document	https://app.jobctl.app/.well-known/oauth-protected-resource
Retrieved	Yes
Resource	https://app.jobctl.app
Authorisation server	https://app.jobctl.app

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://app.jobctl.app/mcp	Verified	200
http (plaintext)	http://app.jobctl.app/mcp	HTTPS enforced	301	https://app.jobctl.app:443/mcp

MCP tools — 10 exposed · ~1,851 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

add_application Add application ~446

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 Output Examples

Name	Type	Req	Description
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

No output schema declared.

No examples provided.

add_note Add note ~85

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 Output Examples

Name	Type	Req	Description
application_id	string	yes	—
text	string	yes	—

No output schema declared.

No examples provided.

attach_analysis Attach company analysis ~108

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 Output Examples

Name	Type	Req	Description
application_id	string	yes	—
markdown	string	yes	The analysis as markdown

No output schema declared.

No examples provided.

attach_file Attach CV or cover letter ~207

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 Output Examples

Name	Type	Req	Description
application_id	string	yes	—
data_base64	string	yes	Base64-encoded file bytes
filename	string	yes	—
kind	string	yes	—
mime	string	—	Optional; inferred from the filename extension when omitted

No output schema declared.

No examples provided.

get_application Get application ~49

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 Output Examples

Name	Type	Req	Description
id	string	yes	—

No output schema declared.

No examples provided.

get_due Due actions ~40

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.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_planned Planned schedule ~119

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 Output Examples

Name	Type	Req	Description
range	string	—	today (default), tomorrow, or week (today plus the next 6 days)

No output schema declared.

No examples provided.

list_applications List applications ~142

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 Output Examples

Name	Type	Req	Description
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	—	—

No output schema declared.

No examples provided.

log_interview Log interview ~270

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 Output Examples

Name	Type	Req	Description
application_id	string	yes	—
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	yes	ISO datetime with offset, e.g. 2026-07-20T14:00:00+02:00
status	string	—	planned (default) or done

No output schema declared.

No examples provided.

update_application Update application ~385

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 Output Examples

Name	Type	Req	Description
applied_at	string	—	ISO date YYYY-MM-DD
company	string	—	—
cv_variant	string	—	Which CV was sent: DE, EN, AI-focused…
id	string	yes	—
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

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	67
27 Jul	68
28 Jul	69
29 Jul	69
30 Jul	70
31 Jul	75
1 Aug	76
2 Aug	76
3 Aug	77