# HireHeat (remote · hireheat-api.cybermaxtools.com)

Company hiring signals + open jobs from Greenhouse, Lever, Ashby boards, API + MCP. 20 free/day.

- Trust score: 75/100 (medium)
- Change this week: +13
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `hireheat-api.cybermaxtools.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-hireheat-api/hireheat-api-2.md), [page](https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-hireheat-api/hireheat-api-2)

## Channel facts

- Endpoint: `https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-22.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 746 tokens (~373/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.

## Install

### How do I install the HireHeat MCP server?

HireHeat is a hosted endpoint at https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry, so there is nothing to install locally. 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 --transport http dev-workers-cybermax-tools-cybermax-hireheat-api 'https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-cybermax-tools-cybermax-hireheat-api": {
      "url": "https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-cybermax-tools-cybermax-hireheat-api": {
      "type": "http",
      "url": "https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-cybermax-tools-cybermax-hireheat-api]
url = "https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-cybermax-tools-cybermax-hireheat-api": {
      "type": "remote",
      "url": "https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-cybermax-tools-cybermax-hireheat-api --url 'https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-cybermax-tools-cybermax-hireheat-api:
    url: "https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-cybermax-tools-cybermax-hireheat-api": {
      "Transport": "http",
      "Url": "https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-cybermax-tools-cybermax-hireheat-api -t streamable-http -u 'https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-cybermax-tools-cybermax-hireheat-api": {
      "type": "http",
      "url": "https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-22 (score 75, +1)

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

### 2026-10-20 (score 74, +1)

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

### 2026-10-17 (score 73, +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-10-16 (score 72, +10)

- [security improvement] Transport: fail → pass

### 2026-10-15 (score 62, −9)

- [security regression] Transport: pass → fail

### 2026-10-13 (score 71, +1)

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

### 2026-10-12 (score 70, −1)

- [security] Tool “company_jobs” rewrote its description, which is the text the model reads
- [security] Tool “hiring_signals” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 185 → 373
- [functional] Schema quality: good → excellent
- [cosmetic] “hiring_signals” reworded the description of “company”
- [cosmetic] “hiring_signals” reworded the description of “keywords”
- [cosmetic] “company_jobs” reworded the description of “remote”
- [cosmetic] “company_jobs” reworded the description of “keywords”
- [cosmetic] “company_jobs” reworded the description of “company”

### 2026-10-10 (score 71)

First indexed and scored.

## MCP tools (2)

### `hiring_signals` (~314 tokens)

Company hiring signals

Hiring SUMMARY for one company, read live from its public Greenhouse, Lever, Ashby, SmartRecruiters and Recruitee job board. Use this when you need to know whether a company is hiring, how fast and in which teams: sales triggers, account research, investor or competitor signals. Do not use it to read the postings themselves (use company_jobs). Input: company (website domain, website URL or job-board URL); optional keywords narrow the counts to matching job titles. Returns results[0] with found, the job board detected (ATS and URL), signals (open roles, roles posted in the last 7 and 30 days, hiring level, counts by function and seniority, top departments and locations, remote share, the 10 newest jobs), a one-line summary, checkedAt and cached. found=false means no supported public board was found (for example a Workday-only company). Limits: one company per call; answers cached for 1 hour; 20 free companies a day per IP without a key, more with a paid key in the x-api-key header. Read-only: nothing is stored or sent.

Input parameters:

- `company` (string, required): The company to check, one per call: its website domain, website URL, or a job-board URL (boards.greenhouse.io/acme, jobs.lever.co/acme, jobs.ashbyhq.com/acme)
- `keywords` (array): Optional job-title keywords; only jobs whose title contains any of them are counted

### `company_jobs` (~347 tokens)

Open jobs at a company

Full LIST of open jobs at one company (up to 500), newest first, read live from its public Greenhouse, Lever, Ashby, SmartRecruiters and Recruitee job board. Use this when you need the actual postings: to read, filter or export them, find a role to apply to, or pull salaries. For counts and hiring trends use hiring_signals instead. Input: company (website domain, website URL or job-board URL); optional keywords (title contains any), remote (true = remote only) and limit (1-500, default 100). Returns company, domain, found, boards, summary, count, totalMatching and results[]: one job each with title, department, location, remote flag, posted date, apply URL, salary when the employer publishes it, function and seniority. found=false (empty results) means no supported public board was found. Limits: one company per call; answers cached for 1 hour; 20 free companies a day per IP without a key, more with a paid key in the x-api-key header. Read-only: nothing is stored or sent.

Input parameters:

- `company` (string, required): The company, one per call: its website domain, website URL, or a job-board URL (boards.greenhouse.io/acme, jobs.lever.co/acme, jobs.ashbyhq.com/acme)
- `keywords` (array): Optional job-title keywords; a job matches if its title contains any of them
- `limit` (integer): Maximum jobs to return, 1-500 (default 100)
- `remote` (boolean): true = remote roles only (default false: all roles)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-hireheat-api/hireheat-api-2#diagnostics

## Score history

- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 73
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 72
- 2026-10-15: 62
- 2026-10-14: 71
- 2026-10-13: 71
- 2026-10-12: 70
- 2026-10-10: 71

## Common questions

### What is the HireHeat MCP server?

HireHeat is an MCP server listed in the public MCP registry as dev.workers.cybermax-tools.cybermax/hireheat-api. Company hiring signals + open jobs from Greenhouse, Lever, Ashby boards, API + MCP. 20 free/day. This page covers its hosted endpoint (https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry).

### Is the HireHeat MCP server safe to use?

HireHeat scores 75 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 HireHeat MCP server expose?

HireHeat exposes 2 tools: hiring_signals, company_jobs. Their descriptions and schemas cost roughly 661 tokens of context every time the server is loaded.

### Does the HireHeat MCP server require authentication?

No. We connected to HireHeat without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the HireHeat MCP server still maintained?

HireHeat is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry
- Repository: https://gitlab.com/CyberMax.tools/agent-tools
- Website: https://cybermaxtools.com/store/hireheat-api/?s=mcp-registry-hireheat-api
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-hireheat-api/hireheat-api-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-hireheat-api/hireheat-api-2.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-cybermax-tools-cybermax-hireheat-api/hireheat-api-2