# 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.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `hiringindex-mcp`: 81/100 (this document), [markdown](https://verifymcp.io/servers/starnikovoleg-hiringindex-mcp/hiringindex-mcp.md), [page](https://verifymcp.io/servers/starnikovoleg-hiringindex-mcp/hiringindex-mcp)

## Channel facts

- Registry: `npm`
- Package: `hiringindex-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to starnikov-oleg-org/hiringindex-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add starnikovoleg-hiringindex-mcp -- npx -y hiringindex-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "starnikovoleg-hiringindex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hiringindex-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "starnikovoleg-hiringindex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hiringindex-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add starnikovoleg-hiringindex-mcp -- npx -y hiringindex-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "starnikovoleg-hiringindex-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "hiringindex-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add starnikovoleg-hiringindex-mcp --command npx --arg -y --arg hiringindex-mcp
```

### Hermes

```yaml
mcp_servers:
  starnikovoleg-hiringindex-mcp:
    command: "npx"
    args: ["-y", "hiringindex-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "starnikovoleg-hiringindex-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "hiringindex-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add starnikovoleg-hiringindex-mcp -t stdio -c npx -a -y hiringindex-mcp
```

### Other

```json
{
  "mcpServers": {
    "starnikovoleg-hiringindex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "hiringindex-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 81, +1)

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

### 2026-09-18 (score 80, +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.

### 2026-09-15 (score 79, +1)

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

### 2026-09-13 (score 78, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-09-12 (score 77, +48)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Source repository: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-09-11 (score 29, −22)

- [security regression] Tool safety: pass → unverified
- [security regression] Source repository: pass → fail
- [security improvement] Malware scan: unverified → pass
- [security improvement] Provenance: fail → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] The attested source repository moved: starnikov-oleg-org/hiringindex-mcp
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-09-10 (score 51)

First indexed and scored.

## MCP tools (4)

### `search_jobs` (~435 tokens)

Search job postings

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.

Input parameters:

- `board_handle` (string): 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…
- `city` (string): City name as employers write it, e.g. "Berlin", "New York", "Bengaluru".
- `company` (string): Restrict to one employer by name.
- `country` (string): Country as ISO 3166-1 alpha-2 code ("US", "DE") or an English name ("Germany").
- `format` (string): markdown (default) or raw json.
- `keywords` (array): 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…
- `limit` (integer): Postings per page, up to 100.
- `page` (integer): Result page, starts at 1.
- `posted_within_days` (integer): Only postings published in the last N days.
- `salary_max` (number): Highest advertised salary to include.
- `salary_min` (number): Lowest advertised salary to include. Only postings that disclose a salary match.
- `titles` (array): Job titles to match, e.g. ["Data Engineer"]. Terms shorter than 3 characters are rejected by the index.
- `work_arrangement` (array): Filter by how the work is done. Hybrid is not a separate filter upstream.

### `job_market_insights` (~380 tokens)

Aggregate a slice of the job market

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.

Input parameters:

- `board_handle` (string): 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…
- `city` (string): City name as employers write it, e.g. "Berlin", "New York", "Bengaluru".
- `company` (string): Restrict to one employer by name.
- `country` (string): Country as ISO 3166-1 alpha-2 code ("US", "DE") or an English name ("Germany").
- `format` (string)
- `keywords` (array): 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_days` (integer): Only postings published in the last N days.
- `salary_max` (number): Highest advertised salary to include.
- `salary_min` (number): Lowest advertised salary to include. Only postings that disclose a salary match.
- `titles` (array): Job titles to match, e.g. ["Data Engineer"]. Terms shorter than 3 characters are rejected by the index.
- `work_arrangement` (array): Filter by how the work is done. Hybrid is not a separate filter upstream.

### `posting_age_report` (~378 tokens)

How long these postings have been open

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.

Input parameters:

- `board_handle` (string): 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…
- `city` (string): City name as employers write it, e.g. "Berlin", "New York", "Bengaluru".
- `company` (string): Restrict to one employer by name.
- `country` (string): Country as ISO 3166-1 alpha-2 code ("US", "DE") or an English name ("Germany").
- `format` (string)
- `keywords` (array): 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_days` (integer): Only postings published in the last N days.
- `salary_max` (number): Highest advertised salary to include.
- `salary_min` (number): Lowest advertised salary to include. Only postings that disclose a salary match.
- `titles` (array): Job titles to match, e.g. ["Data Engineer"]. Terms shorter than 3 characters are rejected by the index.
- `work_arrangement` (array): Filter by how the work is done. Hybrid is not a separate filter upstream.

### `get_job` (~46 tokens)

Fetch one posting

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

Input parameters:

- `format` (string)
- `id` (string, required): Posting id returned by search_jobs.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/starnikovoleg-hiringindex-mcp/hiringindex-mcp#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 29
- 2026-09-10: 51

## 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 81 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. 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 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 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.

## Links

- npm package: https://www.npmjs.com/package/hiringindex-mcp
- Socket report: https://socket.dev/npm/package/hiringindex-mcp
- Repository: https://github.com/starnikov-oleg-org/hiringindex-mcp
- Changelog RSS feed: https://verifymcp.io/servers/starnikovoleg-hiringindex-mcp/hiringindex-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/starnikovoleg-hiringindex-mcp/hiringindex-mcp.json
- HTML version of this page: https://verifymcp.io/servers/starnikovoleg-hiringindex-mcp/hiringindex-mcp