HopeHire
REMOTE · HOPEHIRE.IN
Tailor resumes, score ATS fit, find hiring leads, and send cold outreach, from your agent.
Available components
Last scanned (34 minutes 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 →
get_autopilot_settings_api_autopilot_settings_get ~112
Get Autopilot Settings ### 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.
get_available_leads_api_linkedin_leads_get ~142
Get Available Leads Return leads for the authenticated user, filtered by outreach status. status=fresh — leads not yet contacted (default); AI-ranked status=queued — leads the user has queued for outreach status=contacted — leads the user has already emailed ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| email_only | boolean | – | Only return leads with a known email address |
| limit | integer | – | – |
| min_quality | number | – | – |
| offset | integer | – | – |
| status | string | – | fresh | queued | contacted |
No output schema declared.
No examples provided.
get_available_senders_api_email_sender_pool_senders_get ~79
Get Available Senders Get all available email senders (admin only — exposes other senders' PII and quotas) ### 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.
get_campaign_config_api_config_campaign__campaign_id__get ~55
Get Campaign Config Get configuration for a specific campaign ### 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.
get_cold_email_api_cold_email_get ~231
Get Cold Email Get cold emails for a user with pagination. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "cold_emails": [ { "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 } ], "offset": 1, "pagination": 1, "has_more": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | yes | – |
| pagination | integer | yes | – |
| user_id | string | – | – |
No output schema declared.
No examples provided.
get_cold_email_replies_api_cold_email__cold_email_id__replies_get ~82
Get Cold Email Replies Get replies for a specific cold email using its ID. This checks both the cold_emails collection and email_conversations collection. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| cold_email_id | string | yes | – |
No output schema declared.
No examples provided.
get_cold_email_replies_by_message_id_api_cold_email_message__message_id__replies_get ~89
Get Cold Email Replies By Message Id Get replies for a cold email using its Gmail message_id. This is useful when you have the message_id from the cold email response. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| message_id | string | yes | – |
No output schema declared.
No examples provided.
get_connection_url_api_tools_connect__app_name__get ~60
Get Connection Url Get the authorization URL for a specific Composio 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.
get_conversation_details_api_email_conversations__conversation_id__get ~159
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", "status": "ConversationStatus", "intent": "ConversationIntent", "subject_line": "Subject Line", "message_count": 1, "last_updated": "2023-01-01T00:00:00Z", "messages": [ {} ], "context_data": {} } ```
| Name | Type | Req | Description |
|---|---|---|---|
| conversation_id | string | yes | ID of the conversation to get |
No output schema declared.
No examples provided.
get_conversations_api_email_conversations_get ~143
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 Email", "status": "ConversationStatus", "intent": "ConversationIntent", "subject_line": "Subject Line", "message_count": 1, "last_updated": "2023-01-01T00:00:00Z" } ] ```
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| skip | integer | – | – |
No output schema declared.
No examples provided.
get_default_config_api_config_defaults_get ~41
Get Default Config Get default configuration values ### 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_effective_config_api_config_effective__user_id__get ~67
Get Effective Config Get effective configuration combining user and campaign settings ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | – | – |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
get_email_analytics_report_api_reports__user_id___duration__get ~118
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 Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | yes | – |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
get_email_analytics_summary_api_reports__user_id__summary_get ~74
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
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
get_email_footer_api_email_footer__user_id__get ~55
Get Email Footer Get email footer for a 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.
get_extension_settings_api_extension_settings_get ~77
Get Extension Settings ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "recruiter_comms_consent": true, "field_memory_consent": true, "credit_balance": 1 } ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fallback_sender_api_email_sender_pool_fallback_sender_get ~89
Get Fallback Sender Get a fallback email sender, excluding the specified user (admin only) ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_user_id | string | – | User ID to exclude from selection |
No output schema declared.
No examples provided.
get_filtered_jobs_api_job_matches_get ~233
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 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| experience_level | string | – | Filter by experience level |
| job_type | string | – | Filter by job type |
| keywords | array | – | Filter by keywords |
| limit | integer | – | Maximum number of results to return |
| location | string | – | Filter by location |
| location_type | string | – | Filter by location type (remote, onsite, hybrid) |
| min_match_score | number | – | Filter by minimum match score |
| min_salary | number | – | Filter by minimum salary |
| offset | integer | – | Number of results to skip |
| resume_id | string | – | Resume ID to get matches for |
| sort_by | string | – | Field to sort by |
| sort_order | string | – | Sort order (asc or desc) |
| user_id | string | – | User ID to get matches for |
No output schema declared.
No examples provided.
get_formatted_footer_api_email_footer__user_id__formatted_get ~59
Get Formatted Footer Get formatted footer string for a 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.
get_integration_status_api_tools_status_get ~48
Get Integration Status Get the connection status for key integrations across all providers. ### 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_job_detail_api_v1_jobs__job_id__get ~77
Get Job Detail Get a detailed job listing by ID ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job ID |
No output schema declared.
No examples provided.
get_job_details_api_v1_jobs_get ~226
Get Job Details Get detailed job listings with advanced filters and pagination ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true, "personalized": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Filter by company name |
| experience_level | string | – | Filter by experience level |
| job_type | string | – | Filter by job type |
| limit | integer | – | Maximum number of jobs to return |
| location | string | – | Filter by location |
| offset | integer | – | Number of jobs to skip |
| remote | boolean | – | Filter by remote jobs |
| salary_max | number | – | Maximum salary |
| salary_min | number | – | Minimum salary |
| search | string | – | Search term for job title, company, or description |
| sort_by | string | – | Field to sort by, or 'relevance' for a personalised ranking |
| sort_order | string | – | Sort order (asc or desc) |
No output schema declared.
No examples provided.
get_lead_api_linkedin_leads__lead_id__get ~57
Get Lead Fetch a single lead by its ID. ### 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.
get_lead_outreach_history_api_linkedin_leads__lead_id__history_get ~106
Get Lead Outreach History Return the outreach thread for this lead for the current user. Returns a chronological list of events: - type=sent — initial cold email - type=follow_up — follow-up email - type=reply — recruiter reply ### 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.
get_lead_stats_api_linkedin_leads_stats_get ~48
Get Lead Stats Return summary statistics for the lead database. ### 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_least_contacted_hr_api_cold_email_least_contacted_hr_get ~138
Get Least Contacted Hr Get the least contacted HR email for a specific company. This endpoint uses the same logic as the unified email flow to select the best HR contact. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true, "hr_email": "Hr Email", "company_name": "Company Name", "total_contacts": 1 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | Name of the company to get least contacted HR for |
No output schema declared.
No examples provided.
get_least_used_sender_api_email_sender_pool_least_used_sender_get ~110
Get Least Used Sender Get the least used email sender for load balancing, considering company contact history (admin only) ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | – | Company ID to consider for contact history |
| company_name | string | – | Company name to consider for contact history |
No output schema declared.
No examples provided.
get_my_footer_api_email_footer_me_get ~46
Get My Footer Get the footer for the currently authenticated user. ### 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_notifications_api_notifications_get ~69
Get Notifications Fetch notifications for the current user. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ {} ] ```
| Name | Type | Req | Description |
|---|---|---|---|
| is_read | boolean | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_outreach_batch_api_outreach_batches__batch_id__get ~50
Get 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.
get_outreach_queue_api_outreach_queue_get ~62
Get Outreach Queue Get pending outreach queue items for the current user. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ {} ] ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pending_auto_replies_api_auto_replies_get ~65
Get Pending Auto Replies List pending auto-replies the user can still cancel. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ {} ] ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_preferences_api_job_preferences_get ~69
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 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | – | – |
No output schema declared.
No examples provided.
get_referral_code_api_referrals_code_get ~52
Get Referral Code Return the user's referral code, generating one if it doesn't exist yet. ### 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_rendercv_pdf_api_resume_rendercv_pdf_get ~62
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
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
get_rendercv_pdf_download_api_resume_rendercv_pdf_download_get ~75
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: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | – |
No output schema declared.
No examples provided.
get_resume_api_resume_get ~64
Get Resume Get the user's resume. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | – | – |
No output schema declared.
No examples provided.
get_system_stats_api_multi_tenant_monitoring_stats_get ~84
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": "System Status" } ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_tools_schema_api_tools_schema_get ~62
Get Tools Schema Returns the JSON schema for all available tools. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| use_composio | boolean | – | Whether to include Composio tools |
No output schema declared.
No examples provided.
get_user_config_api_config_user__user_id__get ~55
Get User Config Get configuration 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.
get_user_credits_api_referrals_credits_get ~53
Get User Credits Return the current user's credit balance, referral code, and total referrals. ### 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_user_memory_api_user_memory__user_id__get ~73
Get User Memory Get user memory by user ID ### 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.
get_user_memory_history_api_user_memory__user_id__history_get ~117
Get User Memory History Get user memory history (all versions) ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true, "total": 1, "page": 1, "limit": 1 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page |
| page | integer | – | Page number |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
get_user_monitoring_status_api_multi_tenant_monitoring_users__user_id__status_get ~64
Get User Monitoring Status Get monitoring status 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.
get_yaml_suggestions_api_resume_yaml_suggestions_post ~46
Get Yaml Suggestions Generate YAML-based improvement suggestions ### 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.
invite_info_api_orgs_invites__token__get ~67
Invite Info Public (pre-login) details for the join page. Unknown, used and expired all look the same. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | – |
No output schema declared.
No examples provided.
list_accounts_api_linkedin_leads_accounts_get ~51
List Accounts List all LinkedIn scraper accounts in the pool (passwords masked). ### 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_applications_api_applications_get ~195
List Applications List the current user's tracked applications, most recent first. ### 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 |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
list_companies_api_companies_get ~79
List Companies ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json [ { "hrContacts": [ { "email": "Email" } ], "hrContactCount": 1 } ] ```
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_connections_api_tools_connections_get ~46
List Connections List all active connections for the user in Composio. ### 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.
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.