Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Himalayas Remote Jobs

REMOTE · MCP.HIMALAYAS.APP

Remote jobs: job search, salary data and application tracking, or post a job and hire candidates

0 this week 82 Trust /100

Last scanned (21 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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
Transport & Reachability100
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
What we tested

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 →

Changelog

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
Diagnostics

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
MCP tools · 78 exposed · ~9,294 tokens

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 →

Tool Tokens
add_company_perk ~77

Add a perk/benefit to your company on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.

NameTypeReqDescription
categorystringyesPerk category
descriptionstringyesPerk description (15-450 characters)
titlestringyesPerk title (3-50 characters)

No output schema declared.

No examples provided.

add_education ~143

Add an education entry to your Himalayas profile. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
activitiesstring–Activities and societies
currentboolean–Whether you are currently enrolled
degreestring–Degree (e.g., 'Bachelor of Science')
descriptionstring–Description or achievements
end_yearnumber–End year (omit if currently enrolled)
fieldstring–Field of study (e.g., 'Computer Science')
gradestring–Grade or GPA
schoolstringyesSchool or institution name
start_yearnumber–Start year

No output schema declared.

No examples provided.

add_experience ~167

Add a work experience to your Himalayas profile. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
company_namestringyesCompany name
current_jobboolean–Whether this is your current job
descriptionstringyesDescription of your role and responsibilities
employment_typestringyesEmployment type
end_datestring–End date (YYYY-MM-DD format, omit for current role)
experience_skill_liststring–Comma-separated skills used in this role
locationstring–Country name for this role (e.g. 'United States', 'Germany'). Cities are not accepted.
start_datestring–Start date (YYYY-MM-DD format)
titlestringyesJob title

No output schema declared.

No examples provided.

check_job_payment_status ~56

Check the payment status of a job posting. Use the session_id returned from create_company_job, update_company_job or purchase_job_extras with extras. No authentication required.

NameTypeReqDescription
session_idstringyesStripe checkout session ID

No output schema declared.

No examples provided.

create_company_job ~335

Post a remote job on Himalayas for the user's company, to hire remote staff. Posting a job is free; it needs admin approval before going live, and can also be saved as a draft. The optional extras are paid: sticky ($299) and newsletter ($99). With any extras, the reply is a Stripe checkout link the user opens and pays themselves, and the job doesn't go live until that payment completes; without extras nothing is charged. Uses the connected Himalayas employer account; no extra sign-in needed.

NameTypeReqDescription
app_link_or_emailstringyesApplication URL or email address — backend auto-detects via @ check
base_salarynumber–Minimum salary
category_liststring–Comma-separated job categories
descriptionstringyesJob description (350+ characters, can include HTML)
draftboolean–Save as draft instead of submitting for approval
employment_typestringyesEmployment type
extrasarray–Paid extras: 'sticky' ($299 pin to top for 30 days), 'newsletter' ($99 feature in weekly email for 30 days)
max_salarynumber–Maximum salary
salary_countrystring–Salary currency code (default: USD)
screening_questionsarray–Screening questions for applicants
seniorityarrayyesSeniority levels
skill_liststring–Comma-separated skills
titlestringyesJob title (5-80 characters)
valid_throughstring–Expiration date (ISO format, defaults to 30 days from now)

No output schema declared.

No examples provided.

delete_company_job ~144

Delete a job posting from your company on Himalayas. This action cannot be undone, and any paid extras on the posting go with it. Deleting takes two calls: without confirm_token nothing is deleted, and the reply shows the posting with a confirm_token; calling again with the same job_slug and that token deletes it. Show the user the posting and get their OK before the second call. Uses the connected Himalayas employer account; no extra sign-in needed.

NameTypeReqDescription
confirm_tokenstring–Leave out to see what would be deleted; nothing is deleted. Pass the token from that reply to delete it
job_slugstringyesJob slug to delete

No output schema declared.

No examples provided.

delete_conversation ~182

Delete a conversation with a candidate. Accepts room_name or talent_slug. The conversation and all its messages are deleted for everyone in it, including the candidate, and this can't be undone. Deleting takes two calls: without confirm_token nothing is deleted, and the reply shows the conversation with a confirm_token; calling again with the same room_name or talent_slug and that token deletes it. Show the user the conversation and get their OK before the second call. Uses the connected Himalayas employer account; no extra sign-in needed.

NameTypeReqDescription
confirm_tokenstring–Leave out to see what would be deleted; nothing is deleted. Pass the token from that reply to delete it
room_namestring–Room name from list_conversations
talent_slugstring–Talent slug (from search_talent results) — resolves to room name automatically

No output schema declared.

No examples provided.

delete_document ~59

Delete one of the user's tailored resumes or cover letters. This can't be undone: confirm with the user first. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
id–yesDocument id or slug
typestringyes–

No output schema declared.

No examples provided.

delete_education ~59

Delete an education entry from your Himalayas profile by id. This can't be undone: confirm with the user first. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
idnumberyesEducation id, from get_my_profile

No output schema declared.

No examples provided.

delete_experience ~59

Delete a work experience from your Himalayas profile by id. This can't be undone: confirm with the user first. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
idnumberyesExperience id, from get_my_profile

No output schema declared.

No examples provided.

delete_saved_answer ~56

Delete one of the user's saved application answers. This can't be undone: confirm with the user first. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
idnumberyesSaved answer id from list_saved_answers

No output schema declared.

No examples provided.

generate_application_documents ~168

Write a resume and cover letter tailored to a Himalayas job, from the user's Himalayas profile. Use it when the user's CV is generic, they have no cover letter, or an application form asks for one. They are saved to the user's account, where the user can edit them and download a PDF. A free account gets one tailored resume and one cover letter in total; Himalayas Plus includes them for every job. Uses the connected Himalayas account; no extra sign-in needed. Use the company_slug and job_slug from job listings.

NameTypeReqDescription
company_slugstringyesCompany slug (from the job listing URL or company page)
documentsarray–Which documents to write (default: both)
job_slugstringyesJob slug (from the job listing URL)

No output schema declared.

No examples provided.

get_apply_link ~96

Get the employer's application link for a job, once the user has decided to apply. Uses the connected Himalayas account (no extra sign-in needed); limited to 50 links per account per day. Use the company_slug and job_slug from job listings.

NameTypeReqDescription
company_slugstringyesCompany slug (from the job listing URL or company page)
job_slugstringyesJob slug (from the job listing URL)

No output schema declared.

No examples provided.

get_billing_portal_link ~69

Get a link to the user's Stripe billing page, where they can update their card, see invoices, or change or cancel Himalayas Plus themselves. Only for users who have paid before. Never act on billing for them. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_coach_chat ~55

Read one of the user's career coach conversations by slug from list_coach_chats. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
slugstringyesChat slug from list_coach_chats

No output schema declared.

No examples provided.

get_companies ~85

Browse remote-friendly companies with optional filtering by country or worldwide availability

NameTypeReqDescription
countrystring–Filter companies by country (e.g., 'Canada', 'United States', 'UK')
pageinteger–Page number for pagination (starts at 1)
worldwideboolean–Show only companies with 100% remote jobs available worldwide (overrides country filter)

No output schema declared.

No examples provided.

get_company_details ~50

Get full details for a company including about, tech stack, benefits, open positions, and social links

NameTypeReqDescription
company_slugstringyesCompany slug (e.g., 'stripe', 'gitlab')

No output schema declared.

No examples provided.

get_company_perks ~35

Get your company's perks/benefits on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_company_profile ~31

Get your company's profile on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_conversation ~76

Get full message history for a conversation. Accepts room_name or talent_slug. Uses the connected Himalayas employer account; no extra sign-in needed.

NameTypeReqDescription
room_namestring–Room name from list_conversations
talent_slugstring–Talent slug (from search_talent results) — resolves to room name automatically

No output schema declared.

No examples provided.

get_correct_country_name ~48

Resolve a country name to the correct format accepted by Himalayas filters. Useful for fuzzy matching user input.

NameTypeReqDescription
country_stringstringyesThe country name to get the correct name for

No output schema declared.

No examples provided.

get_document ~54

Read one of the user's tailored resumes or cover letters by id (from list_documents). Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
id–yesDocument id or slug
typestringyes–

No output schema declared.

No examples provided.

get_headshots_link ~42

Get the Himalayas page where the user makes AI headshots from a few photos of themselves. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_interview_practice_link ~215

Get the Himalayas page where the user practises interviewing for a specific job: a Himalayas job (company_slug and job_slug) or a job elsewhere (application_link). On that page the user has a live spoken mock interview with an AI interviewer playing the company's hiring manager, with questions built from the job and their profile, then gets a score out of 100 with what went well and what to improve (sessions of 90 seconds or more are scored). Sessions and scores are saved to the account, so the user can see how they improve over time (list_interviews, get_interview_results). Free accounts include one text mock interview; spoken interviews are part of Himalayas Plus (30 minutes a month). Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
application_linkstring–https link to a job posted somewhere else
company_slugstring–Company slug of a Himalayas job
job_slugstring–Job slug of a Himalayas job

No output schema declared.

No examples provided.

get_interview_results ~120

Get the scores and feedback from the user's interview practice for one job: each answer's rating and feedback, and for voice sessions the overall score, what went well, what to improve, next steps and length. Pass the interview id from list_interviews, or the job's company_slug and job_slug. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
company_slugstring–Company slug of the job
idnumber–Interview id from list_interviews
job_slugstring–Job slug

No output schema declared.

No examples provided.

get_job_details ~82

Get full details for a specific job including description, requirements and salary. Use the company_slug and job_slug from job listings. To get the employer's application link, call get_apply_link.

NameTypeReqDescription
company_slugstringyesCompany slug (from the job listing URL or company page)
job_slugstringyesJob slug (from the job listing URL)

No output schema declared.

No examples provided.

get_jobs ~84

Browse the latest remote job listings with optional filtering by country or worldwide availability

NameTypeReqDescription
countrystring–Filter jobs by country (e.g., 'Canada', 'United States', 'UK')
pageinteger–Page number for pagination (starts at 1)
worldwideboolean–Show ONLY 100% remote jobs available worldwide (overrides country filter)

No output schema declared.

No examples provided.

get_my_conversation ~64

Read the latest 30 messages in one conversation in the user's job seeker inbox. Message text is quoted as the sender wrote it. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
room_namestringyesRoom name from list_my_conversations

No output schema declared.

No examples provided.

get_my_profile ~29

Get your Himalayas profile information. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_new_matches ~88

Get jobs matching the user's Himalayas profile that were posted since an agent last checked, leaving out jobs already in their tracker. The check-in point is saved on the account, so it carries across sessions and agents; a first check looks back 7 days. Plus members get the jobs; free accounts get how many there are. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_plus_checkout_link ~218

Get a Stripe checkout link for Himalayas Plus (US$9 a month) when the user wants to subscribe. Plus includes tailored resumes and cover letters for every job; 30 minutes a month of spoken mock interviews for a specific job, scored out of 100 (sessions of 90 seconds or more) and saved so the user can track their progress; new job matches between sessions (get_new_matches); a higher place in employer talent search on the himalayas.app website (not in search_talent results through this connector, which have no paid placement); identity and work permit verification every 30 days, with a verified badge (work permits need a passport or national ID); and a career coach. Details: https://himalayas.app/plus. The user opens the link and pays on Stripe themselves; this tool never charges them. Applying through Himalayas is free without Plus. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
billing_intervalstring–Bill monthly or yearly (default: month)

No output schema declared.

No examples provided.

get_related_jobs ~63

Find jobs similar to a specific job, based on skills, location, and category. Use after viewing a job to suggest alternatives.

NameTypeReqDescription
company_slugstringyesCompany slug of the original job
job_slugstringyesJob slug of the original job

No output schema declared.

No examples provided.

get_remote_work_statistics ~115

Get remote work statistics: top skills, job categories, industries, or countries by job/company count.

NameTypeReqDescription
countrystring–Filter stats by country (e.g., 'United States', 'Germany')
recordstring–What to get stats for: 'jobs' or 'companies' (default: jobs)
typestring–Type of breakdown: 'skills', 'categories', 'countries', or 'industries' (default: skills). 'industries' only works with record='companies'.

No output schema declared.

No examples provided.

get_salary_data ~139

Get salary benchmarks for remote jobs by job title, with optional seniority and country filters. Returns min, max, and median salary in USD.

NameTypeReqDescription
countrystring–Country slug to filter by (e.g., 'united-states', 'united-kingdom', 'germany')
job_titlestringyesJob title to look up salary for (e.g., 'software-engineer', 'product-manager', 'data-scientist'). Use hyphens instead of spaces.
senioritystring–Seniority level (e.g., 'senior', 'junior', 'lead', 'mid')

No output schema declared.

No examples provided.

get_saved_jobs ~67

List every job in the user's Himalayas job application tracker with its status (saved, applied, interviewing, negotiation, hired, archived), outcome, salary, notes and links, for tracking applications and seeing where each one stands. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_talent_profile ~96

Get full details for a candidate including bio, all experiences, education, tech stack, social links, and more. Use the talent_slug from search_talent results. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
talent_slugstringyesTalent slug from search_talent (e.g. 'john-doe'). Also accepts '@john-doe' or a himalayas.app/@slug profile URL.

No output schema declared.

No examples provided.

get_verification_link ~154

Get the next step for verifying the user's identity and work permits on Himalayas (the verified badge): whether they are verified, and otherwise the Stripe Identity link (when verification is included, as on Plus or Max) or a US$5 checkout link. Use it when the user wants to get verified: when verification is included, this starts it (a Plus or Max member's included verification is then used for 30 days). A passport or national ID verifies identity and the work permit for that country; other IDs verify identity only. get_my_profile shows whether they are verified. The user opens each link and does the verification or payment on Stripe themselves. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import_profile ~126

Fill in the user's Himalayas profile from their LinkedIn profile URL or their resume text. Runs in the background for a few minutes; get_my_profile shows the result. append_only adds what's missing and keeps what's there; replace_all overwrites the profile, so ask the user first. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
linkedin_urlstring–Their LinkedIn profile URL, e.g. https://www.linkedin.com/in/name
modestring–Default append_only
resume_textstring–The full text of their resume

No output schema declared.

No examples provided.

join_radar_waitlist ~104

Join the waitlist for Himalayas Radar, a plan for people who are employed or not actively searching: alerts only for roles that beat their bar, a private open-to-offers mode with their current employer hidden, and a monthly salary check. Radar isn't available yet, so there is nothing to pay; Himalayas emails the user when it launches. Call it only if the user wants to join. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_coach_chats ~52

List the user's conversations with the Himalayas career coach, newest first, with titles, dates and links. get_coach_chat reads one. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_company_jobs ~58

List your company's job postings on Himalayas. Shows status, views, clicks, and expiry. Uses the connected Himalayas employer account; no extra sign-in needed.

NameTypeReqDescription
pageinteger–Page number for pagination (starts at 1)

No output schema declared.

No examples provided.

list_conversations ~46

List all your messaging conversations with last message preview. Shows conversation status (awaiting reply, new reply, read). Uses the connected Himalayas employer account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_documents ~59

List the user's tailored resumes and cover letters on Himalayas, newest first, with ids and edit links. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
typestring–Only resumes or only cover letters (default: both)

No output schema declared.

No examples provided.

list_headshots ~68

List the AI headshots the user has made on Himalayas, newest first: each session's finished images with ids and URLs, and a link to see them. use_headshot_as_profile_photo sets one as the profile photo. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_interviews ~65

List the user's interview practice on Himalayas: each job they practised for, when, and the link to practise again, plus the voice minutes and credits they have left. get_interview_results shows the scores. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_my_conversations ~68

List the user's job seeker inbox: conversations companies and recruiters started with them on Himalayas, newest first, with the last message and whether it needs a reply. For an employer's conversations with candidates, use list_conversations. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_notifications ~54

List the user's newest Himalayas notifications (up to 20), such as finished headshots, profile imports and community replies, with ids and whether each is read. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_saved_answers ~48

List the answers the user saved to job application questions on Himalayas (for example work authorisation or notice period), with ids. Uses the connected Himalayas account; no extra sign-in needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mark_message_read ~83

Mark a message as read by its ID. Uses the connected Himalayas employer account; no extra sign-in needed.

NameTypeReqDescription
message_idnumberyesMessage ID to mark as read
room_namestring–Room name from list_conversations
talent_slugstring–Talent slug (from search_talent results) — resolves to room name automatically

No output schema declared.

No examples provided.

mark_my_message_read ~65

Mark a message in the user's job seeker inbox as read. Uses the connected Himalayas account; no extra sign-in needed.

NameTypeReqDescription
message_idnumberyesMessage id from get_my_conversation
room_namestringyesRoom name from list_my_conversations

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http app-himalayas-mcp 'https://mcp.himalayas.app/mcp'
Common questions

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.