HireHeat
REMOTE · HIREHEAT-API.CYBERMAXTOOLS.COM
Company hiring signals + open jobs from Greenhouse, Lever, Ashby boards, API + MCP. 20 free/day.
Available components
Last scanned (22 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 22 Oct 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 17 Oct 26 +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.
- 16 Oct 26 +10
- Transport: fail → pass ▲ security
- 15 Oct 26 −9
- Transport: pass → fail ▼ security
- 13 Oct 26 +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.
- 12 Oct 26 −1
- 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 security
- Schema quality: 185 → 373 ▼ functional
- Schema quality: good → excellent functional
- “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” cosmetic
- 10 Oct 26 71
First indexed and scored.
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 22 Oct 2026 · Probed https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cybermaxtools.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5b905c74dfdef1d70edcfa2e2ebe7805 |
| SANs: cybermaxtools.com, hireheat-api.cybermaxtools.com, *.hireheat-api.cybermaxtools.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hireheat-api.cybermaxtools.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cybermaxtools.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry | Verified | 200 | |
| http (plaintext) | http://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry | HTTPS enforced | 301 | https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry |
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 →
company_jobs Open jobs at a company ~347
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | 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) |
No output schema declared.
No examples provided.
hiring_signals Company hiring signals ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | 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 |
No output schema declared.
No examples provided.
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.
remote · hireheat-api.cybermaxtools.com
claude mcp add --transport http dev-workers-cybermax-tools-cybermax-hireheat-api 'https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry'
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.