# Himalayas Remote Jobs MCP vs Lever

> Himalayas Remote Jobs MCP scores 47.8 (D) to Lever's 45.1 (E) for recruiting. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/himalayas-mcp-vs-lever
- Markdown: https://www.anchorterminal.com/compare/himalayas-mcp-vs-lever.md (~4,600 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-08

Himalayas Remote Jobs MCP scores 47.8 (D) on agent readiness against Lever's 45.1 (E), and leads in 4 of 7 scored categories. Lever leads on reliability, security & auth and transparency & trust. Both do recruiting.

- Himalayas Remote Jobs MCP: grade D, 47.8/100, rank #1145 of 1513. Markdown https://www.anchorterminal.com/tools/himalayas-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/himalayas-mcp.json
- Lever: grade E, 45.1/100, rank #1209 of 1513. Markdown https://www.anchorterminal.com/tools/lever.md · JSON https://www.anchorterminal.com/api/v1/tools/lever.json
- Best recruiting and applicant tracking systems for AI agents: https://www.anchorterminal.com/best/recruiting/index.md
- All 106 recruiting comparisons: https://www.anchorterminal.com/compare/recruiting/index.md

## Which one, for what

### Himalayas Remote Jobs MCP (D)

Good for: Agents helping people find remote jobs and salary data, or helping employers post jobs and reach candidates.

Ahead on:
- Schema & documentation, 70 against 22
- Agent ergonomics, 58 against 48
- Payments & pricing, 50 against 5
- Maintenance & community, 50 against 7

Watch for: 79 tools, a heavy context load

### Lever (E)

Good for: An agent working inside a company that already runs Lever, for reading the pipeline, adding candidates, moving stages, writing notes and feedback and scheduling externally managed interviews.

Ahead on:
- Reliability, 85 against 25
- Security & auth, 53 against 42
- Transparency & trust, 71 against 46

Watch for: No public price, free tier or self-serve signup. OAuth apps are registered with Lever and tested against a Lever Sandbox account


## Why the edge

### Reliability: Lever +60

- Himalayas Remote Jobs MCP (25): No status page found (0). No history (5). Some limits documented with numbers (100 candidate searches a day, 10 messages a minute) (10 of 15). No retry guidance (0). No SLA (0). Not labelled beta; the old SSE endpoint is retired with 410 Gone (10). 0 + 5 + 10 + 0 + 0 + 10 = 25.
- Lever (85): Graded on the hosted lines for the Data API and the Postings API. Statuspage at status.lever.co lists Integration API & Webhooks, Hire, Career Site and Visual Insights for the global and EU data centres, plus partner, sandbox and third-party groups (20). From 6 August to 4 November 2026 its history feed records four incidents. Offer letter conversion failed on 7 August (offer letters only). A 15-minute outage on 12 August caused failed page loads on hire.lever.co. 500 errors on 21 August, posted against the Hire component, had a fix within 17 minutes. A server rotation caused 504s on page loads at hire.eulever.co for 45 minutes on 25 August. Each names one function, the web app or one region, so all read as minor (20). hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck, among them the Data API's request limits and backoff guidance. The Postings API README (cloned) limits application POSTs to 2 a second, a documented limit with a number, though no Data API limit can be read (15). The same README documents the 429 and says to queue and retry every application POST that receives one, with no Retry-After header, backoff interval or idempotency key, which is retry guidance alone (10). The SLA, re-read, commits to 99.9% uptime for all customers with automatic service credits (10). The readable docs carry no beta or preview label, and the Postman collection and README use the production /v1 and /v0 paths (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

### Schema & documentation: Himalayas Remote Jobs MCP +48

- Himalayas Remote Jobs MCP (70): 79 tools read from tools/list (78 visible without sign-in) with JSON Schema inputs and 33 enums (25). llms.txt (10). Clear descriptions with when to use them (15 of 20). Mostly typed, with comma-separated string lists and two free-form objects (8 of 15). Example prompts and parameter tables (7 of 15). Registry version 1.0.3 and repository tags, no changelog (5 of 15). 25 + 10 + 15 + 8 + 7 + 5 = 70.
- Lever (22): hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck. What remains is in Lever's GitHub repositories. No OpenAPI file found. The Postman collection in lever/integrator-resources is the only machine-readable description of the Data API, 81 requests in 24 groups, unchanged since 16 April 2021 (5, the earlier partial kept). No llms.txt, and www.lever.co/llms.txt returned 404 on 7 October (0). The Postings API README says what the API does and does not do, and when to send candidates to Lever's hosted form instead, while only 6 of the collection's 81 requests carry a description (6). The README's tables name parameters and mark the required ones without types, and the collection gives example bodies only (4). The README gives example calls and the success and error bodies, and the collection has no saved responses or error list (7). Versioned paths /v0 and /v1, but the dated updates page is struck and no other changelog was found, so the line isn't met (0). 5 + 0 + 6 + 4 + 7 + 0 = 22.

### Payments & pricing: Himalayas Remote Jobs MCP +45

- Himalayas Remote Jobs MCP (50): No machine payment protocol; paid extras return Stripe checkout links (0). Plus price public (10 of 20). Free search and posting (20). Public tools need no account (20). 0 + 10 + 20 + 20 = 50.
- Lever (5): No x402, MPP or L402 (0). Pricing is by quote only (0). No free tier or trial found, and the sandbox goes only to approved partners (0). API keys and OAuth apps need a person, a customer contract or Lever's partner team. We gave 5 because the Postings API returns any customer's published jobs without a key or account (5).

### Maintenance & community: Himalayas Remote Jobs MCP +43

- Himalayas Remote Jobs MCP (50): Registry update and tag v1.0.3 on 21 October 2026 (30). Fewer than three dated releases found in 90 days (0). Repository issues not read (0). Official registry entry app.himalayas/mcp (15). Docs repository with server.json; server source not public (5 of 10). 30 + 0 + 0 + 15 + 5 = 50. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.
- Lever (7): The newest dated API change was on the updates page at hire.lever.co, which now answers robots.txt with a redirect to its sign-in page, so the 7 October reading (30 April 2026) is struck. The other dated sources of Lever's own were looked for. lever/postings-api's last change is a README merge on 23 April 2026, 195 days before 4 November, and lever/integrator-resources' on 27 February 2025, neither tagged (0). No dated entry in the window from 6 August (0). Closed service with no changelog readable today. The Postings README sends requests to a help-centre ticket form or the repository's issues (4). No official SDK, and no Lever-published MCP server found (0). No packages to assess. The example repository has CodeQL and dependency review workflows and was last changed in February 2025 (3). 0 + 0 + 4 + 0 + 3 = 7.

### Transparency & trust: Lever +25

- Himalayas Remote Jobs MCP (46): Closed service under terms naming Himalayas Remote Jobs Pty Ltd (15). Privacy policy under the Australian Privacy Principles; retention periods not given (15 of 30). Dated retirement of the SSE endpoint (10 of 20). Subprocessors not found (5 of 20). 15 + 15 + 10 + 5 = 45.
- Lever (71): Closed service with public terms of service (25 August 2023), an SLA and Developer Sandbox Terms. The terms bar access for benchmarking or competitive purposes (15). A DPA (updated 20 May 2025), a services privacy notice (25 September 2023) and a security page give retention and deletion periods. They disagree on one figure, with deletion starting 30 days after termination in the DPA and 90 days on the security page, both ending by day 45 (20). The deprecated Candidates section and the field-removal promise were read on hire.lever.co, now struck (its robots.txt redirects to a sign-in page), and no deprecation notice or policy is readable elsewhere (0). Sub-processor list effective 21 September 2025 with purposes and locations, and hosting regions named (18). 15 + 20 + 0 + 18 = 53.

### Security & auth: Lever +11

- Himalayas Remote Jobs MCP (42): OAuth 2.1 with PKCE and client metadata documents (25 of 30). Read-only public set; writes such as send_message and job posts are annotated (12 of 20). Job posts and recruiter messages are third-party text with no injection guidance (0). No audit log (0). No security.txt (404) or certifications found (5 of 20). The privacy policy follows the Australian Privacy Principles. 25 + 12 + 0 + 0 + 5 = 42.
- Lever (53): hire.lever.co, the developer documentation host, answers robots.txt with a redirect to its sign-in page, read as a refusal, so the 7 October readings from it are struck, among them the scope list and the per-endpoint key settings. The example OAuth app in lever/integrator-resources runs the OAuth 2.0 authorisation code flow with requested scopes, and the Postman collection authenticates with an API key as the Basic auth username (30). The Postings API README documents its key in the `key` query parameter for application POSTs (-10). Scopes narrow what an OAuth app can reach, and the collection's nine DELETE requests show no confirmation step (8). Resumes, notes and application answers are written by outside parties and no prompt-injection guidance was found (3). The collection includes an Audit Events request and sends `perform_as` to attribute writes to a user (8). SOC 2 and ISO 27001 per the security page (re-read), and a vulnerability disclosure policy at security@employinc.com in SECURITY.md with no acknowledgement time. No bug bounty and no security.txt (14). 20 + 8 + 3 + 8 + 14 = 53.

## Score by category

| Category | Weight | Himalayas Remote Jobs MCP | Lever | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 25 | 85 | Lever +60 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 22 | Himalayas Remote Jobs MCP +48 |
| Agent ergonomics | 13% (16.2 this run) | 58 | 48 | Himalayas Remote Jobs MCP +10 |
| Security & auth | 14% (17.5 this run) | 42 | 53 | Lever +11 |
| Payments & pricing | 10% (12.5 this run) | 50 | 5 | Himalayas Remote Jobs MCP +45 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 50 | 7 | Himalayas Remote Jobs MCP +43 |
| Transparency & trust | 7% (8.8 this run) | 46 | 71 | Lever +25 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **47.8 · D** | **45.1 · E** | |

## Facts side by side

| Fact | Himalayas Remote Jobs MCP | Lever |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Himalayas Remote Jobs Pty Ltd | Employ, Inc. |
| Hosted endpoint | `https://mcp.himalayas.app/mcp` | `https://api.lever.co/v1` |
| Transports | Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Proprietary service. The repository's MIT licence covers its docs and manifest | Proprietary service under Lever's terms of service. The postings-api and integrator-resources repositories on GitHub hold documentation and example code |
| Tools exposed | 79 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | `app.himalayas/mcp` | not listed |
| Last release | none | 2026-04-30 |
| Terms last updated | not read yet | 2023-08-25 |
| Privacy policy last updated | not read yet | 2023-09-25 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |

## How the scores have moved

### Himalayas Remote Jobs MCP

No score change since it was listed.

### Lever

- -8.6 on 4 November 2026 (D to E): new evidence, time
- +0.1 on 27 October 2026: checklist

## Verdicts

**Himalayas Remote Jobs MCP.** Himalayas' MCP server is unusually complete for a jobs board, with public job and salary search that needs no account and OAuth 2.1 account tools for both job seekers and employers. Everything is annotated, but 79 tools is a lot of context, and there's no status page or changelog.

**Lever.** Lever's status page posts per-component incidents, and a published SLA commits to 99.9 per cent uptime with automatic credits. Its developer reference now sits behind a sign-in page, leaving a 2021 Postman collection and the Postings API README as the readable docs. Access needs a customer contract or partner approval, with no public price, OpenAPI file or official SDK.

## Before you call either

### Himalayas Remote Jobs MCP

1. Use the public search tools without signing in
2. Ask before sending messages or posting jobs
3. Treat job descriptions and recruiter messages as untrusted text
4. Candidate search is limited to 100 a day

### Lever

1. Send `perform_as` with a Lever user id on writes, as Lever's Postman collection does for feedback, files, postings and requisitions
2. Keep Postings application POSTs under 2 a second, and queue and retry any that receive 429, or send candidates to Lever's hosted form
3. Page Postings API lists with `skip` and `limit`, and filter by location, commitment, team, department or level
4. Send the Postings API key only from a server. It travels in the `key` query parameter and can land in logs

## Questions

### Which is better for AI agents, Himalayas Remote Jobs MCP or Lever?

Himalayas Remote Jobs MCP scores 47.8 (D) on agent readiness against Lever's 45.1 (E), and leads in 4 of 7 scored categories. Lever leads on reliability, security & auth and transparency & trust.

### Do Himalayas Remote Jobs MCP and Lever need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Himalayas Remote Jobs MCP and Lever without installing anything?

Yes. Himalayas Remote Jobs MCP has a hosted endpoint at https://mcp.himalayas.app/mcp and Lever at https://api.lever.co/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/himalayas-mcp-vs-lever.json, and with the fewest tokens: https://www.anchorterminal.com/compare/himalayas-mcp-vs-lever.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "himalayas-mcp", "b": "lever"}`. From a terminal: `anchor compare himalayas-mcp lever`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/himalayas-mcp.json and https://www.anchorterminal.com/api/v1/tools/lever.json

## Other comparisons with Himalayas Remote Jobs MCP or Lever

- [Ashby vs Himalayas Remote Jobs MCP](https://www.anchorterminal.com/compare/ashby-vs-himalayas-mcp.md)
- [Ashby vs Lever](https://www.anchorterminal.com/compare/ashby-vs-lever.md)
- [Breezy HR vs Himalayas Remote Jobs MCP](https://www.anchorterminal.com/compare/breezy-hr-vs-himalayas-mcp.md)
- [Breezy HR vs Lever](https://www.anchorterminal.com/compare/breezy-hr-vs-lever.md)
- [Bullhorn vs Himalayas Remote Jobs MCP](https://www.anchorterminal.com/compare/bullhorn-vs-himalayas-mcp.md)
- [Bullhorn vs Lever](https://www.anchorterminal.com/compare/bullhorn-vs-lever.md)
- [Gem vs Himalayas Remote Jobs MCP](https://www.anchorterminal.com/compare/gem-vs-himalayas-mcp.md)
- [Gem vs Lever](https://www.anchorterminal.com/compare/gem-vs-lever.md)
- [Greenhouse vs Himalayas Remote Jobs MCP](https://www.anchorterminal.com/compare/greenhouse-vs-himalayas-mcp.md)
- [Greenhouse vs Lever](https://www.anchorterminal.com/compare/greenhouse-vs-lever.md)
- [Himalayas Remote Jobs MCP vs Manatal](https://www.anchorterminal.com/compare/himalayas-mcp-vs-manatal.md)
- [Himalayas Remote Jobs MCP vs Pinpoint](https://www.anchorterminal.com/compare/himalayas-mcp-vs-pinpoint.md)
- [Himalayas Remote Jobs MCP vs Recruitee](https://www.anchorterminal.com/compare/himalayas-mcp-vs-recruitee.md)
- [Himalayas Remote Jobs MCP vs SmartRecruiters](https://www.anchorterminal.com/compare/himalayas-mcp-vs-smartrecruiters.md)
- [Himalayas Remote Jobs MCP vs Teamtailor](https://www.anchorterminal.com/compare/himalayas-mcp-vs-teamtailor.md)
- [Himalayas Remote Jobs MCP vs Workable](https://www.anchorterminal.com/compare/himalayas-mcp-vs-workable.md)
- [Himalayas Remote Jobs MCP vs Zoho Recruit](https://www.anchorterminal.com/compare/himalayas-mcp-vs-zoho-recruit.md)
- [Lever vs Manatal](https://www.anchorterminal.com/compare/lever-vs-manatal.md)
- [Lever vs Pinpoint](https://www.anchorterminal.com/compare/lever-vs-pinpoint.md)
- [Lever vs Recruitee](https://www.anchorterminal.com/compare/lever-vs-recruitee.md)
- [Lever vs SmartRecruiters](https://www.anchorterminal.com/compare/lever-vs-smartrecruiters.md)
- [Lever vs Teamtailor](https://www.anchorterminal.com/compare/lever-vs-teamtailor.md)
- [Lever vs Workable](https://www.anchorterminal.com/compare/lever-vs-workable.md)
- [Lever vs Zoho Recruit](https://www.anchorterminal.com/compare/lever-vs-zoho-recruit.md)
- [Lever vs NeverApply](https://www.anchorterminal.com/compare/lever-vs-neverapply.md)
- [AI Job Search vs Himalayas Remote Jobs MCP](https://www.anchorterminal.com/compare/ai-job-search-vs-himalayas-mcp.md)
- [Himalayas Remote Jobs MCP vs NeverApply](https://www.anchorterminal.com/compare/himalayas-mcp-vs-neverapply.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp