Trackly Cli MCP Server

trackly-cli npm v0.18.1 Source verified

Published by trackly-app — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

AI job search CLI + hosted MCP server with OAuth. 128K+ jobs, 1,900+ companies, 40+ ATS. Works with Claude, ChatGPT, Cursor, Windsurf, Codex via hosted streamable-http or local stdio.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Shell/command execution in server code (lib/agent.js)MTC-SRC-002

In the server's implementation (`lib/agent.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: nSync } = require('node:child_process'); const { apiRequest, downloadFile, getConfigPaths, hasAuth, maintenanceOutput }

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server lib/agent.js

high Shell/command execution in server code (lib/path-diagnostics.js)MTC-SRC-002

In the server's implementation (`lib/path-diagnostics.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: cFile } = require('node:child_process'); const { promisify } = require('node:util'); const execFileAsync = promisify(ex

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server lib/path-diagnostics.js

low Shell/command execution in packaging/dev tooling (scripts/verify-audit-exceptions.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/verify-audit-exceptions.js:7`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: nSync } = require('node:child_process'); const DEFAULT_POLICY_PATH = path.join( __dirname, '..', 'security', 'a

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/verify-audit-exceptions.js

Tools 58

Each tool and what it can reach — statically extracted from the published source.

  • trackly_get_apply_execution_snapshotingests untrusted input
  • trackly_get_apply_protocolingests untrusted input
  • trackly_prepare_resumeingests untrusted input
  • get_more_toolsno sensitive capability
  • trackly_advance_apply_executionno sensitive capability
  • trackly_approve_apply_batch_resumeno sensitive capability
  • trackly_approve_apply_execution_resumeno sensitive capability
  • trackly_askno sensitive capability
  • trackly_bind_apply_surfaceno sensitive capability
  • trackly_cancel_apply_batchno sensitive capability
Show 48 more tools ↓
  • trackly_certify_apply_batch_truthno sensitive capability
  • trackly_checkpoint_apply_batchno sensitive capability
  • trackly_claim_apply_batchno sensitive capability
  • trackly_claim_apply_review_handoffno sensitive capability
  • trackly_clear_apply_access_defermentno sensitive capability
  • trackly_contacts_at_companyno sensitive capability
  • trackly_create_apply_batchno sensitive capability
  • trackly_defer_apply_accessno sensitive capability
  • trackly_diagnose_local_pathno sensitive capability
  • trackly_get_active_apply_batchno sensitive capability
  • trackly_get_active_apply_executionno sensitive capability
  • trackly_get_application_profileno sensitive capability
  • trackly_get_apply_batchno sensitive capability
  • trackly_get_apply_evidenceno sensitive capability
  • trackly_get_apply_executionno sensitive capability
  • trackly_get_apply_queueno sensitive capability
  • trackly_get_company_workspaceno sensitive capability
  • trackly_get_jobno sensitive capability
  • trackly_get_job_briefno sensitive capability
  • trackly_get_preferencesno sensitive capability
  • trackly_get_profile_onboardingno sensitive capability
  • trackly_get_statsno sensitive capability
  • trackly_lint_application_textno sensitive capability
  • trackly_list_apply_access_defermentsno sensitive capability
  • trackly_list_apply_review_handoffsno sensitive capability
  • trackly_list_companiesno sensitive capability
  • trackly_list_recoverable_apply_executionsno sensitive capability
  • trackly_record_application_outcomeno sensitive capability
  • trackly_record_application_outcomesno sensitive capability
  • trackly_record_apply_execution_dispositionsno sensitive capability
  • trackly_record_apply_submission_evidenceno sensitive capability
  • trackly_record_apply_surface_evidenceno sensitive capability
  • trackly_recover_exact_apply_membersno sensitive capability
  • trackly_report_apply_observationno sensitive capability
  • trackly_report_apply_observationsno sensitive capability
  • trackly_request_companyno sensitive capability
  • trackly_resume_parked_apply_memberno sensitive capability
  • trackly_search_companiesno sensitive capability
  • trackly_search_jobsno sensitive capability
  • trackly_start_apply_executionno sensitive capability
  • trackly_start_apply_runno sensitive capability
  • trackly_stop_apply_executionno sensitive capability
  • trackly_update_application_profileno sensitive capability
  • trackly_update_experience_limitsno sensitive capability
  • trackly_update_statusno sensitive capability
  • trackly_validate_apply_resume_uploadno sensitive capability
  • trackly_validate_apply_tab_keep_setno sensitive capability
  • trackly_verify_prepared_resumeno sensitive capability

What this scan could not see

Versions 10

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.18.1 latest A 94/100 3 1.13.0 2026-09-07
v0.18.0 A 94/100 3 1.13.0 2026-09-06
v0.17.1 A 94/100 3 1.13.0 2026-09-05
v0.17.0 A 94/100 3 1.13.0 2026-08-27
v0.16.0 A 94/100 3 1.12.1 2026-08-21
Show 5 more versions ↓
v0.15.0 A 94/100 3 1.12.1 2026-08-18
v0.14.2 A 94/100 3 1.12.1 2026-08-17
v0.14.1 A 94/100 3 1.12.1 2026-08-16
v0.13.4 A 94/100 3 1.12.1 2026-08-13
v0.13.3 A 94/100 3 1.12.1 2026-08-12

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/trackly-cli/badge.svg)](https://mcptrustchecker.com/registry/trackly-cli)
HTML
<a href="https://mcptrustchecker.com/registry/trackly-cli"><img src="https://mcptrustchecker.com/registry/trackly-cli/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/trackly-cli/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan trackly-cli --online

Use the free API → How scoring works

More in Web, Search & Scraping