Head to head · Recruiting · October 2026 research run

Greenhouse vs Himalayas Remote Jobs MCP

Greenhouse scores 59.8 (C) on agent readiness against Himalayas Remote Jobs MCP's 47.8 (D), and leads in 6 of 7 scored categories. Himalayas Remote Jobs MCP leads on payments & pricing. Both do recruiting.

Best recruiting and applicant tracking systems for AI agents · All 106 recruiting comparisons

Which one, for what

Greenhouse C

Best for An agent working inside a company that already runs hiring on Greenhouse and needs to read pipelines, move applications, schedule interviews or draft offer records under scoped OAuth.

Ahead on

  • Reliability, 76 against 25
  • Schema & documentation, 79 against 70
  • Agent ergonomics, 63 against 58
  • Security & auth, 85 against 42
  • Maintenance & community, 65 against 50
  • Transparency & trust, 79 against 46

Watch for

No public price, free tier or trial. Pricing is customised through sales, and the sandbox comes only with the Pro tier

Himalayas Remote Jobs MCP D

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

Ahead on

  • Payments & pricing, 50 against 0

Also in its favour

  • No incidents deducted, where Greenhouse loses 6 points for them

Watch for

79 tools, a heavy context load

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Greenhouse +51

Greenhouse 76

Read with the hosted rubric, for the Harvest v3 API. Statuspage at status.greenhouse.io with a Greenhouse Harvest API component and per-silo components (20). The history feed (history.atom) covers the 90 days from 4 August to 2 November 2026. Three posts touch the API, each partial. On 5 August a partial disruption of Greenhouse Recruiting (scorecards, notes, emails, offer letters and more) ran from 02:18 UTC to a fix at 03:56. On 2 September a HarvestV3 maintenance posted as it began gave elevated 401 errors for 34 minutes. On 13 October a partial disruption of Greenhouse Recruiting ran from 15:32 to 19:00. The rest name job boards, integrations, Voice AI or MyGreenhouse. Partial incidents only, so minor (20). The v3 limit is a fixed 30-second window whose size arrives in X-RateLimit-Limit, with no number published beyond an example of 75 (8). 429 carries Retry-After and the docs give backoff guidance, but no idempotency keys were found for writes (10). The SLA commits to 99.5 per cent for Greenhouse Recruiting with service credits and does not name the API (8). Harvest v3 is generally available, while the MCP server is in open beta (10). 20+20+8+10+8+10 = 76.

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.

Payments & pricing Himalayas Remote Jobs MCP +50

Greenhouse 0

Read with the hosted rubric. No x402, MPP or L402 (0). No public prices. The pricing page names Core, Plus and Pro and says pricing is customised (0). No free tier or trial found, and the sandbox comes only with the Pro tier (0). Credentials are created by a person inside a customer account, and the MCP server's dynamic client registration still needs a paying organisation and a user's consent in a browser (0).

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.

Security & auth Greenhouse +43

Greenhouse 85

OAuth 2.0 with a scope per endpoint, client credentials or the authorisation code grant, one-hour partner access tokens and secret rotation that keeps the old secret for up to a week. The MCP server adds PKCE and dynamic client registration (30). Read-only access is possible by scope, the MCP defaults to seven read-only scopes, blocks every DELETE and asks for confirmation on five actions. All list endpoints need a Site Admin as the authorising user (16). The MCP security FAQ covers prompt injection (structured tool calls only, permission-bound and rate-limited), with no guidance on treating candidate text in responses as untrusted (9). The Audit Log API records Harvest and MCP calls with user, client and arguments for thirty days, as a paid add-on (12). SOC 2 Type II, ISO 27001, 27701 and 42001, a HackerOne bug bounty and annual penetration tests. security.txt expired on 1 February 2026 (18).

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.

Transparency & trust Greenhouse +33

Greenhouse 79

Closed service with a public Master Subscription Agreement last updated 1 February 2026, and an Apache-2.0 docs repository (15). The agreement queues customer data for deletion 90 days after termination, a DPA is published, and the MCP FAQ says the server stores no customer data. The privacy policy of 28 May 2026 says personal information may be used to develop and train AI models and gives no retention periods (20). The removal of Harvest v1 and v2 was announced for 31 August 2026 with migration guides, but on 2 November 2026 the banner still read as future, and a v3 changelog entry of 22 October still names Harvest V1 as a way to change job owners. Deprecated v3 values are marked in the changelog (the active status filter on 22 October, kept as an alias). No written deprecation policy with a notice period was found (12). A public sub-processor list with purposes and locations, AWS hosting in the United States, Germany and Australia, and the MCP server stated as US-only (20).

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.

Maintenance & community Greenhouse +15

Greenhouse 65

The newest Harvest v3 changelog entry is dated 29 October 2026 (d5a234aa, GET /v3/prospect_details) (30). 28 dated entries from 1 October to 29 October alone (20). Closed service with a changelog, monthly release notes that list API changes and a partner support address. Changelog entries are titled by commit hash, which makes them hard to follow (10). No official SDKs found, and the MCP server is not in the official MCP registry (0, per the 7 October check, not re-read on 2 November). No package to assess. The docs repository for the older APIs had commits up to 10 September 2026 (5, per the 7 October check, not re-read on 2 November). 30+20+10+0+5 = 65.

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.

Schema & documentation Greenhouse +9

Greenhouse 79

Every v3 reference page has a Markdown twin with an OpenAPI 3.1 definition for that endpoint. No single downloadable spec was found (20). llms.txt indexes 179 reference pages and the guides, all served as Markdown (10). Descriptions state purpose, required fields and limits, for example that stage moves are not handled by the update call and that from_stage_id guards against stale moves (16). Request bodies set additionalProperties to false with required fields, enums and length limits (13). Success examples are given, but reference pages list 401, 403 and 422 without bodies, and error bodies appear only in the guides (8). The path is versioned and the changelog had 28 entries from 1 October to 29 October 2026, titled by commit hash with relative dates on the page, though each entry now names the endpoints and the change (12).

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.

Score by category

CategoryWeight this runGreenhouseHimalayas Remote Jobs MCPEdge
Reliability16%207625Greenhouse +51
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27970Greenhouse +9
Agent ergonomics13%16.26358Greenhouse +5
Security & auth14%17.58542Greenhouse +43
Payments & pricing10%12.5050Himalayas Remote Jobs MCP +50
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86550Greenhouse +15
Transparency & trust7%8.87946Greenhouse +33
Negative events≤15-60
TotalC 59.8/100D 47.8/100

Facts side by side

FactGreenhouseHimalayas Remote Jobs MCP
KindHTTP APIMCP server
VendorGreenhouse Software, Inc.Himalayas Remote Jobs Pty Ltd
Hosted endpointhttps://harvest.greenhouse.io/v3https://mcp.himalayas.app/mcp
TransportsHTTPStreamable HTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Greenhouse's Master Subscription Agreement. The docs repository for the older APIs on GitHub is Apache-2.0Proprietary service. The repository's MIT licence covers its docs and manifest
Tools exposednone79
Read-only variant documentednoyes
llms.txtyesyes
MCP registrynot listedapp.himalayas/mcp
Last release2026-10-29none
Terms last updated2026-02-01not read yet
Privacy policy last updated2026-05-28not read yet
Customer content may train modelsyesnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Greenhouse

Harvest v3 pairs per-endpoint OAuth scopes with Markdown docs that embed an OpenAPI 3.1 definition for each call, and the beta MCP server blocks every DELETE. Access needs a paying customer account with no public price or trial, and October changelog entries changed published behaviour for existing clients on the day they shipped.

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.

Before you call either

Greenhouse

  1. Request a token from https://auth.greenhouse.io/token with client credentials, then send it as a Bearer token to https://harvest.greenhouse.io/v3. Tokens expire, so repeat on 401
  2. Put filters and per_page on the first list request only. A cursor must be the only query parameter, or the call returns 422
  3. Send the current stage as from_stage_id when moving an application. Check for an existing webhook before creating one, since a duplicate answers 409. Other writes have no idempotency key
  4. Treat a job's custom_fields entries as optional. Since 26 October 2026 fields that don't apply to the job are left out rather than returned as null
  5. Expect empty list results or 403 unless the token's user is a Site Admin, and wait for Retry-After on 429 (30-second window)

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

Questions

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

Greenhouse scores 59.8 (C) on agent readiness against Himalayas Remote Jobs MCP's 47.8 (D), and leads in 6 of 7 scored categories. Himalayas Remote Jobs MCP leads on payments & pricing.

Do Greenhouse and Himalayas Remote Jobs MCP need an API key?

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

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

Yes. Greenhouse has a hosted endpoint at https://harvest.greenhouse.io/v3 and Himalayas Remote Jobs MCP at https://mcp.himalayas.app/mcp.

Other comparisons with Greenhouse or Himalayas Remote Jobs MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.