# io.github.CloudCorpRecords/hiringpulse (oci · ghcr.io/cloudcorprecords/hiringpulse)

Is a company really hiring? Job-board truth: fresh and quiet boards, changes, market stats.

- Trust score: 44/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/hiringpulse`: 73/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-hiringpulse/reneturcios-hiringpulse.md), [page](https://verifymcp.io/servers/cloudcorprecords-hiringpulse/reneturcios-hiringpulse)
- oci · `ghcr.io/cloudcorprecords/hiringpulse`: 44/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-hiringpulse/ghcr-io-cloudcorprecords-hiringpulse.md), [page](https://verifymcp.io/servers/cloudcorprecords-hiringpulse/ghcr-io-cloudcorprecords-hiringpulse)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/hiringpulse`
- Version: `0.1.0`
- 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-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 682 tokens (~113/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/hiringpulse MCP server?

io.github.CloudCorpRecords/hiringpulse runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/hiringpulse:0.1.0 mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-hiringpulse -- docker run --rm -i ghcr.io/cloudcorprecords/hiringpulse:0.1.0 mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-hiringpulse": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/hiringpulse:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-hiringpulse": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/hiringpulse:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-hiringpulse -- docker run --rm -i ghcr.io/cloudcorprecords/hiringpulse:0.1.0 mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-hiringpulse": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/hiringpulse:0.1.0",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-hiringpulse:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/hiringpulse:0.1.0", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-hiringpulse": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/hiringpulse:0.1.0",
        "mcp"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-hiringpulse": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/hiringpulse:0.1.0",
        "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-11-21 (score 44, +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-11-19 (score 43, +1)

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

### 2026-11-17 (score 42, +1)

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

### 2026-11-16 (score 41)

First indexed and scored.

## MCP tools (6)

### `search_jobs` (~208 tokens)

Search open job postings read directly from employers' own Greenhouse, Ashby and Lever boards. Unlike a job board, every result carries the employer's real publish date and age in days, so you can tell a role posted this morning from one that has been open two years.

Input parameters:

- `department` (string): Function, e.g. 'Engineering', 'Sales'
- `limit` (integer): Max results (default 25)
- `location` (string): Any part of the location string, e.g. 'Berlin', 'California'
- `max_age_days` (integer): Only roles posted within this many days
- `min_age_days` (integer): Only roles OLDER than this many days -- use to hunt stale listings
- `query` (string): Words in the job title, e.g. 'staff backend engineer'
- `remote` (boolean): Only roles flagged remote
- `technology` (string): Technology named in the posting, e.g. 'Python', 'Kubernetes'

### `check_company` (~106 tokens)

Ask whether a company is ACTUALLY hiring, not just whether it has jobs listed. Returns a verdict on the board -- actively_hiring, still_open, gone_quiet or likely_abandoned -- with the age of the newest posting, the median role age, and how many reqs have sat open over 90 days and over a year. This is the check that tells you whether an application or a sales approach is worth the time.

Input parameters:

- `company` (string, required): Company name

### `find_quiet_boards` (~73 tokens)

Companies still advertising open roles while having posted nothing new in over six months. Strong evidence of a board nobody tidied up after the hiring finished. Useful for striking dead accounts off a prospect list, or for avoiding applications that will never be read.

Input parameters:

- `limit` (integer): Maximum number of boards to return.

### `find_fresh_boards` (~78 tokens)

Companies where EVERY currently open role was posted in the last 30 days -- no backlog of applicants ahead of you, and usually a team that just started hiring. For sales, a company that just opened its first roles in a function is one whose budget has recently moved.

Input parameters:

- `limit` (integer): Maximum number of boards to return.

### `whats_changed` (~151 tokens)

What actually MOVED, on a list of companies you name or across the whole record. Answers the question a person with a book of accounts has every morning: which of mine changed, and is anyone suddenly ramping? Returns NET movement, because a company that opened 342 roles and closed 317 is churning and one that opened 261 and closed 41 is hiring -- and flags a board whose VERDICT flipped, which is a budget unfreezing and the strongest signal in this data.

Input parameters:

- `companies` (array): Company names to watch. Omit for the whole market.
- `days` (integer): Window, default 7
- `limit` (integer): Maximum number of companies to return.

### `hiring_stats` (~66 tokens)

Market-level hiring numbers measured this morning across every board we read: employers hiring, open roles, how many went up in the last 24 hours, how many have been open over 90 days and over a year, how many boards have gone quiet, and the most in-demand technologies.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-hiringpulse/ghcr-io-cloudcorprecords-hiringpulse#diagnostics

## Score history

- 2026-11-21: 44
- 2026-11-20: 43
- 2026-11-19: 43
- 2026-11-18: 42
- 2026-11-17: 42
- 2026-11-16: 41

## Common questions

### What is the io.github.CloudCorpRecords/hiringpulse MCP server?

io.github.CloudCorpRecords/hiringpulse is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/hiringpulse. Is a company really hiring? Job-board truth: fresh and quiet boards, changes, market stats. This page covers its container image (ghcr.io/cloudcorprecords/hiringpulse).

### Is the io.github.CloudCorpRecords/hiringpulse MCP server safe to use?

io.github.CloudCorpRecords/hiringpulse scores 44 out of 100 on VerifyMCP. 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.CloudCorpRecords/hiringpulse MCP server expose?

io.github.CloudCorpRecords/hiringpulse exposes 6 tools: search_jobs, check_company, find_quiet_boards, find_fresh_boards, whats_changed, hiring_stats. Their descriptions and schemas cost roughly 682 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/hiringpulse MCP server still maintained?

io.github.CloudCorpRecords/hiringpulse is still listed as active in the MCP registry. We last reached this channel on 21 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.CloudCorpRecords/hiringpulse MCP server under?

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

### What did VerifyMCP test on the io.github.CloudCorpRecords/hiringpulse MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/hiringpulse, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/hiringpulse: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/hiringpulse
- Repository: https://github.com/CloudCorpRecords/hiringpulse
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-hiringpulse/ghcr-io-cloudcorprecords-hiringpulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-hiringpulse/ghcr-io-cloudcorprecords-hiringpulse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-hiringpulse/ghcr-io-cloudcorprecords-hiringpulse.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-hiringpulse/ghcr-io-cloudcorprecords-hiringpulse
