Ir para o conteúdo
Logo de 100hires

Servidor MCP de 100hires

Quais servidores do registro oficial de MCP são de 100hires, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-14

← Voltar para 100hires

De quem é o servidor
  • Nome no registrocom.100hires/100hiresverificado no registro MCP

O nome no registro fica sob 100hires.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-10-14
  • Estadorespondeverificado em 2026-10-14
  • Ferramentas136
  • O servidor se chama100hires-mcp-server
  • Versão do servidor1.0.6
  • Versão do protocolo2025-06-18

Em 2026-10-14 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 708 ms.

Ferramentas que oferece136 ferramentas · lido em 2026-10-14
  • hires_list_candidates

    List candidates filtered by job, stage, email, name, LinkedIn or dates. Prefer size <= 10.

  • hires_create_candidate

    Create a candidate, optionally with an application (job_id, stage_id) and resume text. Parse an attached resume yourself and pass the text via resume_text; never inline binary data.

  • hires_get_candidate

    Get a candidate with application summaries.

  • hires_update_candidate

    Update candidate fields, profile answers or resume text. For an attached resume pass the parsed text via resume_text; never inline binary data.

  • hires_delete_candidate

    Permanently delete a candidate.

  • hires_list_candidate_tags

    List a candidate's tags.

  • hires_add_candidate_tags

    Add tags to a candidate.

  • hires_remove_candidate_tag

    Remove one tag from a candidate.

  • hires_batch_add_tags

    Add tags to up to 100 candidates; returns per-item results.

  • hires_batch_remove_tags

    Remove tags from up to 100 candidates; returns per-item results.

  • hires_list_candidate_files

    List a candidate's files (resume and other documents): uuid, download url, file metadata, type.

  • hires_upload_candidate_file

    Upload a base64 file to a candidate. Hosts truncate tool arguments above ~20 KB, so for resumes prefer resume_text in hires_create_candidate or hires_update_candidate.

  • hires_get_candidate_resume

    Get a candidate's primary resume: uuid, download url, file metadata, type. include=text_content adds the parsed plain text.

  • hires_list_candidate_activities

    List a candidate's timeline events. Prefer size <= 10. event_type values: comment, copilot_response, stage_moved, automation_action_triggered, assign_job, enrichment, call, validate_emails, profile_mutation, qualification, assign_tags…

  • hires_disqualify_candidate

    Reject all active applications of a candidate; returns the affected application ids.

  • hires_list_candidate_interviews

    List a candidate's interviews across all applications.

  • hires_list_candidate_messages

    List a candidate's email history; is_scheduled=1 returns only pending scheduled messages. Prefer size <= 10.

  • hires_send_candidate_message

    Schedule an email to a candidate; without scheduled_at it is sent 15 minutes after creation.

  • hires_list_applications

    List applications across accessible jobs with filters by candidate, job, stage, status, AI score and dates. Each item embeds its current stage, so a pipeline view needs no extra job call.

  • hires_create_application

    Link an existing candidate to a job, creating an application.

  • hires_get_application

    Get an application with its stage, status and rejection context.

  • hires_update_application

    Update application fields. stage_id performs a full stage transition with the target stage's automation, like hires_move_application.

  • hires_delete_application

    Permanently delete an application.

  • hires_move_application

    Move an application to a specific pipeline stage; stage ids come from the job's pipeline_stages.

  • hires_advance_application

    Advance an application to the next stage in workflow order; no stage_id needed.

  • hires_hire_application

    Mark an application as hired: status becomes hired and hired_at is set.

  • hires_reject_application

    Reject an application, optionally with a reason and without the rejection email.

  • hires_unreject_application

    Reopen a rejected application: status returns to active and rejected_at is cleared.

  • hires_transfer_application

    Transfer an application to another job by creating a new application there, optionally at a given stage.

  • hires_get_ai_score

    Get the AI score of an application with per-criterion scores, justifications and follow-up questions; null score until scored.

  • hires_list_application_stage_history

    Chronological stage transitions of an application, including the initial assignment: from/to stage, moved_at, moved_by_type (system, user, automation), moved_by_user_id and source. Prefer it over candidate activities for stage reports.

  • hires_list_application_attachments

    List an application's attachments with file metadata and download URLs.

  • hires_upload_application_attachment

    Upload a base64-encoded file as an application attachment.

  • hires_list_application_evaluations

    List filled evaluation forms of an application with evaluator, summary score (strong-yes to strong-no) and summary text.

  • hires_create_interview

    Schedule an interview for an application. The location is matched to an existing record or created.

  • hires_batch_move_applications

    Move up to 100 applications to a stage in one request; per-item results, partial success allowed.

  • hires_batch_reject_applications

    Reject up to 100 applications in one request, optionally with a reason; per-item results, partial success allowed.

  • hires_list_jobs

    List jobs filtered by status, creation/update time, department or search query.

  • hires_create_job

    Create a job. Required: status, title, description, location_country; location_city unless is_remote is true.

  • hires_get_job

    Get a job by id or alias.

  • hires_update_job

    Update a job. Send only the fields to change.

  • hires_delete_job

    Delete a job.

  • hires_set_job_status

    Change job status (publish, unpublish, archive).

  • hires_list_job_boards

    List job boards the job is published to, with their state.

  • hires_publish_to_job_board

    Queue the job for publication on the given boards.

  • hires_remove_from_job_board

    Deactivate the job's publication on the given boards.

  • hires_batch_job_boards

    Get board publication states for several jobs at once.

  • hires_batch_publish_to_boards

    Queue several jobs for publication on the given boards.

  • hires_batch_remove_from_boards

    Deactivate publication of several jobs on the given boards.

  • hires_list_hiring_team

    List users on the job's hiring team.

  • hires_add_hiring_team_member

    Add a company user to the job's hiring team.

  • hires_list_job_webhooks

    List webhooks subscribed to this job's events.

  • hires_create_job_webhook

    Register an HTTPS webhook for this job's events. Returns signing_secret once; use it to verify the x-hires-signature-v2 header.

  • hires_delete_job_webhook

    Delete a job webhook.

  • hires_rotate_job_webhook_secret

    Rotate the signing secret; the new one is returned once, the old stays valid for a grace window.

  • hires_list_messages

    List outbound messages (sent and scheduled) of one mail account; received mail is not included.

  • hires_get_message

    Get a scheduled message with sender account, schedule timestamps and cancelability.

  • hires_update_message

    Replace a scheduled message before it is sent; all required fields must be provided.

  • hires_patch_message

    Partially update a scheduled message before it is sent.

  • hires_delete_message

    Cancel a scheduled message before it is sent.

As primeiras 60 de 136, na ordem do servidor.

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

{
  "mcpServers": {
    "100hires": {
      "type": "http",
      "url": "https://mcp.100hires.com/mcp"
    }
  }
}

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.