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.

io.github.starnikovoleg/hiringindex-mcp

NPM · HIRINGINDEX-MCP

Search live job postings, aggregate any market slice, and see how long each listing has been open.

Available components

0 this week 90 Trust /100

Last scanned (3 hours ago)

Scores higher than 93% of npm servers

Category Search and Retrieval

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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to starnikov-oleg-org/hiringindex-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 54 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1292 tokens (~323/item across 4 items; 4 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
  • 25 Oct 26 0
    • Stability: 0.97 → pass security
  • 24 Oct 26 0
    • Stability: pass → 0.97 functional
  • 18 Oct 26 0
    • Stability: 0.97 → pass security
  • 17 Oct 26 +1

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

  • 15 Oct 26 +6
    • Source repository: unverified → pass ▲ security
  • 14 Oct 26 −5
    • Provenance: pass → unverified ▼ security
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 5 Nov 2026 · Analysed npm/hiringindex-mcp@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo starnikov-oleg-org/hiringindex-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/starnikov-oleg-org/hiringindex-mcp/.github/workflows/publish.yml@refs/tags/v0.1.1
Rekor log index 2794081840
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7a7a2be9aa1ffb38384c42ab3acf316c43095c5d7cbbb5f6bea6ca0619c69721b7ff26e0daed4c19318d48fdf906031b987bddbb1b3ff2790871c848e

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~1,239 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
get_job ~46

Full detail for a single posting by its id, including the description and the application link.

NameTypeReqDescription
formatstring––
idstringyesPosting id returned by search_jobs.

No output schema declared.

No examples provided.

job_market_insights ~380

Counts, salary percentiles by currency, remote share, top employers, seniority and employment-type mix, city and source split for any slice of postings. Accepts the same filters as search_jobs. Use this instead of paging through results when the question is about the market rather than about individual roles.

NameTypeReqDescription
board_handlestring–Restrict to one ATS board by its handle, exactly as the `handle` field of a posting reports it, e.g. "EndeavorITSolution" (SmartRecruiters) or "walmart:wd504:WalmartExternal" (Workday). The precise w…
citystring–City name as employers write it, e.g. "Berlin", "New York", "Bengaluru".
companystring–Restrict to one employer by name.
countrystring–Country as ISO 3166-1 alpha-2 code ("US", "DE") or an English name ("Germany").
formatstring––
keywordsarray–Terms mentioned anywhere in the posting — title or description — e.g. ["Kubernetes"]. Any keyword matches. Use titles for the role itself; keywords for a tool, skill or technology the posting talks a…
posted_within_daysinteger–Only postings published in the last N days.
salary_maxnumber–Highest advertised salary to include.
salary_minnumber–Lowest advertised salary to include. Only postings that disclose a salary match.
titlesarray–Job titles to match, e.g. ["Data Engineer"]. Terms shorter than 3 characters are rejected by the index.
work_arrangementarray–Filter by how the work is done. Hybrid is not a separate filter upstream.

No output schema declared.

No examples provided.

posting_age_report ~378

Age profile of a slice of postings: median days since publication, share posted in the last week, and share still open after sixty days. A listing that has been open for months is the most commonly cited sign that a role is not being actively filled — this reports the numbers rather than guessing.

NameTypeReqDescription
board_handlestring–Restrict to one ATS board by its handle, exactly as the `handle` field of a posting reports it, e.g. "EndeavorITSolution" (SmartRecruiters) or "walmart:wd504:WalmartExternal" (Workday). The precise w…
citystring–City name as employers write it, e.g. "Berlin", "New York", "Bengaluru".
companystring–Restrict to one employer by name.
countrystring–Country as ISO 3166-1 alpha-2 code ("US", "DE") or an English name ("Germany").
formatstring––
keywordsarray–Terms mentioned anywhere in the posting — title or description — e.g. ["Kubernetes"]. Any keyword matches. Use titles for the role itself; keywords for a tool, skill or technology the posting talks a…
posted_within_daysinteger–Only postings published in the last N days.
salary_maxnumber–Highest advertised salary to include.
salary_minnumber–Lowest advertised salary to include. Only postings that disclose a salary match.
titlesarray–Job titles to match, e.g. ["Data Engineer"]. Terms shorter than 3 characters are rejected by the index.
work_arrangementarray–Filter by how the work is done. Hybrid is not a separate filter upstream.

No output schema declared.

No examples provided.

search_jobs ~435

Search live job postings read directly from ten applicant tracking systems (Workday, SmartRecruiters, Greenhouse, Workable, Lever, Ashby, Recruitee, Teamtailor, Breezy, Personio). Returns title, employer where the ATS publishes it, location, employment type, advertised salary where disclosed, posting date and the employer's own apply link where the source carries one.

NameTypeReqDescription
board_handlestring–Restrict to one ATS board by its handle, exactly as the `handle` field of a posting reports it, e.g. "EndeavorITSolution" (SmartRecruiters) or "walmart:wd504:WalmartExternal" (Workday). The precise w…
citystring–City name as employers write it, e.g. "Berlin", "New York", "Bengaluru".
companystring–Restrict to one employer by name.
countrystring–Country as ISO 3166-1 alpha-2 code ("US", "DE") or an English name ("Germany").
formatstring–markdown (default) or raw json.
keywordsarray–Terms mentioned anywhere in the posting — title or description — e.g. ["Kubernetes"]. Any keyword matches. Use titles for the role itself; keywords for a tool, skill or technology the posting talks a…
limitinteger–Postings per page, up to 100.
pageinteger–Result page, starts at 1.
posted_within_daysinteger–Only postings published in the last N days.
salary_maxnumber–Highest advertised salary to include.
salary_minnumber–Lowest advertised salary to include. Only postings that disclose a salary match.
titlesarray–Job titles to match, e.g. ["Data Engineer"]. Terms shorter than 3 characters are rejected by the index.
work_arrangementarray–Filter by how the work is done. Hybrid is not a separate filter upstream.

No output schema declared.

No examples provided.

Install

How do I install the io.github.starnikovoleg/hiringindex-mcp server?

io.github.starnikovoleg/hiringindex-mcp runs locally as an npm package, launched with npx -y hiringindex-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · hiringindex-mcp

# add to Claude Code
claude mcp add starnikovoleg-hiringindex-mcp -- npx -y hiringindex-mcp
Common questions

What is the io.github.starnikovoleg/hiringindex-mcp server?

io.github.starnikovoleg/hiringindex-mcp is listed in the public MCP registry as io.github.starnikovoleg/hiringindex-mcp. Search live job postings, aggregate any market slice, and see how long each listing has been open. This page covers its npm package (hiringindex-mcp).

Is the io.github.starnikovoleg/hiringindex-mcp server safe to use?

io.github.starnikovoleg/hiringindex-mcp scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.starnikovoleg/hiringindex-mcp server expose?

io.github.starnikovoleg/hiringindex-mcp exposes 4 tools: search_jobs, job_market_insights, posting_age_report, get_job. Their descriptions and schemas cost roughly 1,239 tokens of context every time the server is loaded.

Is the io.github.starnikovoleg/hiringindex-mcp server still maintained?

io.github.starnikovoleg/hiringindex-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.starnikovoleg/hiringindex-mcp server under?

io.github.starnikovoleg/hiringindex-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.