Servidor MCP de HopeHire

• Nome no registroin.hopehire/mcpverificado no registro MCP

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

• Estadorespondeverificado em 2026-10-28
• Ferramentas167
• O servidor se chamaHopeHire
• Versão do servidor1.0.0
• Versão do protocolo2025-06-18

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

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 1 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 1 até agora
• Respondeumedindo1 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta375 ms
• Espaço no contexto do agente≈ 32.733 tokensas definições de todas as ferramentas (168), que o agente carrega a cada turno
• Definições das ferramentasC · 73 de 100
• Resultados tipados0 de 168 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 102 de 168
• Sem dizer se só lê ou se pode destruir: 168 de 168

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• get_notifications_api_notifications_get

  Get Notifications Fetch notifications for the current user. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ {} ] ```

• mark_all_notifications_as_read_api_notifications_read_all_post

  Mark All Notifications As Read Mark every unread notification as read (not just the page the client loaded). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• mark_notification_as_read_api_notifications__notification_id__read_patch

  Mark Notification As Read Mark a notification as read. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• delete_notification_api_notifications__notification_id__delete

  Delete Notification Delete a notification. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_ats_score_api_resume_ats_score_get

  Get Ats Score Return the most recently calculated ATS score for the user's resume. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• refresh_ats_score_api_resume_ats_score_refresh_post

  Refresh Ats Score Recalculate the ATS score from the current resume and persist it. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• resume_ai_chat_api_resume_ai_chat_post

  Resume Ai Chat Stream an AI response that helps the user interactively improve their resume. Body: user_id (str) — authenticated user's ID message (str) — latest user message conversation_history (list) — [{role: "user"|"assistant"…

• mark_improvement_suggestions_invalid_api_resume_improvement_suggestions_mark_inv

  Mark Improvement Suggestions Invalid Replace improvement suggestions with the provided valid_suggestions list. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• generate_yaml_version_api_resume_generate_yaml_post

  Generate Yaml Version Generate YAML version and RenderCV PDF for existing resume ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• apply_suggestions_api_resume_apply_suggestions_post

  Apply Suggestions Apply improvement suggestions to YAML and regenerate PDF ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_yaml_suggestions_api_resume_yaml_suggestions_post

  Get Yaml Suggestions Generate YAML-based improvement suggestions ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• generate_complete_resume_api_resume_generate_complete_post

  Generate Complete Resume Generate a complete, enhanced resume with additional relevant content using AI. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• render_raw_yaml_api_resume_render_raw_yaml_post

  Render Raw Yaml Hot-reload: Generate PDF from raw YAML content ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• list_themes_api_resume_themes_get

  List Themes ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• apply_resume_theme_api_resume_apply_theme_post

  Apply Resume Theme Switch the design theme in a YAML document. Pure transform: no render, no save. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• save_resume_yaml_api_resume_save_yaml_post

  Save Resume Yaml Save raw YAML content to the user's resume. YAML is treated as the source of truth: the structured resume fields (personalInfo, experience, education, projects, skills, certifications) are parsed from the YAML and written…

• create_resume_from_linkedin_api_resume_from_linkedin_post

  Create Resume From Linkedin Create a resume from LinkedIn profile URL using Apify API. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json {…

• get_rendercv_pdf_api_resume_rendercv_pdf_get

  Get Rendercv Pdf Get RenderCV PDF download URL for the user's resume. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_rendercv_pdf_download_api_resume_rendercv_pdf_download_get

  Get Rendercv Pdf Download Return a presigned URL with Content-Disposition: attachment so the browser downloads the resume PDF instead of opening it inline. ### Responses: **200**: Successful Response (Success Response) Content-Type…

• test_pdf_generation_api_resume_test_pdf_generation_get

  Test Pdf Generation Test PDF generation to debug PDF issues. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• debug_pdf_api_resume_debug_pdf_get

  Debug Pdf Get debugging information about a PDF file. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• download_resume_api_resume_download_get

  Download Resume Download the user's resume. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• public_resume_api_resume_public_get

  Public Resume Resume link embedded in cold emails: no login, but only links we signed will open. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• show_resume_api_resume__resume_id__get

  Show Resume Show the resume via redirect to presigned S3 URL. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• get_resume_api_resume_get

  Get Resume Get the user's resume. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• upload_resume_api_resume_post

  Upload Resume Upload and process a resume file. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• update_resume_manual_api_resume_put

  Update Resume Manual Update a user's resume manually and trigger PDF generation. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json {…

• delete_resume_api_resume_delete

  Delete Resume Delete the user's resume and cleanup associated resources. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• set_cold_email_resume_source_api_resume_cold_email_source_put

  Set Cold Email Resume Source Set which resume file cold outreach should use: the originally uploaded file ("uploaded", the default) or HopeHire's RenderCV-generated PDF ("generated"). A lightweight sibling to the full manual-edit PUT…

• get_preferences_api_job_preferences_get

  Get Preferences Get the user's job preferences Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• create_preferences_api_job_preferences_post

  Create Preferences Create the user's job preferences Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• update_preferences_api_job_preferences_put

  Update Preferences Update the user's job preferences Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• delete_preferences_api_job_preferences_delete

  Delete Preferences Delete the user's job preferences Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• start_job_matching_api_job_matches_start_post

  Start Job Matching Start an asynchronous job matching process Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_filtered_jobs_api_job_matches_get

  Get Filtered Jobs Get filtered job matches for a user Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• clear_job_matches_api_job_matches_delete

  Clear Job Matches Clear all job matches for a user Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• start_conversation_api_auto_apply_start_conversation_post

  Start Conversation Start a new conversation using the shared auto-apply service logic. ### Responses: **201**: Successful Response (Success Response) Content-Type: application/json

• start_auto_apply_api_auto_apply_post

  Start auto-apply process Launches an automated job application process that finds contacts, generates personalized messages, and sends emails with resume attachments. ### Responses: **200**: Successful Response (Success Response)…

• get_auto_apply_tasks_api_auto_apply_get

  Get all auto-apply tasks for a user Get all auto-apply tasks for a given user. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_auto_apply_status_api_auto_apply__task_id__get

  Check auto-apply status Retrieves the current status and results of an auto-apply task. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "task_id": "Task Id"…

• get_auto_apply_status_by_task_id_api_auto_apply_status__task_id__get

  Get Auto Apply Status By Task Id Get status of an auto-apply task by task_id (conversationId). Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:**…

• start_conversation_api_email_conversations_start_conversation_post

  Start Conversation Start a new email conversation. ### Responses: **201**: Successful Response (Success Response) Content-Type: application/json

• get_conversations_api_email_conversations_get

  Get Conversations Get all conversations for the authenticated user. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ { "id": "Id", "contact_email": "Contact…

• get_conversation_details_api_email_conversations__conversation_id__get

  Get Conversation Details Get details of a specific conversation. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "id": "Id", "contact_email": "Contact Email"…

• pause_conversation_api_email_conversations__conversation_id__pause_post

  Pause Conversation Pause an ongoing conversation to stop automatic follow-ups. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• resume_conversation_api_email_conversations__conversation_id__resume_post

  Resume Conversation Resume a paused conversation. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• send_manual_message_api_email_conversations__conversation_id__message_post

  Send Manual Message Send a manual message in the conversation, overriding the AI. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• resolve_protocol_api_email_conversations__conversation_id__resolve_post

  Resolve Protocol Resolve a human-intervention protocol by sending a manual reply and marking the associated notification as read. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_system_stats_api_multi_tenant_monitoring_stats_get

  Get System Stats Get overall system statistics ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "workers": [ {} ], "total_active_users": 1, "system_status"…

• get_active_users_api_multi_tenant_monitoring_users_active_get

  Get Active Users Get list of active users with email monitoring enabled ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ {} ] ```

• enable_user_monitoring_api_multi_tenant_monitoring_users__user_id__enable_post

  Enable User Monitoring Enable email monitoring for a specific user ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• disable_user_monitoring_api_multi_tenant_monitoring_users__user_id__disable_post

  Disable User Monitoring Disable email monitoring for a specific user ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• update_user_monitoring_config_api_multi_tenant_monitoring_users__user_id__config

  Update User Monitoring Config Update email monitoring configuration for a user ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• trigger_user_discovery_api_multi_tenant_monitoring_discovery_trigger_post

  Trigger User Discovery Manually trigger user discovery process ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_user_monitoring_status_api_multi_tenant_monitoring_users__user_id__status_ge

  Get User Monitoring Status Get monitoring status for a specific user ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_email_analytics_report_api_reports__user_id___duration__get

  Get Email Analytics Report Get email analytics report for a user over a specific duration. Duration options: - 7d: Last 7 days - 30d: Last 30 days - 90d: Last 90 days - 1y: Last year - all: All time ### Responses: **200**: Successful…

• get_email_analytics_summary_api_reports__user_id__summary_get

  Get Email Analytics Summary Get a quick summary of email analytics for the last 30 days. This is a lightweight endpoint for dashboard widgets. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json

• get_user_memory_api_user_memory__user_id__get

  Get User Memory Get user memory by user ID ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• create_user_memory_api_user_memory__user_id__post

  Create User Memory Create new user memory ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

• update_user_memory_api_user_memory__user_id__put

  Update User Memory Update existing user memory ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```

As primeiras 60 de 167, na ordem do servidor.