dev.workers.cybermax-tools.cybermax/hireheat-api

Est-ce que dev.workers.cybermax-tools.cybermax/hireheat-api est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.workers.cybermax-tools.cybermax/hireheat-api » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• company_jobs≈ 490 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Maximum jobs to return, 1-500 (default 100)
  • remote · boolean · optionnel
    true = remote roles only (default false: all roles)
  • company · string · requis
    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 · optionnel
    Optional job-title keywords; a job matches if its title contains any of them

  Exemple d'appel

  {"name": "company_jobs", "arguments": {"company": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• hiring_signals≈ 450 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • company · string · requis
    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 · optionnel
    Optional job-title keywords; only jobs whose title contains any of them are counted

  Exemple d'appel

  {"name": "hiring_signals", "arguments": {"company": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://hireheat-api.cybermaxtools.com/mcp?via=mcp-registry