HopeHire
REMOTE · HOPEHIRE.IN
Tailor resumes, score ATS fit, find hiring leads, and send cold outreach, from your agent.
Available components
Last scanned (23 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 4 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 Management40
- Stability observed for 12 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 4 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 →
add_account_api_linkedin_leads_accounts_post ~86
Add Account Add a LinkedIn scraper account to the pool. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_queries | array | – | – |
| string | yes | – | |
| max_requests_per_day | integer | – | – |
| password | string | yes | – |
| proxy | string | – | – |
No output schema declared.
No examples provided.
add_ai_interaction_context_api_user_memory__user_id__context_post ~78
Add Ai Interaction Context Add AI interaction context to user memory ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
add_hr_contact_endpoint_api_companies__company_id__hr_contacts_post ~71
Add Hr Contact Endpoint ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "name": "Name" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | – |
No output schema declared.
No examples provided.
agent_step_api_extension_agent_step_post ~179
Agent Step Tier 4: one step of an agentic fallback loop for pages where tiers 1-3 (coded adapters, universal field matcher, batched AI field-answering) found nothing to work with. The extension sends a snapshot of every visible interactive element on the page; this returns exactly one action to take next. Never raises on a bad/failed model response - degrades to "blocked" so the client loop just stops rather than crashing the fill. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "action": "Action" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| elements | array | yes | – |
| history | array | – | – |
| job_context | object | yes | – |
| step | integer | yes | – |
No output schema declared.
No examples provided.
answer_fields_api_extension_answer_fields_post ~135
Answer Fields AI fallback for job-application form fields the extension's coded/heuristic fill pass could not confidently answer. Batched per application (not per field) to control latency and cost. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "answers": [ { "field_id": "Field Id", "confidence": "Confidence", "source": "Source" } ] } ```
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | – |
| job_context | object | yes | – |
No output schema declared.
No examples provided.
apify_webhook_api_linkedin_leads_webhook_apify_post ~81
Apify Webhook Receives push notifications from Apify when a scraper run completes. No authentication required (Apify calls this endpoint). Apify includes a secret token in the URL for verification in production. ### 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.
apply_memory_suggestion_api_user_memory_apply_suggestion_post ~59
Apply Memory Suggestion Apply a specific memory update suggested by the AI. Body: { user_id, suggestion } ### 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.
apply_resume_theme_api_resume_apply_theme_post ~55
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
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
apply_suggestions_api_resume_apply_suggestions_post ~46
Apply Suggestions Apply improvement suggestions to YAML and regenerate PDF ### 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.
approve_outreach_item_api_outreach_queue__item_id__approve_post ~62
Approve Outreach Item Approve a queue item and send the cold email. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
No output schema declared.
No examples provided.
bulk_send_outreach_api_linkedin_leads_bulk_outreach_post ~111
Bulk Send Outreach Send outreach emails to multiple leads in one call. Each lead must have an email address. Leads without emails are skipped. Returns per-lead results so the frontend can show success/fail per contact. Rate-limited to 20 leads per request to protect Gmail sending quotas. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| lead_ids | array | yes | List of lead IDs to contact |
No output schema declared.
No examples provided.
cancel_outreach_batch_api_outreach_batches__batch_id__cancel_post ~51
Cancel Outreach Batch ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| batch_id | string | yes | – |
No output schema declared.
No examples provided.
cancel_pending_auto_reply_api_auto_replies__reply_id__delete ~61
Cancel Pending Auto Reply Cancel a pending auto-reply before it fires. ### 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.
claim_referral_code_api_referrals_claim_post ~65
Claim Referral Code Claim a referral code. Awards 10 credits to both the claimer and the referrer. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| referral_code | string | yes | – |
No output schema declared.
No examples provided.
clear_job_matches_api_job_matches_delete ~61
Clear Job Matches Clear all job matches for a user Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | – | User ID to clear matches for |
No output schema declared.
No examples provided.
create_application_api_applications_post ~213
Create Application Track a newly-submitted job application (called by the extension after a user submits). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "user_id": "User Id", "company_name": "Company Name", "job_title": "Job Title", "job_url": "Job Url", "platform": "Platform", "status": "ApplicationStatus", "applied_at": "2023-01-01T00:00:00Z", "status_history": [ { "status": "ApplicationStatus", "changed_at": "2023-01-01T00:00:00Z" } ], "source": "Source" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | – |
| job_title | string | yes | – |
| job_url | string | yes | – |
| platform | string | – | – |
No output schema declared.
No examples provided.
create_company_endpoint_api_companies_post ~91
Create Company Endpoint ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "hrContacts": [ { "email": "Email" } ], "hrContactCount": 1 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| hrEmail | string | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
create_invites_api_orgs_me_invites_post ~46
Create Invites ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| invites | array | yes | – |
No output schema declared.
No examples provided.
create_key_api_api_keys_post ~60
Create Key Create a new API key. The raw key is only ever returned here -- store it now. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
create_outreach_batch_api_outreach_batches_post ~88
Create Outreach Batch ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| batch_type | string | yes | linkedin_leads | outreach_queue |
| item_ids | array | – | Explicit IDs to process; otherwise auto-select from fresh/pending items |
| limit | integer | – | – |
| min_quality | number | – | – |
No output schema declared.
No examples provided.
create_preferences_api_job_preferences_post ~189
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 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| expectedCtc | string | – | – |
| experienceLevels | array | – | – |
| functionAreas | array | – | – |
| graduationYear | integer | – | – |
| id | string | – | – |
| industries | array | – | – |
| isFresher | boolean | – | – |
| jobTypes | array | – | – |
| locationTypes | array | – | – |
| locations | array | – | – |
| specializations | array | – | – |
| targetCompanies | array | – | – |
| targetRoles | array | – | – |
| techStack | array | – | – |
| updatedAt | string | – | – |
| userId | string | – | – |
No output schema declared.
No examples provided.
create_resume_from_linkedin_api_resume_from_linkedin_post ~75
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 { "success": true } ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_user_memory_api_user_memory__user_id__post ~145
Create User Memory Create new user memory ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| ai_context_notes | string | – | – |
| auto_apply_preferences | object | – | – |
| career_context | object | – | – |
| communication_preferences | object | – | – |
| compensation | object | – | – |
| job_preferences | object | – | – |
| notice_period | object | – | – |
| safety_guardrails | object | – | – |
| screening_profile | object | – | – |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
debug_pdf_api_resume_debug_pdf_get ~54
Debug Pdf Get debugging information about a PDF file. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | – |
No output schema declared.
No examples provided.
delete_key_api_api_keys__key_id__delete ~46
Delete Key ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | – |
No output schema declared.
No examples provided.
delete_notification_api_notifications__notification_id__delete ~49
Delete Notification Delete a notification. ### 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.
delete_preferences_api_job_preferences_delete ~51
Delete Preferences Delete the user's job preferences Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | – | – |
No output schema declared.
No examples provided.
delete_remembered_field_answer_api_user_memory__user_id__remembered_field_delete ~107
Delete Remembered Field Answer Forgets one remembered application-field answer (memory-bank UI delete action). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| normalized_label | string | yes | The entry's normalized_label, as returned in interaction_history |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
delete_resume_api_resume_delete ~62
Delete Resume Delete the user's resume and cleanup associated resources. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| s3Path | string | – | – |
| user_id | string | – | – |
No output schema declared.
No examples provided.
delete_user_memory_api_user_memory__user_id__delete ~74
Delete User Memory Delete (deactivate) user memory ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
disable_user_monitoring_api_multi_tenant_monitoring_users__user_id__disable_post ~62
Disable User Monitoring Disable email monitoring for a specific user ### 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.
disconnect_app_api_tools_connect__app_name__delete ~59
Disconnect App Revoke the user's Composio connection for a specific app. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| app_name | string | yes | – |
No output schema declared.
No examples provided.
dismiss_outreach_item_api_outreach_queue__item_id__delete ~57
Dismiss Outreach Item Dismiss an outreach queue item. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
No output schema declared.
No examples provided.
download_resume_api_resume_download_get ~66
Download Resume Download the user's resume. ### 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.
enable_user_monitoring_api_multi_tenant_monitoring_users__user_id__enable_post ~62
Enable User Monitoring Enable email monitoring for a specific user ### 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.
execute_tool_api_tools_execute_post ~44
Execute Tool Executes a tool by name with provided arguments. ### 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.
extension_apply_api_extension_apply_post ~166
Extension Apply Orchestrator called by the extension right after a user submits a job application: tracks the application, then immediately attempts the same credit-gated cold-outreach send the daily cron would eventually do, triggered on-demand instead. Outreach is best-effort: if there is no known contact for the company or the user is out of credits, the application is still tracked and the response says why outreach was skipped rather than failing the request. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | – |
| job_description | string | – | – |
| job_title | string | yes | – |
| job_url | string | yes | – |
| platform | string | – | – |
No output schema declared.
No examples provided.
generate_complete_resume_api_resume_generate_complete_post ~69
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
| Name | Type | Req | Description |
|---|---|---|---|
| resume_text | string | yes | – |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
generate_footer_from_resume_api_email_footer__user_id__generate_from_resume_post ~61
Generate Footer From Resume Generate email footer from user's resume data. ### 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.
generate_linkedin_message_api_linkedin_leads__lead_id__generate_linkedin_message_post ~99
Generate Linkedin Message Generate a short LinkedIn outreach message (≤280 chars) personalised to this lead. The frontend copies it to clipboard and opens the recruiter's LinkedIn profile so the user can paste-and-send in one step. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| lead_id | string | yes | – |
No output schema declared.
No examples provided.
generate_yaml_version_api_resume_generate_yaml_post ~49
Generate Yaml Version Generate YAML version and RenderCV PDF for existing resume ### 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.
get_active_outreach_batch_api_outreach_batches_active_get ~41
Get Active Outreach Batch ### 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.
get_active_users_api_multi_tenant_monitoring_users_active_get ~90
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 [ {} ] ```
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of users to return |
| skip | integer | – | Number of users to skip |
No output schema declared.
No examples provided.
get_all_campaign_configs_api_config_admin_campaigns_get ~49
Get All Campaign Configs Get all campaign configurations (admin only) ### 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.
get_all_leads_admin_api_linkedin_leads_all_get ~83
Get All Leads Admin Admin view: return all leads regardless of outreach status. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| email_only | boolean | – | – |
| limit | integer | – | – |
| min_quality | number | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
get_all_user_configs_api_config_admin_users_get ~48
Get All User Configs Get all user configurations (admin only) ### 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.
get_ats_score_api_resume_ats_score_get ~51
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
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_auto_apply_status_api_auto_apply__task_id__get ~105
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", "status": "AutoApplyStatus" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Auto-apply task ID returned from the start endpoint |
No output schema declared.
No examples provided.
get_auto_apply_status_by_task_id_api_auto_apply_status__task_id__get ~110
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:** ```json { "task_id": "Task Id", "status": "AutoApplyStatus" } ```
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Auto-apply task ID |
No output schema declared.
No examples provided.
get_auto_apply_tasks_api_auto_apply_get ~73
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
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | – | ID of the user to fetch tasks for |
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.