Himalayas Remote Jobs
REMOTE · MCP.HIMALAYAS.APP
Remote jobs: job search, salary data and application tracking, or post a job and hire candidates
Available components
Last scanned (22 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 21 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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (generate_application_documents). See how to fix → View diagnostics → Fail
- 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 Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 9602 tokens (~123/item across 78 items; 78 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
- Stability check failed: schema churn in the 30 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 11 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 79 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 11 Nov 26 0
- Tool “delete_company_job” rewrote its description, which is the text the model reads security
- Tool “delete_conversation” rewrote its description, which is the text the model reads security
- “delete_company_job” added an optional parameter “confirm_token” cosmetic
- “delete_conversation” added an optional parameter “confirm_token” cosmetic
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 94 to 97.
- 8 Nov 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 97 to 94.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “post_job_public” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_job_payment_status” rewrote its description, which is the text the model reads security
- Tool “create_company_job” rewrote its description, which is the text the model reads security
- Tool “get_plus_checkout_link” rewrote its description, which is the text the model reads security
- Tool “reply_to_message” rewrote its description, which is the text the model reads security
- Tool “search_talent” rewrote its description, which is the text the model reads security
- Tool “send_message” rewrote its description, which is the text the model reads security
- Tool “start_conversation” rewrote its description, which is the text the model reads security
- Tool “update_company_job” rewrote its description, which is the text the model reads security
- “reply_to_message” added an optional parameter “confirm_token” cosmetic
- “send_message” added an optional parameter “confirm_token” cosmetic
- “start_conversation” added an optional parameter “confirm_token” cosmetic
- 21 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_company_job” rewrote its description, which is the text the model reads security
- Tool “get_saved_jobs” rewrote its description, which is the text the model reads security
- Tool “search_jobs” rewrote its description, which is the text the model reads security
- Tool “search_talent” rewrote its description, which is the text the model reads security
- Tool “generate_application_documents” rewrote its description, which is the text the model reads security
- Tool “get_interview_practice_link” rewrote its description, which is the text the model reads security
- Tool “get_plus_checkout_link” rewrote its description, which is the text the model reads security
- Tool “get_remote_work_statistics” rewrote its description, which is the text the model reads security
- Tool “get_verification_link” rewrote its description, which is the text the model reads security
- Tool “join_radar_waitlist” rewrote its description, which is the text the model reads security
- Tool “submit_feedback” rewrote its description, which is the text the model reads security
- Tool “create_company_job” is now declared destructive security
- Tool “generate_application_documents” is now declared destructive security
- Tool “get_verification_link” is now declared destructive security
- Tool “import_profile” is now declared destructive security
- Tool “post_job_public” is now declared destructive security
- Tool “purchase_job_extras” is now declared destructive security
- Tool “reply_to_message” is now declared destructive security
- Tool “save_job” is now declared destructive security
- Tool “send_message” is now declared destructive security
- Tool “skip_job” is now declared destructive security
- Tool “start_conversation” is now declared destructive security
- Tool “update_account” is now declared destructive security
- Tool “update_company_job” is now declared destructive security
- Tool “update_company_profile” is now declared destructive security
- Tool “update_company_tech_stack” is now declared destructive security
- Tool “update_document” is now declared destructive security
- Tool “update_education” is now declared destructive security
- Tool “update_email_preferences” is now declared destructive security
- Tool “update_experience” is now declared destructive security
- Tool “update_job_status” is now declared destructive security
- Tool “update_profile” is now declared destructive security
- Tool “update_profile_photo” is now declared destructive security
- Tool “update_saved_answer” is now declared destructive security
- Tool “update_tech_stack” is now declared destructive security
- Tool “use_headshot_as_profile_photo” is now declared destructive security
- “search_jobs” reworded the description of “keyword” cosmetic
- “submit_feedback” reworded the description of “endpoint” cosmetic
- “submit_feedback” dropped the optional parameter “method” cosmetic
- Tool “add_company_perk” changed its title: Add company perk cosmetic
- Tool “add_education” changed its title: Add education cosmetic
- Tool “add_experience” changed its title: Add work experience cosmetic
- Tool “check_job_payment_status” changed its title: Check job payment status cosmetic
- Tool “create_company_job” changed its title: Create company job cosmetic
- Tool “delete_company_job” changed its title: Delete company job cosmetic
- Tool “delete_conversation” changed its title: Delete employer conversation cosmetic
- Tool “delete_document” changed its title: Delete resume or cover letter cosmetic
- Tool “delete_education” changed its title: Delete education cosmetic
- Tool “delete_experience” changed its title: Delete work experience cosmetic
- Tool “delete_saved_answer” changed its title: Delete saved application answer cosmetic
- Tool “generate_application_documents” changed its title: Tailor resume and cover letter cosmetic
- Tool “get_apply_link” changed its title: Get apply link cosmetic
- Tool “get_billing_portal_link” changed its title: Get billing portal link cosmetic
- Tool “get_coach_chat” changed its title: Get career coach chat cosmetic
- Tool “get_companies” changed its title: Browse remote companies cosmetic
- Tool “get_company_details” changed its title: Get company details cosmetic
- Tool “get_company_perks” changed its title: Get company perks cosmetic
- Tool “get_company_profile” changed its title: Get company profile cosmetic
- Tool “get_conversation” changed its title: Get employer conversation cosmetic
- Tool “get_correct_country_name” changed its title: Resolve country name cosmetic
- Tool “get_document” changed its title: Get resume or cover letter cosmetic
- Tool “get_headshots_link” changed its title: Get headshots link cosmetic
- Tool “get_interview_practice_link” changed its title: Get interview practice link cosmetic
- Tool “get_interview_results” changed its title: Get interview practice results cosmetic
- Tool “get_job_details” changed its title: Get job details cosmetic
- Tool “get_jobs” changed its title: Browse remote jobs cosmetic
- Tool “get_my_conversation” changed its title: Get inbox conversation cosmetic
- Tool “get_my_profile” changed its title: Get my profile cosmetic
- Tool “get_new_matches” changed its title: Get new job matches cosmetic
- Tool “get_plus_checkout_link” changed its title: Get Himalayas Plus checkout link cosmetic
- Tool “get_related_jobs” changed its title: Get related jobs cosmetic
- Tool “get_remote_work_statistics” changed its title: Get remote work statistics cosmetic
- Tool “get_salary_data” changed its title: Get salary data cosmetic
- Tool “get_saved_jobs” changed its title: Get saved jobs cosmetic
- Tool “get_talent_profile” changed its title: Get talent profile cosmetic
- Tool “get_verification_link” changed its title: Get ID verification link cosmetic
- Tool “import_profile” changed its title: Import profile from LinkedIn or resume cosmetic
- Tool “join_radar_waitlist” changed its title: Join Radar waitlist cosmetic
- Tool “list_coach_chats” changed its title: List career coach chats cosmetic
- Tool “list_company_jobs” changed its title: List company jobs cosmetic
- Tool “list_conversations” changed its title: List employer conversations cosmetic
- Tool “list_documents” changed its title: List resumes and cover letters cosmetic
- Tool “list_headshots” changed its title: List headshots cosmetic
- Tool “list_interviews” changed its title: List interview practice cosmetic
- Tool “list_my_conversations” changed its title: List my inbox cosmetic
- Tool “list_notifications” changed its title: List notifications cosmetic
- Tool “list_saved_answers” changed its title: List saved application answers cosmetic
- Tool “mark_message_read” changed its title: Mark employer message read cosmetic
- Tool “mark_my_message_read” changed its title: Mark inbox message read cosmetic
- Tool “mark_notifications_read” changed its title: Mark notifications read cosmetic
- Tool “post_job_public” changed its title: Post a paid job without an account cosmetic
- Tool “purchase_job_extras” changed its title: Purchase job extras cosmetic
- Tool “remove_company_perk” changed its title: Remove company perk cosmetic
- Tool “remove_saved_job” changed its title: Remove saved job cosmetic
- Tool “reply_to_message” changed its title: Reply in inbox cosmetic
- Tool “save_job” changed its title: Save job to tracker cosmetic
- Tool “search_companies” changed its title: Search remote companies cosmetic
- Tool “search_jobs” changed its title: Search remote jobs cosmetic
- Tool “search_talent” changed its title: Search talent cosmetic
- Tool “send_message” changed its title: Send message to candidate cosmetic
- Tool “show_company_job” changed its title: Get company job cosmetic
- Tool “skip_job” changed its title: Skip job cosmetic
- Tool “start_conversation” changed its title: Start conversation with candidate cosmetic
- Tool “submit_feedback” changed its title: Send feedback to Himalayas cosmetic
- Tool “update_account” changed its title: Update account time zone cosmetic
- Tool “update_company_job” changed its title: Update company job cosmetic
- Tool “update_company_profile” changed its title: Update company profile cosmetic
- Tool “update_company_tech_stack” changed its title: Update company tech stack cosmetic
- Tool “update_document” changed its title: Update resume or cover letter cosmetic
- Tool “update_education” changed its title: Update education cosmetic
- Tool “update_email_preferences” changed its title: Update email preferences cosmetic
- Tool “update_experience” changed its title: Update work experience cosmetic
- Tool “update_job_status” changed its title: Update job status cosmetic
- Tool “update_profile” changed its title: Update profile cosmetic
- Tool “update_profile_photo” changed its title: Update profile photo cosmetic
- Tool “update_saved_answer” changed its title: Update saved application answer cosmetic
- Tool “update_tech_stack” changed its title: Update profile tech stack cosmetic
- Tool “use_headshot_as_profile_photo” changed its title: Use headshot as profile photo cosmetic
- 20 Oct 26 0
- Tool “get_plus_checkout_link” rewrote its description, which is the text the model reads security
- Tool “get_talent_profile” rewrote its description, which is the text the model reads security
- Tool “search_talent” rewrote its description, which is the text the model reads security
- New tool “get_verification_link” functional
- 19 Oct 26 0
First indexed and scored.
- New tool “delete_document”, which the server declares destructive security
- New tool “delete_education”, which the server declares destructive security
- New tool “delete_experience”, which the server declares destructive security
- New tool “delete_saved_answer”, which the server declares destructive security
- Tool “generate_application_documents” rewrote its description, which is the text the model reads security
- Tool “get_plus_checkout_link” rewrote its description, which is the text the model reads security
- Tool “send_message” rewrote its description, which is the text the model reads security
- Tool “start_conversation” rewrote its description, which is the text the model reads security
- Tool “update_job_status” rewrote its description, which is the text the model reads security
- Tool “update_tech_stack” rewrote its description, which is the text the model reads security
- Schema quality: 5276 → 8771 ▼ functional
- New tool “get_billing_portal_link” functional
- New tool “get_coach_chat” functional
- New tool “get_document” functional
- New tool “get_headshots_link” functional
- New tool “get_interview_practice_link” functional
- New tool “get_interview_results” functional
- New tool “get_my_conversation” functional
- New tool “get_new_matches” functional
- New tool “import_profile” functional
- New tool “join_radar_waitlist” functional
- New tool “list_coach_chats” functional
- New tool “list_documents” functional
- New tool “list_headshots” functional
- New tool “list_interviews” functional
- New tool “list_my_conversations” functional
- New tool “list_notifications” functional
- New tool “list_saved_answers” functional
- New tool “mark_my_message_read” functional
- New tool “mark_notifications_read” functional
- “update_job_status” added an optional parameter “detail” cosmetic
- “update_job_status” added an optional parameter “reason” cosmetic
- “update_profile” added an optional parameter “behance” cosmetic
- “update_profile” added an optional parameter “career_company_size” cosmetic
- “update_profile” added an optional parameter “career_compensation” cosmetic
- “update_profile” added an optional parameter “career_interested_role_list” cosmetic
- “update_profile” added an optional parameter “career_salary_country” cosmetic
- “update_profile” added an optional parameter “career_skill_list” cosmetic
- “update_profile” added an optional parameter “career_working_permits” cosmetic
- “update_profile” added an optional parameter “contact_email” cosmetic
- “update_profile” added an optional parameter “dribbble” cosmetic
- “update_profile” added an optional parameter “email_visible” cosmetic
- “update_profile” added an optional parameter “first_name” cosmetic
- “update_profile” added an optional parameter “github” cosmetic
- “update_profile” added an optional parameter “last_name” cosmetic
- “update_profile” added an optional parameter “linkedin” cosmetic
- “update_profile” added an optional parameter “portfolio” cosmetic
- “update_profile” added an optional parameter “seniority” cosmetic
- “update_profile” added an optional parameter “twitter” cosmetic
- “update_profile” added an optional parameter “username” cosmetic
- “update_profile” added an optional parameter “visibility” cosmetic
- “update_profile” added an optional parameter “website” cosmetic
- “search_jobs” reworded the description of “currency” cosmetic
- “search_jobs” reworded the description of “salary_max” cosmetic
- “search_jobs” reworded the description of “salary_min” cosmetic
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 21 Nov 2026 · Probed https://mcp.himalayas.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=himalayas.app | CN=WE1,O=Google Trust Services,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 84d054f5115379540ecccff3d50e492f |
| SANs: himalayas.app, mcp.himalayas.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.himalayas.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| himalayas.app. | 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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.himalayas.app/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.himalayas.app/mcp | HTTPS enforced | 301 | https://mcp.himalayas.app/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 →
mark_notifications_read Mark notifications read ~69
Mark one of the user's Himalayas notifications as read by id, or all of them with all: true. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | true marks every notification as read |
| id | number | – | Notification id from list_notifications |
No output schema declared.
No examples provided.
purchase_job_extras Purchase job extras ~89
Purchase paid extras for an existing job posting: sticky ($299), newsletter ($99). Returns a Stripe checkout URL. Uses the connected Himalayas employer account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| extras | array | yes | Extras to purchase: 'sticky' ($299 pin to top), 'newsletter' ($99 weekly email feature) |
| job_slug | string | yes | Job slug to add extras to |
No output schema declared.
No examples provided.
remove_company_perk Remove company perk ~58
Remove a perk/benefit from your company on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Perk ID to remove (use get_company_perks to find IDs) |
No output schema declared.
No examples provided.
remove_saved_job Remove saved job ~43
Remove a job from your application tracker. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | Kanban item ID to remove |
No output schema declared.
No examples provided.
reply_to_message Reply in inbox ~170
Send a reply in a conversation in the user's job seeker inbox. Sending takes two calls: without confirm_token nothing is sent, and the reply is a preview of the exact text with a confirm_token; calling again with the same message and that token sends it. The company reads it as coming from the user and it can't be unsent, so show the user the preview and get their OK before the second call. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | – | Leave out to get a preview; nothing is sent. Pass the token from that preview, with the same message, to send it |
| message | string | yes | The reply, exactly as the user approved it |
| room_name | string | yes | Room name from list_my_conversations |
No output schema declared.
No examples provided.
save_job Save job to tracker ~150
Save a job to your application tracker. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| app_link | string | – | Application link URL |
| base_salary | number | – | Base salary |
| company_name | string | yes | Company name |
| currency | string | – | Salary currency (e.g., 'USD') |
| excitement | number | – | Excitement level from 0-5 |
| himalayas_link | string | – | Himalayas job listing URL |
| max_salary | number | – | Maximum salary |
| notes | string | – | Personal notes about this job |
| status | string | – | Application status (default: saved) |
| title | string | yes | Job title |
No output schema declared.
No examples provided.
search_companies Search remote companies ~171
Search for remote-friendly companies using keywords with optional country filtering
| Name | Type | Req | Description |
|---|---|---|---|
| benefits | string | – | Comma-separated benefit slugs to filter by (e.g., '401k,health-insurance,equity') |
| country | string | – | Filter companies by country (e.g., 'Canada', 'United States', 'UK') |
| keyword | string | – | Search keyword/term (optional) |
| page | integer | – | Page number for pagination (starts at 1) |
| sort | string | – | Sort order for results (default: 'relevant') |
| tech_stack | string | – | Comma-separated technology slugs to filter by (e.g., 'react,typescript,python') |
| worldwide | boolean | – | Show only companies with 100% remote jobs available worldwide (overrides country filter) |
No output schema declared.
No examples provided.
search_jobs Search remote jobs ~499
Search remote job listings on Himalayas by job title, role, skill or keyword, filtered by the countries a job is open to, worldwide availability, seniority, employment type, salary, markets, benefits or companies. Each result has the company, title, salary range when listed, the countries the job is open to, the posting date and the slugs for get_job_details.
| Name | Type | Req | Description |
|---|---|---|---|
| benefits | string | – | Comma-separated benefit slugs to filter by (e.g., '401k,health-insurance,equity') |
| companies | string | – | Comma-separated company slugs to filter by (e.g., 'stripe,gitlab') |
| country | string | – | Filter jobs by country (e.g., 'Canada', 'United States', 'UK') |
| currency | string | – | Salary currency (default: USD). salary_min and salary_max are always USD; this doesn't convert them. |
| exclude_worldwide | boolean | – | When true and country is set, return ONLY jobs specifically available in that country, excluding worldwide/remote jobs. Requires country to be set. |
| experience | string | – | Filter by a single experience/seniority level (entry-level, mid-level, senior, manager, director, or executive) |
| keyword | string | – | Job title, role or skill to search for, e.g. 'product manager' or 'react' (optional) |
| markets | string | – | Comma-separated market/category slugs to filter by (e.g., 'saas,fintech,healthcare') |
| page | integer | – | Page number for pagination (starts at 1) |
| salary_max | number | – | Maximum yearly pay in USD, compared the same way as salary_min |
| salary_min | number | – | Minimum yearly pay in USD. Hourly, weekly and monthly pay is converted to a yearly figure first (hourly x 2080), so hourly jobs whose yearly equivalent clears it are included. |
| salary_required | boolean | – | If false, include jobs without salary data in salary-filtered results (default: true — only jobs with salary) |
| sort | string | – | Sort order for results (default: 'relevant') |
| type | string | – | Filter by a single employment type (full-time, part-time, contractor, temporary, intern, volunteer, or other) |
| worldwide | boolean | – | Show ONLY 100% remote jobs available worldwide (overrides country filter) |
No output schema declared.
No examples provided.
search_talent Search talent ~172
Search remote candidates and talent on Himalayas to hire or recruit, such as developers, designers or marketers, by skill, job title or keyword and country. Each result has the candidate's current role, salary expectation, job search status and the profile link for get_talent_profile. Results here have no paid placement: they are ordered by relevance or recency only, and Himalayas Plus or verified candidates rank like everyone else. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Filter by country (e.g., 'United States', 'Germany') |
| keyword | string | – | Search keyword (e.g., 'react developer') |
| page | integer | – | Page number for pagination (starts at 1) |
| sort | string | – | Sort order (default: relevant) |
No output schema declared.
No examples provided.
send_message Send message to candidate ~213
Send a message in an existing conversation. Accepts room_name (from list_conversations) or talent_slug (from search_talent). Use start_conversation first if no conversation exists yet. Sending takes two calls: without confirm_token nothing is sent, and the reply is a preview of the exact text with a confirm_token; calling again with the same message and that token sends it. The candidate reads it as coming from the user's company and it can't be unsent, so show the user the preview and get their OK before the second call. Uses the connected Himalayas employer account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | – | Leave out to get a preview; nothing is sent. Pass the token from that preview, with the same message, to send it |
| message | string | yes | Message text to send |
| room_name | string | – | Room name from list_conversations |
| talent_slug | string | – | Talent slug (from search_talent results) — resolves to room name automatically |
No output schema declared.
No examples provided.
show_company_job Get company job ~52
Get full details of one of your company's job postings on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| job_slug | string | yes | Job slug (from list_company_jobs) |
No output schema declared.
No examples provided.
skip_job Skip job ~156
Record that the user is passing on a Himalayas job, with the reason, so it stops coming back in get_new_matches and future matches can learn from it. job_closed also reports the listing as expired. For a job already in the tracker, use update_job_status with outcome didnt_apply instead. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| company_slug | string | yes | Company slug (from the job listing URL) |
| detail | string | – | Anything worth knowing, in a sentence or two (what the page said, a hidden requirement). No personal data. |
| job_slug | string | yes | Job slug (from the job listing URL) |
| reason | string | yes | Why the user is passing on it |
No output schema declared.
No examples provided.
start_conversation Start conversation with candidate ~208
Start a conversation with a candidate by talent slug, optionally with a first message. If the conversation already exists, returns it. Use search_talent to find candidates first, then use their slug here. A first message takes two calls: without confirm_token nothing is created or sent, and the reply is a preview of the exact text with a confirm_token; calling again with the same message and that token sends it. The candidate reads it as coming from the user's company and it can't be unsent, so show the user the preview and get their OK before the second call. Uses the connected Himalayas employer account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_token | string | – | Leave out to get a preview; nothing is sent. Pass the token from that preview, with the same message, to send it |
| message | string | – | Optional initial message to send with the conversation |
| talent_slug | string | yes | Talent slug of the candidate to message (from search_talent results) |
No output schema declared.
No examples provided.
submit_feedback Send feedback to Himalayas ~316
Send a problem report about Himalayas to its engineering team: a missing capability (filter, field, tool), unclear or wrong documentation, a surprising response, an unhelpful error, a bug, a blocked page or action, or impractical performance. Describe the goal, what got in the way and, if known, a suggested fix. Fill `agent` with the client's name and model. Reports must not contain credentials, personal data or the user's private content.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | object | – | Who is reporting: name (agent or product) and model |
| endpoint | string | – | The Himalayas tool involved, e.g. search_jobs |
| evidence | object | – | Sanitized details of the failing call, with no credentials or personal data |
| expected | string | – | What you expected to find or happen |
| goal | string | yes | What you or your user were trying to accomplish, in plain language |
| message | string | yes | What prevented or complicated the task |
| metadata | object | – | – |
| outcome | string | – | blocked = task failed, degraded = completed worse or slower, completed = suggestion only |
| request_id | string | – | – |
| session_id | string | – | Reuse the same value for every report in one task |
| suggestion | string | – | A concrete change that would have let you succeed |
| type | string | yes | The kind of problem |
| workaround | boolean | – | Whether you found a workaround |
| workaround_description | string | – | The workaround, if any |
No output schema declared.
No examples provided.
update_account Update account time zone ~79
Change the user's account time zone (used for email timing). Name is on update_profile; email address and password can only be changed on himalayas.app. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| time_zone | string | yes | Time zone name, e.g. 'Pacific Time (US & Canada)' or 'London' |
No output schema declared.
No examples provided.
update_company_job Update company job ~288
Update an existing job posting on Himalayas. Only provide fields you want to change. For screening_questions, provide the full set — questions not included will be removed. Editing is free. If the job has paid extras (sticky or newsletter, chosen earlier) that aren't paid yet, the reply is a Stripe checkout link for them, which the user opens and pays themselves; nothing is charged otherwise. Uses the connected Himalayas employer account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| app_link_or_email | string | – | Application URL or email address |
| base_salary | number | – | Minimum salary |
| category_list | string | – | Comma-separated job categories |
| description | string | – | Job description (350+ characters, can include HTML) |
| draft | boolean | – | Save as draft instead of submitting for approval |
| employment_type | string | – | Employment type |
| job_slug | string | yes | Job slug to update |
| max_salary | number | – | Maximum salary |
| salary_country | string | – | Salary currency code |
| screening_questions | array | – | Screening questions — provide full set, questions not included will be removed |
| seniority | array | – | Seniority levels |
| skill_list | string | – | Comma-separated skills |
| title | string | – | Job title (5-80 characters) |
| valid_through | string | – | Expiration date (ISO format) |
No output schema declared.
No examples provided.
update_company_profile Update company profile ~154
Update your company's profile on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| about | string | – | Company description (HTML or plain text) |
| ceo | string | – | CEO name |
| string | – | Facebook URL | |
| string | – | Instagram URL | |
| string | – | LinkedIn URL | |
| location_list | string | – | Comma-separated list of locations (e.g., 'San Francisco, New York') |
| num_employees_range | string | – | Number of employees range |
| summary | string | – | Short company summary |
| string | – | Twitter URL | |
| year_founded | number | – | Year the company was founded |
No output schema declared.
No examples provided.
update_company_tech_stack Update company tech stack ~85
Update your company's tech stack on Himalayas. Pass technology names (e.g., 'React', 'Python') and they'll be matched to the Himalayas stack database. Uses the connected Himalayas employer account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| stacks | array | yes | Array of technology names (e.g., ['React', 'TypeScript', 'Python', 'AWS']) |
No output schema declared.
No examples provided.
update_document Update resume or cover letter ~99
Rename a tailored resume or cover letter, or replace a cover letter's text. Resume content is edited in the website's resume editor (link from list_documents). Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Cover letters only: the full new text, paragraphs separated by blank lines |
| id | – | yes | Document id or slug |
| title | string | – | New title |
| type | string | yes | – |
No output schema declared.
No examples provided.
update_education Update education ~143
Edit an education entry on your Himalayas profile by id (get_my_profile lists the ids). Only the fields you pass change. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| activities | string | – | – |
| current | boolean | – | Currently enrolled |
| degree | string | – | – |
| description | string | – | – |
| end_year | number | – | – |
| field | string | – | Field of study |
| grade | string | – | – |
| id | number | yes | Education id |
| school | string | – | – |
| sort_order | number | – | Position on the profile, 0 first |
| start_year | number | – | – |
No output schema declared.
No examples provided.
update_email_preferences Update email preferences ~187
Turn Himalayas emails on or off for the user. Only the settings you pass change. Daily job-match emails are a Plus feature; free accounts get weekly. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| application_followups | boolean | – | 'Did you hear back?' emails about applications |
| job_match_frequency | string | – | How often job-match emails come (daily needs Plus) |
| job_matches | boolean | – | Emails with new jobs that match the profile |
| job_post_reminders | boolean | – | Reminders about jobs they posted (employers) |
| job_post_updates | boolean | – | Updates about jobs they posted (employers) |
| job_reminders | boolean | – | Reminders about saved jobs |
| marketing_emails | boolean | – | Himalayas news and offers |
| message_notifications | boolean | – | Emails when an employer messages them |
No output schema declared.
No examples provided.
update_experience Update work experience ~190
Edit a work experience on your Himalayas profile by id (get_my_profile lists the ids). Only the fields you pass change. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | – | Company name |
| current_job | boolean | – | Whether this is the current job |
| description | string | – | Description of the role |
| employment_type | string | – | – |
| end_date | string | – | End date (YYYY-MM-DD) |
| experience_skill_list | array | – | Skills used in this role. Replaces the current list. |
| id | number | yes | Experience id |
| location | string | – | Country name for this role. Cities are not accepted. |
| sort_order | number | – | Position on the profile, 0 first |
| start_date | string | – | Start date (YYYY-MM-DD) |
| title | string | – | Job title |
No output schema declared.
No examples provided.
update_job_status Update job status ~242
Update a saved job's status, outcome or details. Use status for where the application is now (interviewing, negotiation for an offer, hired). Use outcome for an applied job that ended without progressing: rejected, no_response (no reply after 45+ days), withdrawn, or didnt_apply; status stays as it is. With didnt_apply, give a reason: job_closed reports the listing as expired, and the rest improve the user's future matches. Add detail for anything worth knowing (what the page said, a hidden requirement). Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Anything worth knowing about the outcome, in a sentence or two. No personal data. |
| excitement | number | – | Excitement level from 0-5 |
| id | number | yes | Kanban item ID |
| notes | string | – | Updated notes |
| outcome | string | – | What happened after applying, as reported by the user. "clear" removes a recorded outcome. |
| reason | string | – | Why the user didn't apply (only with outcome didnt_apply) |
| status | string | – | New application status |
No output schema declared.
No examples provided.
update_profile Update profile ~576
Update your Himalayas profile. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| behance | string | – | Behance profile URL |
| bio | string | – | Short bio |
| career_base_salary | number | – | Desired minimum salary |
| career_company_size | object | – | Company size preferences, e.g. {'1-10': 'not_interested', '51-200': 'preferred'}. Replaces all current size preferences, so include every size the user cares about. |
| career_compensation | string | – | How the user feels about equity as part of pay |
| career_description | string | – | Description of what you're looking for |
| career_interested_role_list | array | – | Other roles the user is interested in. Replaces the current list. |
| career_max_salary | number | – | Desired maximum salary |
| career_primary_role | string | – | Primary role (e.g., 'software-engineer') |
| career_salary_country | string | – | Currency of the desired salary |
| career_search_status | string | – | Career search status (e.g., 'actively_searching', 'open_to_roles', 'closed_to_roles') |
| career_skill_list | array | – | Skills for job matching (e.g. ['Product design', 'User research']). Replaces the current list. |
| career_working_permits | array | – | Countries the user can legally work in, as country names (e.g. ['United States']). Replaces the current list. |
| contact_email | string | – | Email shown to employers, if different from the login email |
| dribbble | string | – | Dribbble profile URL |
| email_visible | boolean | – | Show the contact email on the profile |
| first_name | string | – | First name, as shown on the profile and tailored resumes |
| github | string | – | GitHub profile URL |
| intro | string | – | Introduction/headline |
| last_name | string | – | Last name |
| string | – | LinkedIn profile URL | |
| location | string | – | Country name (e.g. 'United States', 'Australia'). Cities and 'City, Country' strings are not accepted. |
| portfolio | string | – | Portfolio URL |
| seniority | array | – | Seniority levels the user wants. Replaces the current list. |
| string | – | Twitter/X profile URL | |
| username | string | – | New username: 3 to 30 letters, numbers, dashes or underscores. The profile moves to himalayas.app/@username and the old link stops working. |
| visibility | string | – | public_profile: employers can find and view it. unsearchable_profile: viewable by link but not in search. private_profile: only the user sees it. |
| website | string | – | Personal website URL |
No output schema declared.
No examples provided.
update_profile_photo Update profile photo ~75
Set the user's profile photo (avatar) or profile cover photo from an image URL (https, JPEG/PNG/WebP/GIF, up to 5 MB). Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| image_url | string | yes | https URL of the image |
| kind | string | yes | – |
No output schema declared.
No examples provided.
update_saved_answer Update saved application answer ~66
Change the text of one of the user's saved application answers, by id from list_saved_answers. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The full new answer |
| id | number | yes | Saved answer id from list_saved_answers |
No output schema declared.
No examples provided.
update_tech_stack Update profile tech stack ~88
Set the tools and technologies on your Himalayas profile, replacing the current list. Names are matched to Himalayas' catalogue; any it doesn't have yet are requested for review and left off for now. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| stacks | array | yes | Array of technology names (e.g., ['React', 'TypeScript', 'Node.js']) |
No output schema declared.
No examples provided.
use_headshot_as_profile_photo Use headshot as profile photo ~80
Set one of the user's finished AI headshots as their Himalayas profile photo, by session id and image id from list_headshots. Uses the connected Himalayas account; no extra sign-in needed.
| Name | Type | Req | Description |
|---|---|---|---|
| image_id | number | yes | Image id from list_headshots |
| session_id | number | yes | Session id from list_headshots |
No output schema declared.
No examples provided.
How do I install the Himalayas Remote Jobs MCP server?
Himalayas Remote Jobs is a hosted endpoint at https://mcp.himalayas.app/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 · mcp.himalayas.app
claude mcp add --transport http app-himalayas-mcp 'https://mcp.himalayas.app/mcp'
What is the Himalayas Remote Jobs MCP server?
Himalayas Remote Jobs is an MCP server listed in the public MCP registry as app.himalayas/mcp. Remote jobs: job search, salary data and application tracking, or post a job and hire candidates. This page covers its hosted endpoint (https://mcp.himalayas.app/mcp).
Is the Himalayas Remote Jobs MCP server safe to use?
Himalayas Remote Jobs scores 82 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 Himalayas Remote Jobs MCP server expose?
Himalayas Remote Jobs exposes 78 tools: get_jobs, search_jobs, get_job_details, get_apply_link, generate_application_documents, and 73 more. Their descriptions and schemas cost roughly 9,294 tokens of context every time the server is loaded.
Does the Himalayas Remote Jobs MCP server require authentication?
No. We connected to Himalayas Remote Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Himalayas Remote Jobs MCP server still maintained?
Himalayas Remote Jobs is still listed as active in the MCP registry. We last reached this channel on 21 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 Himalayas Remote Jobs MCP server?
VerifyMCP ran 13 checks on Himalayas Remote Jobs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.