Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Trackly CLI

NPM · TRACKLY-CLI · SCANNED SEP 20

Job tracking CLI + MCP server for AI agents. 99K+ jobs, 775+ companies.

Available components

0 this week 77 Trust /100

Deprecated

This server is marked deprecated in the MCP registry.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 592 tokens (~59/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Trackly CLI MCP server?

Trackly CLI runs locally as an npm package, launched with npx -y trackly-cli. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · trackly-cli

# add to Claude Code
claude mcp add kevinastuhuaman-trackly -- npx -y trackly-cli
// .cursor/mcp.json
{
  "mcpServers": {
    "kevinastuhuaman-trackly": {
      "command": "npx",
      "args": [
        "-y",
        "trackly-cli"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "kevinastuhuaman-trackly": {
      "command": "npx",
      "args": [
        "-y",
        "trackly-cli"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add kevinastuhuaman-trackly -- npx -y trackly-cli
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kevinastuhuaman-trackly": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "trackly-cli"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add kevinastuhuaman-trackly --command npx --arg -y --arg trackly-cli
# ~/.hermes/config.yaml
mcp_servers:
  kevinastuhuaman-trackly:
    command: "npx"
    args: ["-y", "trackly-cli"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "kevinastuhuaman-trackly": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "trackly-cli"
      ]
    }
  }
}
# add to Vellum
assistant mcp add kevinastuhuaman-trackly -t stdio -c npx -a -y trackly-cli
// mcp.json
{
  "mcpServers": {
    "kevinastuhuaman-trackly": {
      "command": "npx",
      "args": [
        "-y",
        "trackly-cli"
      ]
    }
  }
}
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.

  • 20 Sept 26 +1

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

  • 19 Sept 26 −4
    • Security disclosure: pass → unverified functional
    • Stability: pass → 0.80 functional
  • 18 Sept 26 +1
    • Stability: 0.97 → pass security
  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 +1
    • Stability: 0.97 → pass security
  • 9 Sept 26 +1

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

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 20 Sept 2026 · Analysed npm/trackly-cli@0.1.10

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~592 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
trackly_ask ~61

Natural language job search. Describe what you are looking for and the AI parses it into structured filters. Limited to 20 queries per day.

NameTypeReqDescription
querystringyesNatural language search query, e.g. "PM jobs at fintech companies in SF"

No output schema declared.

No examples provided.

trackly_contacts_at_company ~57

Search contacts at a specific company. Returns matching contacts with name, title, email, and status.

NameTypeReqDescription
companystringyesCompany name to search contacts for
limitnumberMax results (default 20)

No output schema declared.

No examples provided.

trackly_get_company_workspace ~45

Get the full workspace view for a company: active jobs, contacts, hiring managers, coverage gap, and campaign status.

NameTypeReqDescription
companyIdnumberyesCompany ID

No output schema declared.

No examples provided.

trackly_get_job ~31

Get full details for a specific job posting including description.

NameTypeReqDescription
idnumberyesJob posting ID

No output schema declared.

No examples provided.

trackly_get_job_brief ~46

Get a network brief for a specific job. Returns company signal, recommended motion, top contact, and suggested actions.

NameTypeReqDescription
jobIdnumberyesJob posting ID

No output schema declared.

No examples provided.

trackly_get_stats ~24

Get job tracker metrics: total jobs, companies, application status counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trackly_list_companies ~39

List all tracked companies with their active job counts.

NameTypeReqDescription
limitnumberMax results
offsetnumberPagination offset

No output schema declared.

No examples provided.

trackly_search_companies ~45

Semantic search for companies by name, domain, or keywords.

NameTypeReqDescription
limitnumberMax results (default 10)
querystringyesSearch query

No output schema declared.

No examples provided.

trackly_search_jobs ~202

Search and filter job postings. Returns matching jobs with title, company, location, modality. Use companyId to filter jobs at a specific company (get companyId from trackly_search_companies first).

NameTypeReqDescription
companyIdnumberFilter jobs by company ID (get from trackly_search_companies)
functionstringJob function filter (matches DB column). Common: product, engineering, design, data, marketing, sales, operations, other
keywordsstringKeyword search in title/description
limitnumberMax results (default 20, max 50)
locationstringLocation filter (city or state)
modalitystringWork modality: remote, hybrid, onsite
offsetnumberPagination offset
sortstringSort order: newest, oldest, company
statusstringApplication status: new, saved, applied, dismissed

No output schema declared.

No examples provided.

trackly_update_status ~42

Update a job application status (apply, save, or dismiss).

NameTypeReqDescription
actionstringyesStatus action
idnumberyesJob posting ID

No output schema declared.

No examples provided.

Common questions

What is the Trackly CLI MCP server?

Trackly CLI is an MCP server listed in the public MCP registry as io.github.kevinastuhuaman/trackly. Job tracking CLI + MCP server for AI agents. 99K+ jobs, 775+ companies. This page covers its npm package (trackly-cli).

Is the Trackly CLI MCP server safe to use?

Trackly CLI scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Trackly CLI MCP server expose?

Trackly CLI exposes 10 tools: trackly_search_jobs, trackly_get_job, trackly_search_companies, trackly_list_companies, trackly_get_stats, and 5 more. Their descriptions and schemas cost roughly 592 tokens of context every time the server is loaded.

Is the Trackly CLI MCP server still maintained?

Trackly CLI is marked deprecated in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Trackly CLI MCP server under?

Trackly CLI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.