mcpbeat Sign in

HireHeat MCP Server

by workers-cybermax-tools-cybermax Your server? Claim it
answering

HireHeat is answering right now. Last checked 10 min ago. It exposes 2 tools.

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

Uptime history 11 days of history
11 days agonow
100.0%
Uptime 24h
172 of 172 checks
2
Tools
read from the server
90 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 October 2026. No other catalogue keeps this.

10 Oct 2 tool descriptions were rewritten company_jobs, hiring_signals
10 Oct 2 tools changed the parameters they ask for company_jobs, hiring_signals
9 Oct 2 tool descriptions were rewritten company_jobs, hiring_signals
9 Oct a tool changed the parameters it asks for company_jobs

Nothing serious here today

Today is the operative word: we check HireHeat every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add hireheat-api --transport http https://hireheat-api.cybermax-tools.workers.dev/mcp?via=mcp-registry
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "hireheat-api": {
      "url": "https://hireheat-api.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}
~/.codex/config.toml
[mcp_servers.hireheat-api]
url = "https://hireheat-api.cybermax-tools.workers.dev/mcp?via=mcp-registry"
.cursor/mcp.json
{
  "mcpServers": {
    "hireheat-api": {
      "url": "https://hireheat-api.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "hireheat-api": {
      "url": "https://hireheat-api.cybermax-tools.workers.dev/mcp?via=mcp-registry"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

company
company_jobs
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.
hiring
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.

Endpoints

URLTransportStateLatencyChecked
https://hireheat-api.cybermax-tools.workers.dev/mcp?via=mcp-registry streamable-http answering 82 ms 10 min ago
https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry streamable-http answering 175 ms 10 min ago

Alternatives to HireHeat

same job, measured the same way
Career Page Jobs on Apify MCP
by donmangudata-ops

Open jobs from company career pages on Greenhouse, Lever, Ashby, Workday and 18 more, via Apify MCP

answering
ATS Jobs
by groundtruthtools

Open jobs read from a company's own careers system: Greenhouse, Ashby, Lever.

143 installs/wk 3 tools answering
Hiring Signals
by kiskecske24

Live job openings from Workday, Greenhouse, Lever, Ashby, Workable and Personio career sites.

answering
Company Jobs & Hiring Signals
by plainfold

Open jobs and hiring signals for any company, from its public careers page or job board.

answering
HireHeat Jobs: Career Site Job Listings from 12,000+ Companies
by cybermax-tools

HireHeat Jobs: search jobs on 12,000+ company career sites (Greenhouse, Ashby, Workable…).

answering
HireHeat Jobs: Career Site Job Listings from 12,000+ Companies
by shawmena-dotcom

HireHeat Jobs: search jobs on 12,000+ company career sites (Greenhouse, Ashby, Workable…).

answering
C
Company Signals
by lastminutedealshq

Open jobs and hiring changes per company, daily. Free keyless lookup. AI-compiled from job boards.

5 tools answering
MCP Gtm Hiring Signal Scraper
by mambabuilt

Detects GTM hiring activity from company career pages via Greenhouse, Lever, Ashby. Clay-ready.

132 installs/wk local only

HireHeat — questions

Answers built from our own checks of this server.

What can HireHeat do?
It exposes 2 tools, read directly from the server on our last check. Among them: company_jobs, hiring_signals. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is HireHeat working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 172 of 172 checks got a reply (100.0%), average response time 90 ms. The bar chart above shows every period we have measured.
How do I connect HireHeat?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does HireHeat need an API key?
No. HireHeat completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is HireHeat?
It answers our handshake in 90 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.