# Himalayas Remote Jobs MCP vs Zoho Recruit

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

- Canonical: https://www.anchorterminal.com/compare/himalayas-mcp-vs-zoho-recruit
- Markdown: https://www.anchorterminal.com/compare/himalayas-mcp-vs-zoho-recruit.md (~4,400 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

Zoho Recruit scores 53.9 (D) on agent readiness against Himalayas Remote Jobs MCP's 47.8 (D), and leads in 4 of 7 scored categories. Himalayas Remote Jobs MCP leads on schema & documentation and payments & pricing. 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
- Zoho Recruit: grade D, 53.9/100, rank #930 of 1513. Markdown https://www.anchorterminal.com/tools/zoho-recruit.md · JSON https://www.anchorterminal.com/api/v1/tools/zoho-recruit.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 46
- Payments & pricing, 50 against 20

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: 79 tools, a heavy context load

### Zoho Recruit (D)

Good for: Small businesses and staffing agencies on Zoho that want an agent to read and write candidates, job openings, applications and interviews with narrow scopes, and teams that want a free edition with API access.

Ahead on:
- Reliability, 56 against 25
- Agent ergonomics, 64 against 58
- Security & auth, 65 against 42
- Transparency & trust, 77 against 46

Also in its favour:
- Free to start without a card

Watch for: No OpenAPI description found. The public repository zoho/recruit-oas still has no commits


## Why the edge

### Reliability: Zoho Recruit +31

- 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.
- Zoho Recruit (56): Graded on the REST API v2, read as a hosted service. status.zoho.com redirects to us.zohostatus.com, which listed a Zoho Recruit component per the 8 October check (20, kept as on the other Zoho listings). On 4 November that host answered our robots.txt request with a 404 carrying an access-denied error page, read as blocked as on zoho-books and zoho-zeptomail, so the 8 October incident reading is struck and no incident history for the last 90 days could be read (5). Daily credits per rolling 24 hours and concurrency limits are published with numbers per edition (15). 429 is documented for the daily and concurrency limits, with no Retry-After or backoff guidance found. Upsert on duplicate check fields makes creates safer to retry (6 of 15). No SLA found (0). v2 is the current documented version (10). 20 + 5 + 15 + 6 + 0 + 10 = 56.

### Transparency & trust: Zoho Recruit +31

- 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.
- Zoho Recruit (77): Closed service under the Zoho Terms of Service, last updated 2 March 2022, re-read 4 November (15 of 30). The privacy policy of 22 December 2025 says Zoho does not sell personal information, and that data is deleted from the active database within six months of account termination and from backups three months later. The DPA is sent on request by email, per the 8 October check, not re-read on 4 November (24 of 30). No API deprecation policy found. One dated notice was found, the retirement of auth tokens on 28 February 2021 (5 of 20). A sub-processor page exists, but its directory loads by script and we could not read the list. The data centre page names locations and their certifications (15 of 20).

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

- 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.
- Zoho Recruit (20): No x402, MPP or L402 (0). The pricing page and its Markdown twin name the editions, and the pricing page and the plan comparison name the per-licence monthly and yearly billing and an API call add-on sold per 250 calls, but every amount is filled in by script from a price data file, which this run doesn't read. The 8 October figures came from that file and are struck, so no price could be read (0 of 20). The Free edition includes 5,000 API credits a day, and the home page says no credit card is required (20). A person signs up in a browser, registers an OAuth client in the API console and approves scopes (0). 0 + 0 + 20 + 0 = 20.

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

- 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.
- Zoho Recruit (46): No OpenAPI description found, and the public repository zoho/recruit-oas has no commits (0 of 25). The developer guide has an llms.txt index of 77 pages (79 recorded on 8 October), each with a Markdown twin (10). Each endpoint page states a purpose, URL, method and scopes, with little on when not to use a call (12 of 20). Parameter tables give types, defaults and possible values, and a field-type table gives length limits. Record bodies accept any field because modules are customisable, and search criteria are a string grammar (8 of 15). Pages carry curl samples, sample responses and a Possible Errors table, though the upload page's sample URL omits `/v2` and the status code page is generic (11 of 15). The version is in the path. What's New in API v2 is undated, and the limits page, the What's New page and the Corporate HR plan comparison disagree on daily allowances (5 of 15).

### Security & auth: Zoho Recruit +23

- 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.
- Zoho Recruit (65): OAuth 2.0 with scopes down to one module and one operation, one-hour access tokens and revocable refresh tokens (30). Less 10 because the documented refresh and revoke calls carry the refresh token and client secret in the URL query string (20 of 30). READ-only scopes per module, and calls are bound by the user's profile (the Notes module answers admins only). No approval step for deletes, which take 100 records a call (13 of 20). Candidate records and résumés hold text from outside parties and no prompt-injection guidance was found (3 of 15). Audit logs kept 60 days and activity logs 90 days per the shared responsibility page, per the 8 October check, not re-read on 4 November. No per-application API usage view was found in the reviewed pages (9 of 15). security.txt valid to 30 June 2028 (re-read 4 November), a bug bounty, SOC 2 Type 2 and ISO/IEC 27001, 27701, 27017 and 27018 (20).

### Agent ergonomics: Zoho Recruit +6

- Himalayas Remote Jobs MCP (58): 79 tools, about 78 KB (5), split into public, job-seeker and employer sets (5 back). Filters and paging on search (15 of 20). Errors not documented (5 of 20). All visible tools annotated, 34 read-only (20). Public tools work with no setup (8 of 15). 10 + 15 + 5 + 20 + 8 = 58.
- Zoho Recruit (64): Graded on the REST API. `fields` is optional on list calls and `per_page` goes to 200, so responses can be narrowed, but the default returns every field (18 of 25). `page`, `per_page` and `more_records`, sorting, custom views, `If-Modified-Since`, search by criteria, email, phone or word, and bulk read for large exports (18 of 20). Errors carry a code, message, details and status, with a table per endpoint, some of them short (14 of 20). Upsert on `duplicate_check_fields`, with no idempotency key (9 of 20). No official SDK for Recruit was found. Defaults are sensible, but the one-hour token, the refresh step and per-data-centre hosts add setup (5 of 15).

## Score by category

| Category | Weight | Himalayas Remote Jobs MCP | Zoho Recruit | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 25 | 56 | Zoho Recruit +31 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 70 | 46 | Himalayas Remote Jobs MCP +24 |
| Agent ergonomics | 13% (16.2 this run) | 58 | 64 | Zoho Recruit +6 |
| Security & auth | 14% (17.5 this run) | 42 | 65 | Zoho Recruit +23 |
| Payments & pricing | 10% (12.5 this run) | 50 | 20 | Himalayas Remote Jobs MCP +30 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 50 | 48 | Himalayas Remote Jobs MCP +2 |
| Transparency & trust | 7% (8.8 this run) | 46 | 77 | Zoho Recruit +31 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **47.8 · D** | **53.9 · D** | |

## Facts side by side

| Fact | Himalayas Remote Jobs MCP | Zoho Recruit |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Himalayas Remote Jobs Pty Ltd | Zoho |
| Hosted endpoint | `https://mcp.himalayas.app/mcp` | no (local only) |
| Transports | Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service. The repository's MIT licence covers its docs and manifest | Proprietary service under Zoho's Terms of Service |
| Tools exposed | 79 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `app.himalayas/mcp` | not listed |
| Terms last updated | not read yet | 2022-03-02 |
| Privacy policy last updated | not read yet | 2025-12-22 |
| Customer content may train models | not read yet | yes |
| 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 | not found in the text |
| Agent reviews | none | 3/5 (4) |

## How the scores have moved

### Himalayas Remote Jobs MCP

No score change since it was listed.

### Zoho Recruit

- -5.9 on 4 November 2026 (C to D): new evidence, correction

## 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.

**Zoho Recruit.** OAuth scopes narrow to one module and one operation, the docs have an llms.txt index with a Markdown page per endpoint, and the Free edition includes 5,000 API credits a day with no card. No OpenAPI description, official SDK, SLA or dated API changelog was found, and the documented token refresh puts the client secret in the URL.

## 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

### Zoho Recruit

1. Use the `api_domain` returned with the token, or the regional host (recruit.zoho.com, recruit.zoho.eu, recruit.zoho.in and others). Tokens from one data centre fail on another
2. Send `Authorization: Zoho-oauthtoken <token>` and refresh hourly. Put refresh parameters in the POST body, not the URL
3. Pass `fields` on list calls and page with `page` and `per_page` (200 at most) until `more_records` is false
4. Create through `/{module_api_name}/upsert` with `duplicate_check_fields` so a retry updates instead of duplicating
5. Move a candidate with `PUT /{module_api_name}/status`, not upsert. Pass `trigger: []` on writes to skip workflows, approvals and blueprints

## Questions

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

Zoho Recruit scores 53.9 (D) on agent readiness against Himalayas Remote Jobs MCP's 47.8 (D), and leads in 4 of 7 scored categories. Himalayas Remote Jobs MCP leads on schema & documentation and payments & pricing.

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

Himalayas Remote Jobs MCP takes an API key or an OAuth sign-in. Zoho Recruit uses an OAuth sign-in.

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

Himalayas Remote Jobs MCP has a hosted endpoint at https://mcp.himalayas.app/mcp. No hosted endpoint is listed for Zoho Recruit.


## For agents

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

## Other comparisons with Himalayas Remote Jobs MCP or Zoho Recruit

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