mcpbeat Sign in

HireHeat: Hiring Signals & Company Job Postings by Domain MCP Server

answering

HireHeat: Hiring Signals & Company Job Postings by Domain is answering right now. Last checked 10 min ago.

HireHeat: who's hiring? Open and new roles per company domain by function, seniority, location.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 16 days of history · worst day 98%
16 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
321 ms
Response time
average over 24h
API key
Access
streamable-http

HireHeat: Hiring Signals & Company Job Postings by Domain missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

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 hiring-signals --transport http https://mcp.apify.com?tools=cybermax/hiring-signals
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "hiring-signals": {
      "url": "https://mcp.apify.com?tools=cybermax/hiring-signals"
    }
  }
}
~/.codex/config.toml
[mcp_servers.hiring-signals]
url = "https://mcp.apify.com?tools=cybermax/hiring-signals"
.cursor/mcp.json
{
  "mcpServers": {
    "hiring-signals": {
      "url": "https://mcp.apify.com?tools=cybermax/hiring-signals"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "hiring-signals": {
      "url": "https://mcp.apify.com?tools=cybermax/hiring-signals"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.apify.com?tools=cybermax/hiring-signals streamable-http needs key 298 ms 10 min ago

Alternatives to HireHeat: Hiring Signals & Company Job Postings by Domain

same job, measured the same way
HireHeat: Hiring Signals & Company Job Postings by Domain
by shawmena-dotcom

HireHeat: who's hiring? Open and new roles per company domain by function, seniority, location.

answering
R
Remote Rocketship jobs
by remoterocketship

Search remote jobs from company career pages by title, location, seniority, salary, and tech stack.

1 tools answering
Jobily Jobs
by jobily

Search Greek job listings on Jobily.gr by role, location, sector or company. Anonymous, read-only.

5 tools answering
Reqbeat Hiring Signals
by reqbeat

Find companies hiring for a role and geo, qualify them, and watch them for changes.

15 tools answering
HasData Indeed
by hasdata

Indeed job listings by keyword and location, and full postings, as structured JSON.

266 installs/wk 2 tools answering
Location & Demand Intelligence
by timzinin-api

Pay-per-call where-and-when-to-operate signals from official local statistics.

7 tools answering
Google Jobs API
by saulius876-lgtm

Google Jobs listings by keyword and location: title, company, salary, source board, apply links.

answering
NordicMCP — Weather
by nordicmcp

Hosted Weather MCP server (Open-Meteo): current, forecast, and historical weather by location.

answering

HireHeat: Hiring Signals & Company Job Postings by Domain — questions

Answers built from our own checks of this server.

Why is there no tool list for HireHeat: Hiring Signals & Company Job Postings by Domain?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is HireHeat: Hiring Signals & Company Job Postings by Domain working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 321 ms. The bar chart above shows every period we have measured.
Is HireHeat: Hiring Signals & Company Job Postings by Domain still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect HireHeat: Hiring Signals & Company Job Postings by Domain?
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. You will need your own key: it refuses anonymous clients.
Does HireHeat: Hiring Signals & Company Job Postings by Domain need an API key?
Yes. Every time we knock, HireHeat: Hiring Signals & Company Job Postings by Domain answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is HireHeat: Hiring Signals & Company Job Postings by Domain?
It answers our handshake in 321 ms on average, which is faster than 44% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.