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.CloudCorpRecords/hiringpulse

OCI · GHCR.IO/CLOUDCORPRECORDS/HIRINGPULSE · 2 COMPONENTS

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

44 Trust /100

Last scanned (13 hours ago)

Scores higher than 45% of OCI servers

Category CRM and Sales

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 Security0
  • 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.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 682 tokens (~113/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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

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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 16 Nov 26 41

    First indexed and scored.

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 21 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/hiringpulse@0.1.0

Provenance No attestation

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

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 6 exposed · ~682 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
check_company ~106

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.

NameTypeReqDescription
companystringyesCompany name

No output schema declared.

No examples provided.

find_fresh_boards ~78

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.

NameTypeReqDescription
limitinteger–Maximum number of boards to return.

No output schema declared.

No examples provided.

find_quiet_boards ~73

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.

NameTypeReqDescription
limitinteger–Maximum number of boards to return.

No output schema declared.

No examples provided.

hiring_stats ~66

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_jobs ~208

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.

NameTypeReqDescription
departmentstring–Function, e.g. 'Engineering', 'Sales'
limitinteger–Max results (default 25)
locationstring–Any part of the location string, e.g. 'Berlin', 'California'
max_age_daysinteger–Only roles posted within this many days
min_age_daysinteger–Only roles OLDER than this many days -- use to hunt stale listings
querystring–Words in the job title, e.g. 'staff backend engineer'
remoteboolean–Only roles flagged remote
technologystring–Technology named in the posting, e.g. 'Python', 'Kubernetes'

No output schema declared.

No examples provided.

whats_changed ~151

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.

NameTypeReqDescription
companiesarray–Company names to watch. Omit for the whole market.
daysinteger–Window, default 7
limitinteger–Maximum number of companies to return.

No output schema declared.

No examples provided.

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.

oci · ghcr.io/cloudcorprecords/hiringpulse

# add to Claude Code
claude mcp add cloudcorprecords-hiringpulse -- docker run --rm -i ghcr.io/cloudcorprecords/hiringpulse:0.1.0 mcp
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.