# Himalayas Remote Jobs

> Search and post remote jobs, browse companies, check salaries, and find talent on Himalayas.app

- name: app.himalayas/mcp
- version: 1.0.2
- connection class: R0 (autonomous)
- trust: 85/100
- quality: 70/100 (needs work)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/app.himalayas%2Fmcp
- tools: https://api.protogrid.dev/v1/servers/app.himalayas%2Fmcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "himalayas": {
      "type": "http",
      "url": "https://mcp.himalayas.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 45
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% -stale-232d
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 70/100 (needs work)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 79 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 76 of 79 tools declare readOnlyHint or destructiveHint
- warn `tools.directory_hints`: 42 of 79 tools declare all four hints; missing: list_conversations (destructiveHint, idempotentHint); search_jobs (destructiveHint, idempotentHint); get_jobs (destructiveHint, idempotentHint); …
- warn `tools.token_cost`: about 15,699 tokens to load every tool
- warn `tools.api_dump`: 79 tools, 76% named like REST operations: looks like an API mapped one endpoint per tool

### stability: 25 (weight 15)

- warn `stability.changes`: 96 tool changes in 30 days
- fail `stability.rug_pull`: 17 tools kept their name but changed most of their description in 30 days; review before trusting them

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 79, about 15,699 tokens to load them all
- tool set hash: 535cbf2c3fb71da51570f6ae6068bc1c
- tools last changed: 2026-10-19T13:14:18.217Z
- badge: [![protogrid quality](https://protogrid.dev/badge/app.himalayas/mcp.svg)](https://protogrid.dev/servers/app.himalayas/mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `get_verification_link` changed (description)
  - before: Get the next step for the user's Himalayas verified badge: whether they are verified, and otherwise the Stripe Identity link (when a check is included, as on Plus) or a US$5 checkout link. Call it when the user wants to get verified: when a check is included, this starts it (a Plus member's included check is then used for 30 days). get_my_profile shows whether they are verified. The user opens each link and does the ID check or payment on Stripe themselves. Uses the connected Himalayas account; no extra sign-in needed.
  - after: Get the next step for the user's Himalayas verified badge: whether they are verified, and otherwise the Stripe Identity link (when a check is included, as on Plus or Max) or a US$5 checkout link. Call it when the user wants to get verified: when a check is included, this starts it (a Plus or Max member's included check is then used for 30 days). Tell the user to use a passport or national ID if they want their work permit verified too. get_my_profile shows whether they are verified. The user opens each link and does the ID check or payment on Stripe themselves. Uses the connected Himalayas account; no extra sign-in needed.
- 2026-10-19 `get_plus_checkout_link` changed (description)
  - before: Get a checkout link for Himalayas Plus (US$9 a month), which covers tailored resumes and cover letters for every job, live spoken mock interviews for a specific job with an AI interviewer playing the hiring manager (30 minutes a month, each scored out of 100 on content and delivery), new job matches between sessions (get_new_matches), the user's profile shown first to employers searching Himalayas talent, a verified badge (one ID check every 30 days), and a career coach. The user opens the link and pays on Stripe themselves. Plus is optional: applying through Himalayas is free. Never enter payment details or make up a link. Uses the connected Himalayas account; no extra sign-in needed.
  - after: Get a checkout link for Himalayas Plus (US$9 a month), which covers tailored resumes and cover letters for every job, live spoken mock interviews for a specific job with an AI interviewer playing the hiring manager (30 minutes a month, each scored out of 100 on content and delivery), new job matches between sessions (get_new_matches), the user's profile shown first to employers searching Himalayas talent, an ID verified badge (one ID check every 30 days), and a career coach. The user opens the link and pays on Stripe themselves. Plus is optional: applying through Himalayas is free. Never enter payment details or make up a link. Uses the connected Himalayas account; no extra sign-in needed.
- 2026-10-19 `get_verification_link` added
  - Get the next step for the user's Himalayas verified badge: whether they are verified, and otherwise the Stripe Identity link (when a check is included, as on Plus) or a US$5 checkout link. Call it when the user wants to get verified: when a check is included, this starts it (a Plus member's included check is then used for 30 days). get_my_profile shows whether they are verified. The user opens each link and does the ID check or payment on Stripe themselves. Uses the connected Himalayas account; no extra sign-in needed.
- 2026-10-19 `get_plus_checkout_link` changed (description)
  - before: Get a checkout link for Himalayas Plus (US$9 a month), which covers tailored resumes and cover letters for every job, live spoken mock interviews for a specific job with an AI interviewer playing the hiring manager (30 minutes a month, each scored out of 100 on content and delivery), new job matches between sessions (get_new_matches), the user's profile shown first to employers searching Himalayas talent, and a career coach. The user opens the link and pays on Stripe themselves. Plus is optional: applying through Himalayas is free. Never enter payment details or make up a link. Uses the connected Himalayas account; no extra sign-in needed.
  - after: Get a checkout link for Himalayas Plus (US$9 a month), which covers tailored resumes and cover letters for every job, live spoken mock interviews for a specific job with an AI interviewer playing the hiring manager (30 minutes a month, each scored out of 100 on content and delivery), new job matches between sessions (get_new_matches), the user's profile shown first to employers searching Himalayas talent, a verified badge (one ID check every 30 days), and a career coach. The user opens the link and pays on Stripe themselves. Plus is optional: applying through Himalayas is free. Never enter payment details or make up a link. Uses the connected Himalayas account; no extra sign-in needed.
- 2026-10-19 `mark_my_message_read` added
  - Mark a message in the user's job seeker inbox as read. Uses the connected Himalayas account; no extra sign-in needed.
- 2026-10-19 `reply_to_message` added
  - Send a reply in a conversation in the user's job seeker inbox. The company reads it as coming from the user, so show the user the exact text and get their OK before sending. Uses the connected Himalayas account; no extra sign-in needed.
- 2026-10-19 `get_my_conversation` added
  - 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.
- 2026-10-19 `list_my_conversations` added
  - 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.
- 2026-10-19 `send_message` changed (description)
  - before: 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. Uses the connected Himalayas employer account; no extra sign-in needed.
  - after: 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. The candidate reads it as coming from the user's company, so show the user the exact text and get their OK before sending. Uses the connected Himalayas employer account; no extra sign-in needed.
- 2026-10-19 `start_conversation` changed (description)
  - before: Start a conversation with a candidate by talent slug. Optionally send an initial message. If the conversation already exists, returns it. Use search_talent to find candidates first, then use their slug here. Uses the connected Himalayas employer account; no extra sign-in needed.
  - after: Start a conversation with a candidate by talent slug. Optionally send an initial message. If the conversation already exists, returns it. Use search_talent to find candidates first, then use their slug here. The candidate reads it as coming from the user's company, so show the user the exact text and get their OK before sending. Uses the connected Himalayas employer account; no extra sign-in needed.

Full history: https://api.protogrid.dev/v1/servers/app.himalayas%2Fmcp/changes

## Remotes

- https://mcp.himalayas.app/mcp (streamable-http, auth none, reachable true, uptime30d 1)
- https://mcp.himalayas.app/sse (sse, auth unknown, reachable false, uptime30d 0)

## Packages

_none_

## Tools (79)

- `add_company_perk`: Add a perk/benefit to your company on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
- `add_education`: Add an education entry to your Himalayas profile. Uses the connected Himalayas account; no extra sign-in needed.
- `add_experience`: Add a work experience to your Himalayas profile. Uses the connected Himalayas account; no extra sign-in needed.
- `check_job_payment_status`: Check the payment status of a job posting. Use the session_id returned from post_job_public or create_company_job with extras. No authentication required.
- `create_company_job`: Post a new job on Himalayas. Jobs are free to post and require admin approval before going live. Uses the connected Himalayas employer account; no extra sign-in needed.
- `delete_company_job`: Delete a job posting from your company on Himalayas. This action cannot be undone. Uses the connected Himalayas employer account; no extra sign-in needed.
- `delete_conversation`: Delete a conversation. Accepts room_name or talent_slug. Uses the connected Himalayas employer account; no extra sign-in needed.
- `delete_document`: 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.
- `delete_education`: 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.
- `delete_experience`: 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.
- `delete_saved_answer`: 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.
- `generate_application_documents`: 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, ever, so on a free account use them on the job the user is most likely to apply to; Himalayas Plus covers every job. Uses the connected Himalayas account; no extra sign-in needed. Use the company_slug and job_slug from job listings.
- `get_apply_link`: 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.
- `get_billing_portal_link`: 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.
- `get_coach_chat`: 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.
- `get_companies`: Browse remote-friendly companies with optional filtering by country or worldwide availability
- `get_company_details`: Get full details for a company including about, tech stack, benefits, open positions, and social links
- `get_company_perks`: Get your company's perks/benefits on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
- `get_company_profile`: Get your company's profile on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
- `get_conversation`: Get full message history for a conversation. Accepts room_name or talent_slug. Uses the connected Himalayas employer account; no extra sign-in needed.
- `get_correct_country_name`: Resolve a country name to the correct format accepted by Himalayas filters. Useful for fuzzy matching user input.
- `get_document`: 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.
- `get_headshots_link`: 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.
- `get_interview_practice_link`: Get the Himalayas page where the user practises interviewing for a job: a Himalayas job (company_slug and job_slug) or a job elsewhere (application_link). Uses the connected Himalayas account; no extra sign-in needed.
- `get_interview_results`: 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.
- `get_job_details`: 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.
- `get_jobs`: Browse the latest remote job listings with optional filtering by country or worldwide availability
- `get_my_conversation`: 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.
- `get_my_profile`: Get your Himalayas profile information. Uses the connected Himalayas account; no extra sign-in needed.
- `get_new_matches`: 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.
- `get_plus_checkout_link`: Get a checkout link for Himalayas Plus (US$9 a month), which covers tailored resumes and cover letters for every job, live spoken mock interviews for a specific job with an AI interviewer playing the hiring manager (30 minutes a month, each scored out of 100 on content and delivery), new job matches between sessions (get_new_matches), the user's profile shown first to employers searching Himalayas talent, an ID verified badge (one ID check every 30 days), and a career coach. The user opens the link and pays on Stripe themselves. Plus is optional: applying through Himalayas is free. Never enter payment details or make up a link. Uses the connected Himalayas account; no extra sign-in needed.
- `get_related_jobs`: Find jobs similar to a specific job, based on skills, location, and category. Use after viewing a job to suggest alternatives.
- `get_remote_work_statistics`: Get remote work statistics: top skills, job categories, industries, or countries by job/company count. Great for understanding the remote work landscape.
- `get_salary_data`: Get salary benchmarks for remote jobs by job title, with optional seniority and country filters. Returns min, max, and median salary in USD.
- `get_saved_jobs`: Get all jobs in your application tracker. Uses the connected Himalayas account; no extra sign-in needed.
- `get_talent_profile`: 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.
- `get_verification_link`: Get the next step for the user's Himalayas verified badge: whether they are verified, and otherwise the Stripe Identity link (when a check is included, as on Plus or Max) or a US$5 checkout link. Call it when the user wants to get verified: when a check is included, this starts it (a Plus or Max member's included check is then used for 30 days). Tell the user to use a passport or national ID if they want their work permit verified too. get_my_profile shows whether they are verified. The user opens each link and does the ID check or payment on Stripe themselves. Uses the connected Himalayas account; no extra sign-in needed.
- `import_profile`: 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.
- `join_radar_waitlist`: Join the waitlist for Himalayas Radar, a planned 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.
- `list_coach_chats`: 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.
- `list_company_jobs`: 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.
- `list_conversations`: 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.
- `list_documents`: 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.
- `list_headshots`: 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.
- `list_interviews`: 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.
- `list_my_conversations`: 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.
- `list_notifications`: 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.
- `list_saved_answers`: 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.
- `mark_message_read`: Mark a message as read by its ID. Uses the connected Himalayas employer account; no extra sign-in needed.
- `mark_my_message_read`: Mark a message in the user's job seeker inbox as read. Uses the connected Himalayas account; no extra sign-in needed.
- `mark_notifications_read`: 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.
- `post_job_public`: Post a job on Himalayas without an account. Provide your email and company details. Payment is required — a Stripe checkout URL will be returned. No authentication needed.
- `purchase_job_extras`: 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.
- `remove_company_perk`: Remove a perk/benefit from your company on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
- `remove_saved_job`: Remove a job from your application tracker. Uses the connected Himalayas account; no extra sign-in needed.
- `reply_to_message`: Send a reply in a conversation in the user's job seeker inbox. The company reads it as coming from the user, so show the user the exact text and get their OK before sending. Uses the connected Himalayas account; no extra sign-in needed.
- `save_job`: Save a job to your application tracker. Uses the connected Himalayas account; no extra sign-in needed.
- `search_companies`: Search for remote-friendly companies using keywords with optional country filtering
- `search_jobs`: Search for remote jobs using keywords with optional filtering by country or worldwide availability
- `search_talent`: Search for remote talent/candidates on Himalayas. Browse professionals by keyword, country, or role.
- `send_message`: 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. The candidate reads it as coming from the user's company, so show the user the exact text and get their OK before sending. Uses the connected Himalayas employer account; no extra sign-in needed.
- `show_company_job`: Get full details of one of your company's job postings on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
- `skip_job`: 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.
- `start_conversation`: Start a conversation with a candidate by talent slug. Optionally send an initial message. If the conversation already exists, returns it. Use search_talent to find candidates first, then use their slug here. The candidate reads it as coming from the user's company, so show the user the exact text and get their OK before sending. Uses the connected Himalayas employer account; no extra sign-in needed.
- `submit_feedback`: Report a problem with Himalayas to its engineering team. Call this when something prevented or complicated your task: a missing capability (filter, field, tool), unclear or wrong documentation, a surprising response, an unhelpful error, a bug, being blocked from a page or action, or impractical performance. Describe your goal in plain language, say specifically what got in the way, and include a concrete suggestion if you have one. Say who you are in `agent` (name and model). Report each distinct problem once per task. Never include credentials, personal data or your user's private content. This is best effort: after calling it, continue with your task.
- `update_account`: 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.
- `update_company_job`: 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. Uses the connected Himalayas employer account; no extra sign-in needed.
- `update_company_profile`: Update your company's profile on Himalayas. Uses the connected Himalayas employer account; no extra sign-in needed.
- `update_company_tech_stack`: 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.
- `update_document`: 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.
- `update_education`: 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.
- `update_email_preferences`: 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.
- `update_experience`: 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.
- `update_job_status`: 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.
- `update_profile`: Update your Himalayas profile. Uses the connected Himalayas account; no extra sign-in needed.
- `update_profile_photo`: 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.
- `update_saved_answer`: 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.
- `update_tech_stack`: 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.
- `use_headshot_as_profile_photo`: 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.