Job Tracker runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 31 Oct 2026.
Local job-search tracker: roles, a status machine with evidence, rules, interviews, daily reports.
What the code does
We read the source, 14 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
proc = subprocess.run(
const tsc = spawnSync(process.execPath, [TSC, '-p', join(REPO, 'registry', 'tsconfig.build.json'), '--outDir', out], { encoding: 'utf8' });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Job Tracker
same job, measured the same wayDiagnoses Apple .ips crash reports: ranks likely causes with cited evidence, not just a stack trace.
Find lab-report identities and clinical research with dated sources and evidence limitations.
Research intelligence for AI coding agents. 2M+ CS papers with evidence and tradeoffs.
Deep Research MCP for multi-round investigations, traceable evidence, and cited reports.
Mine the architecture rules your TypeScript repo already enforces, with the evidence attached.
AI testing harness with Jay: risk-based checks, bug investigation, and local evidence reports.
Search arXiv papers and read Scout reports with methods, evidence and verification points.
Personal bill tracker: due dates, payments and spending reports. Sign in with Google or LINE.
Job Tracker — questions
Answers built from our own checks of this server.