HopeHire
REMOTE · HOPEHIRE.IN
Tailor resumes, score ATS fit, find hiring leads, and send cold outreach, from your agent.
Available components
Last scanned (12 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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. | DS published | 10094 | 13 | Verified |
| hopehire.in. | No DS | 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 →
update_account_status_api_linkedin_leads_accounts__account_id__status_patch ~74
Update Account Status Update the status of a LinkedIn account (active / cooldown / banned). ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
update_application_status_api_applications__application_id__status_patch ~204
Update Application Status Manually update an application's status (e.g. marking Interview/Offer/Rejected). ### 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 |
|---|---|---|---|
| application_id | string | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
update_campaign_config_api_config_campaign__campaign_id__put ~55
Update Campaign Config Update 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.
update_daily_outreach_settings_api_autopilot_settings_patch ~140
Update Daily Outreach 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 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| daily_outreach_batch_size | integer | – | – |
| daily_outreach_enabled | boolean | yes | – |
| outreach_timezone | string | – | – |
No output schema declared.
No examples provided.
update_email_footer_api_email_footer__user_id__put ~126
Update Email Footer Update email footer for a user. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| string | – | – | |
| github | string | – | – |
| string | – | – | |
| location | string | – | – |
| name | string | – | – |
| phone | string | – | – |
| portfolio | string | – | – |
| project_links | array | – | – |
| title | string | – | – |
| user_id | string | yes | – |
No output schema declared.
No examples provided.
update_extension_settings_api_extension_settings_patch ~98
Update 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 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| field_memory_consent | boolean | – | – |
| recruiter_comms_consent | boolean | – | – |
No output schema declared.
No examples provided.
update_legacy_autopilot_settings_api_autopilot_legacy_settings_patch ~116
Update Legacy Autopilot Settings Legacy job-board autopilot — not available when daily outreach is enabled. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "autopilot_enabled": true, "autopilot_min_match_score": 1.0 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| autopilot_enabled | boolean | yes | – |
| autopilot_min_match_score | number | yes | – |
No output schema declared.
No examples provided.
update_my_footer_api_email_footer_me_put ~117
Update My Footer Update the footer for the currently authenticated user. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| string | – | – | |
| github | string | – | – |
| string | – | – | |
| location | string | – | – |
| name | string | – | – |
| phone | string | – | – |
| portfolio | string | – | – |
| project_links | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
update_outreach_status_api_linkedin_leads__lead_id__outreach_patch ~102
Update Outreach Status Update the current user's outreach status for a given lead. Use this after sending a cold email so the lead is marked as contacted. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| cold_email_id | string | – | – |
| lead_id | string | yes | – |
| notes | string | – | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
update_preferences_api_job_preferences_put ~189
Update Preferences Update the user's job preferences Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| 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.
update_remembered_field_answer_api_user_memory__user_id__remembered_field_put ~141
Update Remembered Field Answer Edit one remembered application-field answer from the memory-bank UI. Same durable store the extension writes to (interaction_history, keyed by normalized label) - this just lets the user correct it directly instead of waiting to be asked the question again on some future form. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | – |
| user_id | string | yes | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
update_resume_manual_api_resume_put ~296
Update Resume Manual Update a user's resume manually and trigger PDF generation. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| achievements | array | – | – |
| certifications | array | – | – |
| cold_email_resume_source | string | – | – |
| createdAt | string | yes | – |
| education | array | yes | – |
| experience | array | yes | – |
| extracurriculars | array | – | – |
| fileName | string | – | – |
| fileSize | integer | – | – |
| fileType | string | – | – |
| id | string | yes | – |
| improvementSuggestions | array | – | – |
| jobPreferences | object | – | – |
| languages | array | – | – |
| linkedin_url | string | – | – |
| personalInfo | object | yes | – |
| positionsOfResponsibility | array | – | – |
| projects | array | – | – |
| rendercv_pdf_path | string | – | – |
| rendercv_pdf_url | string | – | – |
| rendercv_url_refreshed_at | string | – | – |
| s3Path | string | – | – |
| skills | array | yes | – |
| source | string | – | – |
| updatedAt | string | yes | – |
| userId | string | yes | – |
| yaml_content | string | – | – |
| yaml_updated_at | string | – | – |
No output schema declared.
No examples provided.
update_template_api_email_templates__template_id__put ~144
Update Template Edit a template's subject, body, or name. ### 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 } ```
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| name | string | – | – |
| subject | string | – | – |
| template_id | string | yes | – |
No output schema declared.
No examples provided.
update_user_config_api_config_user__user_id__put ~55
Update User Config Update 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.
update_user_memory_api_user_memory__user_id__put ~145
Update User Memory Update existing 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.
update_user_monitoring_config_api_multi_tenant_monitoring_users__user_id__config_put ~108
Update User Monitoring Config Update email monitoring configuration for a user ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
| Name | Type | Req | Description |
|---|---|---|---|
| email_monitoring_enabled | boolean | – | Enable/disable email monitoring |
| monitoring_frequency | integer | – | Monitoring frequency in seconds |
| priority | string | – | Priority level (low, normal, high) |
| user_id | string | yes | User ID |
No output schema declared.
No examples provided.
upload_resume_api_resume_post ~76
Upload Resume Upload and process a resume file. Requires authentication. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json **Example Response:** ```json { "success": true } ```
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | – | – |
| user_id | string | – | – |
No output schema declared.
No examples provided.
user_memory_ai_chat_api_user_memory_ai_chat_post ~40
User Memory Ai Chat ### 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.
What did VerifyMCP test on the HopeHire MCP server?
VerifyMCP ran 12 checks on HopeHire, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about HopeHire: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.