HopeHire
REMOTE · HOPEHIRE.IN
Tailor resumes, score ATS fit, find hiring leads, and send cold outreach, from your agent.
Available components
Last scanned (6 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 168 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 15344 tokens (~91/item across 168 items; 168 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 21% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 24 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_notification_api_notifications__notification_id__delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 168 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
- New tool “send_pending_auto_reply_now_api_auto_replies__reply_id__send_post” functional
- 27 Oct 26 +1
- New tool “apply_resume_theme_api_resume_apply_theme_post” functional
- New tool “list_themes_api_resume_themes_get” functional
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://hopehire.in/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hopehire.in | CN=WR3,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | b56fc1b2fdde48e40a759f2eda020388 |
| SANs: hopehire.in, www.hopehire.in | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hopehire.in. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| hopehire.in. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hopehire.in/mcp | Verified | 200 | |
| http (plaintext) | http://hopehire.in/mcp | HTTPS enforced | 301 | https://hopehire.in/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_invites_api_orgs_me_invites_get ~46
List Invites ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | – |
No output schema declared.
No examples provided.
list_keys_api_api_keys_get ~34
List Keys ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_scrape_runs_api_linkedin_leads_scrape_runs_get ~71
List Scrape Runs List recent scrape run records for audit / dashboard (admin only: they hold platform-wide queries and volumes). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_templates_api_email_templates_get ~117
List Templates Return the user's email templates, generating them if none exist yet. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ { "id": "Id", "name": "Name", "subject": "Subject", "body": "Body", "usage_count": 1, "reply_count": 1, "reply_rate": 1.0 } ] ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_themes_api_resume_themes_get ~36
List Themes ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mark_all_notifications_as_read_api_notifications_read_all_post ~56
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
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mark_improvement_suggestions_invalid_api_resume_improvement_suggestions_mark_invalid_post ~76
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
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
| valid_suggestions | array | yes | – |
No output schema declared.
No examples provided.
mark_notification_as_read_api_notifications__notification_id__read_patch ~56
Mark Notification As Read Mark a notification as read. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| notification_id | string | yes | – |
No output schema declared.
No examples provided.
match_score_api_extension_match_score_post ~136
Match Score Ad-hoc resume<->job-description match score for a posting the extension is looking at, which isn't (and doesn't need to be) a job stored in the DB. Uses the pure heuristic matcher (no embeddings/DB lookups needed). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "match_score": 1.0, "summary": "Summary", "missing_skills": [ "string" ] } ```
| Name | Type | Req | Description |
|---|---|---|---|
| job_description | string | yes | – |
No output schema declared.
No examples provided.
my_org_api_orgs_me_get ~35
My Org ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_org_summary_api_orgs_me_summary_get ~38
My Org Summary ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_students_api_orgs_me_students_get ~65
My Students ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| cohort_id | string | – | – |
| limit | integer | – | – |
| q | string | – | – |
| skip | integer | – | – |
No output schema declared.
No examples provided.
pause_conversation_api_email_conversations__conversation_id__pause_post ~65
Pause Conversation Pause an ongoing conversation to stop automatic follow-ups. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | ID of the conversation to pause |
No output schema declared.
No examples provided.
preview_cold_email_api_cold_email_preview_post ~111
Preview Cold Email Generate a preview of a cold email without sending it. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "message": "Message", "subject": "Subject" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | – |
| recruiter_email | string | yes | – |
| user_id | string | yes | – |
| user_profile | object | yes | – |
No output schema declared.
No examples provided.
preview_unified_cold_email_api_cold_email_unified_preview_post ~163
Preview Unified Cold Email Generate a preview for unified cold email flow. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "message": "Message", "subject": "Subject" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | – |
| email_content | string | – | – |
| fallback_enabled | boolean | – | – |
| hr_email | string | – | – |
| is_new_company | boolean | – | – |
| jobLink | string | – | – |
| sender_user_id | string | – | – |
| subject | string | – | – |
| user_id | string | yes | – |
| user_profile | object | yes | – |
No output schema declared.
No examples provided.
public_resume_api_resume_public_get ~68
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
| Name | Type | Req | Description |
|---|---|---|---|
| s3Path | string | yes | – |
| sig | string | yes | – |
No output schema declared.
No examples provided.
refresh_ats_score_api_resume_ats_score_refresh_post ~53
Refresh Ats Score Recalculate the ATS score from the current resume and persist it. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
regenerate_templates_api_email_templates_regenerate_post ~119
Regenerate Templates Delete all existing templates and generate a fresh one via AI. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ { "id": "Id", "name": "Name", "subject": "Subject", "body": "Body", "usage_count": 1, "reply_count": 1, "reply_rate": 1.0 } ] ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remember_field_answer_api_extension_remember_field_answer_post ~182
Remember Field Answer Durable, cross-device, cross-site memory of one field answer the extension learned - either a confirmed AI answer or a user's correction, fired on every blur/selection of a field the extension filled. Grounds future /answer-fields calls (see get_remembered_field_answers above) so the same question doesn't need asking again on the next application, anywhere. Requires extension_field_memory_consent - the extension's own UI should already gate whether it ever sends this request, but a consent decision this sensitive (can include EEO/self-identification answers the user typed themselves) shouldn't rely on client-side gating alone. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
remove_student_api_orgs_me_students__user_id__delete ~48
Remove Student ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
render_raw_yaml_api_resume_render_raw_yaml_post ~50
Render Raw Yaml Hot-reload: Generate PDF from raw YAML content ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reset_campaign_config_api_config_campaign__campaign_id__delete ~54
Reset Campaign Config Reset campaign configuration to defaults ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | – |
No output schema declared.
No examples provided.
reset_user_config_api_config_user__user_id__delete ~54
Reset User Config Reset user configuration to defaults ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
resolve_protocol_api_email_conversations__conversation_id__resolve_post ~103
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
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | ID of the conversation |
| message_content | string | yes | Content of the manual message to send |
| notification_id | string | yes | ID of the notification to mark as read |
No output schema declared.
No examples provided.
resume_ai_chat_api_resume_ai_chat_post ~99
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", content: str}] ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resume_conversation_api_email_conversations__conversation_id__resume_post ~60
Resume Conversation Resume a paused conversation. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | ID of the conversation to resume |
No output schema declared.
No examples provided.
resume_outreach_endpoint_api_autopilot_resume_outreach_post ~125
Resume Outreach Endpoint User-initiated: clear the bounce circuit breaker's paused state. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "daily_outreach_enabled": true, "outreach_timezone": "Outreach Timezone", "daily_outreach_batch_size": 1, "credit_balance": 1, "autopilot_enabled": true, "outreach_paused": true } ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
revoke_invite_api_orgs_me_invites__invite_id__delete ~51
Revoke Invite ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| invite_id | string | yes | – |
No output schema declared.
No examples provided.
save_resume_yaml_api_resume_save_yaml_post ~114
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 back to the database so that every other part of the application (resume overview, AI chat, job matching …) always reflects the latest YAML edits. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_cold_email_api_cold_email_post ~215
Send Cold Email Send a cold email with a pre-generated message. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "user_id": "User Id", "recruiter_email": "Recruiter Email", "company_name": "Company Name", "sent_at": "2023-01-01T00:00:00Z", "status": "Status", "followup_interval_hours": 1, "followup_count": 1, "replied": true, "message": "Message", "opened": true, "open_count": 1, "auto_draft_generated": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | – |
| message | string | yes | – |
| recruiter_email | string | yes | – |
| user_id | string | yes | – |
| user_profile | object | yes | – |
No output schema declared.
No examples provided.
send_cold_email_to_hr_api_cold_email_send_to_hr_post ~98
Send Cold Email To Hr Send a cold email to a specific HR contact. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | – |
| company_name | string | yes | – |
| hr_email | string | yes | – |
| user_id | string | yes | – |
| user_profile | object | yes | – |
No output schema declared.
No examples provided.
send_email_via_pool_api_email_sender_pool_send_email_post ~145
Send Email Via Pool Send an email using the email sender pool (admin only) ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| attachment_filename | string | – | – |
| in_reply_to | string | – | – |
| message_text | string | yes | – |
| references | string | – | – |
| s3_attachment_key | string | – | – |
| sender_user_id | string | – | – |
| subject | string | yes | – |
| thread_id | string | – | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
send_manual_message_api_email_conversations__conversation_id__message_post ~81
Send Manual Message Send a manual message in the conversation, overriding the AI. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | ID of the conversation |
| message_content | string | yes | Content of the manual message to send |
No output schema declared.
No examples provided.
send_outreach_from_lead_api_linkedin_leads__lead_id__send_outreach_post ~234
Send Outreach From Lead Generate and send a cold outreach email directly from a LinkedIn lead. Flow: 1. Fetch the lead — must have an email address. 2. Load the authenticated user's resume/profile from MongoDB. 3. Call send_and_track_cold_email() to generate (or use custom_message) and send the email via the user's connected Gmail. 4. Record the outreach status on the lead (status='sent') with a back- reference to the cold_email_id. 5. Sync the company HR contact (idempotent — already done on scrape, but update lastContactedAt now). Returns the cold_email_id so the frontend can link to the email thread. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| custom_message | string | – | Override the LLM-generated email body |
| job_link | string | – | Optional job URL to include in the email |
| lead_id | string | yes | – |
No output schema declared.
No examples provided.
send_pending_auto_reply_now_api_auto_replies__reply_id__send_post ~74
Send Pending Auto Reply Now Send a pending auto-reply now instead of waiting for tomorrow's 9:30 AM run. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| reply_id | string | yes | – |
No output schema declared.
No examples provided.
send_product_update_broadcast_api_newsletter_send_post ~69
Send Product Update Broadcast Manually trigger a one-off product-update broadcast to all subscribed users. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| html_body | string | yes | – |
| subject | string | yes | – |
No output schema declared.
No examples provided.
send_unified_cold_email_api_cold_email_unified_post ~332
Send Unified Cold Email Unified cold email endpoint that handles: 1. Company creation if it doesn't exist 2. HR email auto-selection if not provided 3. HR contact addition to company 4. Email sending with tracking Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true, "cold_email": { "user_id": "User Id", "recruiter_email": "Recruiter Email", "company_name": "Company Name", "sent_at": "2023-01-01T00:00:00Z", "status": "Status", "followup_interval_hours": 1, "followup_count": 1, "replied": true, "message": "Message", "opened": true, "open_count": 1, "auto_draft_generated": true }, "hr_email_used": "Hr Email Used", "company_created": true, "hr_added": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | – |
| email_content | string | – | – |
| fallback_enabled | boolean | – | – |
| hr_email | string | – | – |
| is_new_company | boolean | – | – |
| jobLink | string | – | – |
| sender_user_id | string | – | – |
| subject | string | – | – |
| user_id | string | yes | – |
| user_profile | object | yes | – |
No output schema declared.
No examples provided.
set_cold_email_resume_source_api_resume_cold_email_source_put ~118
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 above — this only flips one field and doesn't trigger PDF/YAML regeneration. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
show_resume_api_resume__resume_id__get ~76
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 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| s3Path | string | yes | – |
No output schema declared.
No examples provided.
start_auto_apply_api_auto_apply_post ~135
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) Content-Type: application/json **Example Response:** ```json { "task_id": "Task Id", "status": "AutoApplyStatus" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | ID of the job to apply for |
| user_id | string | yes | ID of the user applying for the job |
| user_profile | object | yes | User profile information for job application |
No output schema declared.
No examples provided.
start_conversation_api_auto_apply_start_conversation_post ~103
Start Conversation Start a new conversation using the shared auto-apply service logic. ### Responses: **201**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Related job ID |
| resume_id | string | – | Resume ID if available |
| user_id | string | yes | User ID initiating the conversation |
| user_profile | object | – | User profile (optional, for backward compatibility) |
No output schema declared.
No examples provided.
start_conversation_api_email_conversations_start_conversation_post ~131
Start Conversation Start a new email conversation. ### Responses: **201**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | yes | Email address of the contact |
| contact_name | string | – | Name of the contact |
| context_data | object | – | Additional context data |
| initial_body | string | – | Optional initial message body |
| intent | string | yes | Primary intent of the conversation |
| job_id | string | – | Related job ID if applicable |
| subject_line | string | yes | Subject line for the conversation |
No output schema declared.
No examples provided.
start_job_matching_api_job_matches_start_post ~91
Start Job Matching Start an asynchronous job matching process Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| resume_id | string | – | Resume ID to use for matching |
| use_preferences | boolean | – | Whether to filter jobs by user preferences first |
| user_id | string | – | User ID to match jobs for |
No output schema declared.
No examples provided.
submit_feedback_api_feedback_post ~49
Submit Feedback ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | yes | – |
| feedback_text | string | – | – |
No output schema declared.
No examples provided.
tailor_resume_api_extension_tailor_resume_post ~120
Tailor Resume Generates a one-off resume PDF reworded toward a specific job description, for the extension to swap into a file-upload field before submitting that one application. Never persisted to the user's profile/canonical resume. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "pdf_base64": "Pdf Base64", "file_name": "File Name" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| job_description | string | yes | – |
No output schema declared.
No examples provided.
test_pdf_generation_api_resume_test_pdf_generation_get ~49
Test Pdf Generation Test PDF generation to debug PDF issues. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tracking_pixel_api_tracking_pixel__email_id__png_get ~66
Tracking Pixel Endpoint for the email tracking pixel. When loaded, it updates the corresponding email record as opened. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| email_id | string | yes | – |
No output schema declared.
No examples provided.
trigger_scrape_api_linkedin_leads_trigger_post ~142
Trigger Scrape Manually kick off a LinkedIn scrape run. Admin only: each run spends metered Apify credits and accepts arbitrary search queries. Strategy (tried in order): 1. Publish to the linkedin_scrape_queue via RabbitMQ (if running). 2. If RabbitMQ is unavailable or times out, run the scrape directly as a FastAPI BackgroundTask so this endpoint always returns fast. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| max_posts_per_query | integer | – | – |
| queries | array | – | – |
No output schema declared.
No examples provided.
trigger_user_discovery_api_multi_tenant_monitoring_discovery_trigger_post ~50
Trigger User Discovery Manually trigger user discovery process ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
unsubscribe_api_newsletter_unsubscribe_get ~79
Unsubscribe Public link clicked from a newsletter email - no auth, verified by HMAC signature. ### Responses: **200**: Successful Response (Success Response) Content-Type: text/html **Example Response:** ```json "string" ```
| Name | Type | Req | Description |
|---|---|---|---|
| sig | string | yes | – |
| uid | string | yes | – |
No output schema declared.
No examples provided.
How do I install the HopeHire MCP server?
HopeHire is a hosted endpoint at https://hopehire.in/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hopehire.in
claude mcp add --transport http in-hopehire-mcp 'https://hopehire.in/mcp'
What is the HopeHire MCP server?
HopeHire is an MCP server listed in the public MCP registry as in.hopehire/mcp. Tailor resumes, score ATS fit, find hiring leads, and send cold outreach, from your agent. This page covers its hosted endpoint (https://hopehire.in/mcp).
Is the HopeHire MCP server safe to use?
HopeHire scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HopeHire MCP server expose?
HopeHire exposes 168 tools: get_notifications_api_notifications_get, mark_all_notifications_as_read_api_notifications_read_all_p…, mark_notification_as_read_api_notifications__notification_i…, delete_notification_api_notifications__notification_id__del…, get_ats_score_api_resume_ats_score_get, and 163 more. Their descriptions and schemas cost roughly 15,344 tokens of context every time the server is loaded.
Does the HopeHire MCP server require authentication?
No. We connected to HopeHire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HopeHire MCP server still maintained?
HopeHire is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.