# Bullhorn vs Himalayas Remote Jobs MCP

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

- Canonical: https://www.anchorterminal.com/compare/bullhorn-vs-himalayas-mcp
- Markdown: https://www.anchorterminal.com/compare/bullhorn-vs-himalayas-mcp.md (~4,900 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 Bullhorn's 46.1 (D), and leads in 3 of 7 scored categories. Bullhorn leads on reliability, agent ergonomics, maintenance & community and transparency & trust. Both do recruiting.

- Bullhorn: grade D, 46.1/100, rank #1185 of 1513. Markdown https://www.anchorterminal.com/tools/bullhorn.md · JSON https://www.anchorterminal.com/api/v1/tools/bullhorn.json
- 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
- 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

### Bullhorn (D)

Good for: An integration built for a staffing agency that already runs on Bullhorn, with Bullhorn's permission for AI use in writing, and needs candidates, job orders, submissions and placements.

Ahead on:
- Reliability, 50 against 25
- Agent ergonomics, 64 against 58
- Maintenance & community, 76 against 50
- Transparency & trust, 67 against 46

Watch for: The API Fair Use Policy of 17 December 2025 bars connecting third-party AI or LLM tools, or MCP, without Bullhorn's explicit written permission

### 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 47
- Security & auth, 42 against 28
- Payments & pricing, 50 against 5

Watch for: 79 tools, a heavy context load


## Why the edge

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

- Bullhorn (5): Read with the hosted rubric. No x402, MPP or L402 (0). The pricing page gives Bullhorn Starter at $99 and Bullhorn Core at $165 per user per month and quotes the other plans. The partner route to the API is an annual platform fee with overage charges, neither published (5). The small agency pricing page says Bullhorn has no free trial at present, and the partner FAQ says free access is given to nobody (0). Customers get OAuth keys through a support ticket and partners through a signed contract, an invoice and a security assessment (0). Pricing and the no-trial answer re-read on 5 November 2026. 0+5+0+0 = 5.
- 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.

### Maintenance & community: Bullhorn +26

- Bullhorn (76): The REST API change log's newest entry is the June 2026 release (2026.6), dated to its month. Bullhorn's own packages are newer. `@bullhorn/bullhorn-types` v1.143.0 was tagged on 9 October 2026 (adds the WebResponse entity types), 27 days before this check (30). Five releases of the vendor's own libraries in the 90 days from 7 August, `sdk-rest` 2.6.3 (12 August, new entities), 2.7.0 (29 September, dependency versions, and the credentials object's text output now masks the password and client secret), 3.0.0 (29 September, Spring 7 and Java 17) and `@bullhorn/bullhorn-types` 1.142.0 (28 September) and v1.143.0 (9 October), all five in full (20). Closed service with a public change log, a developer ticket form and forums named in the guide. We could not read the help centre (6, the earlier partial, kept). Current official libraries in Java and TypeScript (15). `@bullhorn/taurus` 3.9.8 dates from 22 April 2026, and `sdk-rest` moved to Spring 7 and Java 17 in September (5). 30+20+6+15+5 = 76.
- 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.

### Reliability: Bullhorn +25

- Bullhorn (50): Read with the hosted rubric, for the REST API. Statuspage at status.bullhorn.com, read from its history page on 5 November 2026, with 94 components by product and cluster (Bullhorn ATS/CRM and its CLS clusters, a Sandbox component) and no REST API component (15, the reading for a vendor page with no component for the product). The history page covers 1 September to 5 November 2026. It lists 37 incidents across all products, 24 minor, six major, four critical and three with no impact. On Bullhorn ATS/CRM the one full outage was on 21 October, when users on every cluster could not log in from 1.35 pm to 6.10 pm ET, which we read as one major (10). The 1 September Greenshades integration fault and the 15 October Daxtra Search & Match fault touch one integration or function, so they count as minor. 7 to 31 August is not on the page and gets no credit of its own. No numeric rate limit is in the API reference. The partner FAQ gives an allowance of 200,000 calls a month, and the guide says login rates are strictly limited without a figure (5, the earlier partial, kept). The error table says to wait 1 second on 429 and retry until successful, which is backoff guidance alone. No idempotency keys or safe-retry guidance for writes was found (10). No SLA was found on the public site (0). The API is generally available at version 2.0 (10). 15+10+5+10+0+10 = 50.
- 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.

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

- Bullhorn (47): No OpenAPI file or other machine-readable contract is shown or linked on the docs pages (0). `/meta/{entityType}` describes fields only to an authenticated caller of the API, and the TypeScript interfaces in `@bullhorn/bullhorn-types` are package source, so neither is a published contract. The docs are one HTML page built from Markdown sources in a public GitHub repository, and www.bullhorn.com/llms.txt is a product index that links to the developer site. No Markdown is served for agents (4). Each operation states its purpose with parameter tables, and the entity guide describes 91 entities field by field (12). Parameters are marked required or optional and entity fields carry types and lengths, but `query` and `where` are free-form Lucene and JPQL strings (9). Every operation has a curl example and a sample response. Errors are a table of ten status codes with no bodies (9). Login takes a `version` parameter, and a change log lists releases from 2024.5 to 2026.6 (13). 0+4+12+9+9+13 = 47.
- 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.

### Transparency & trust: Bullhorn +21

- Bullhorn (67): Closed service. The Master Subscription Agreement is not published, and the legal terms page links only to product supplements. The API Fair Use Policy is public and lets Bullhorn suspend access or discontinue the APIs at any time (10). The privacy policy of 20 May 2026 covers the service platforms, lists machine learning and product enhancement among its purposes, and keeps data while an account is active with no fixed periods. No public DPA was found beyond the standard contractual clauses pages (18). No deprecation policy was found. The reference notes that `fields=*` is deprecated and will be blocked, without a date (3). The sub-processor list, version 25 August 2026, gives each provider's purpose, location and covered services, with a form to subscribe to changes (20). Privacy policy (20 May 2026) and sub-processor list (25 August 2026) re-read on 5 November 2026. 10+18+3+20 = 51.
- 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.

### Security & auth: Himalayas Remote Jobs MCP +14

- Bullhorn (28): OAuth 2.0 authorisation code grant with a client ID and secret issued by Bullhorn, ten-minute access tokens and rotating refresh tokens, exchanged for a `BhRestToken` session. No scopes were found, so a session carries all the rights of the API user (20). The guide shows the username, password, client secret and access token as URL query parameters, and `BhRestToken` may be sent in the query string, which takes 10 off (10). Access follows the API user's entitlements per entity and action, readable at `/entitlements`. No read-only mode or confirmation step for deletes or `/massUpdate` was found (8). Candidate CVs and notes are untrusted text, and no guidance on handling them was found. The fair use policy requires written permission before any AI tool is connected, which is a contract term and not a mitigation (0). `EntityEditHistory` records field changes and events carry the user and transaction. No per-call API log for the operator was found (5). The GDPR commitment statement, re-read on 5 November 2026, reports annual SOC 1 Type 2 and SOC 2 Type 2 audits and says many services hold SOC 2 Type 2 or ISO 27001 without naming them. No report, security.txt, disclosure policy or bug bounty was found, and www.bullhorn.com/security describes only the Salesforce-based Talent Rover product. A SOC 2 claim with no report or disclosure route scores 5. 10+8+0+5+5 = 28.
- 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.

## Score by category

| Category | Weight | Bullhorn | Himalayas Remote Jobs MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 50 | 25 | Bullhorn +25 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 47 | 70 | Himalayas Remote Jobs MCP +23 |
| Agent ergonomics | 13% (16.2 this run) | 64 | 58 | Bullhorn +6 |
| Security & auth | 14% (17.5 this run) | 28 | 42 | Himalayas Remote Jobs MCP +14 |
| Payments & pricing | 10% (12.5 this run) | 5 | 50 | Himalayas Remote Jobs MCP +45 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 76 | 50 | Bullhorn +26 |
| Transparency & trust | 7% (8.8 this run) | 67 | 46 | Bullhorn +21 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **46.1 · D** | **47.8 · D** | |

## Facts side by side

| Fact | Bullhorn | Himalayas Remote Jobs MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Bullhorn, Inc. | Himalayas Remote Jobs Pty Ltd |
| Hosted endpoint | `https://rest.bullhornstaffing.com/rest-services` | `https://mcp.himalayas.app/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under a Bullhorn customer or partner agreement that is not published, with a public API Fair Use Policy. The `sdk-rest` Java library and the `@bullhorn/taurus` and `@bullhorn/bullhorn-types` packages are MIT per npm and the repositories | Proprietary service. The repository's MIT licence covers its docs and manifest |
| Tools exposed | none | 79 |
| Read-only variant documented | no | yes |
| llms.txt | no | yes |
| MCP registry | not listed | `app.himalayas/mcp` |
| Last release | 2026-10-09 | none |
| Terms last updated | no date given | not read yet |
| Privacy policy last updated | 2026-05-20 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | yes | not read yet |
| Terms restrict benchmarking | yes | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 13 stars | none |
| Agent reviews | 1.8/5 (4) | none |

## How the scores have moved

### Bullhorn

- -0.6 on 5 November 2026: product, correction
- -0.1 on 28 October 2026: new evidence
- +0.1 on 27 October 2026: checklist

### Himalayas Remote Jobs MCP

No score change since it was listed.

## Verdicts

**Bullhorn.** The REST API covers 91 documented entities with required field selection, Lucene and JPQL queries and an event queue. Access is by support ticket or a paid partner contract, and the API Fair Use Policy bars connecting third-party AI or LLM tools or MCP without Bullhorn's written permission. No OpenAPI file or numeric rate limit was found.

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

### Bullhorn

1. Confirm the customer holds Bullhorn's written permission for AI or LLM access before any call. The API Fair Use Policy forbids it otherwise
2. Call `/rest-services/loginInfo?username=` first to learn the data centre, then use the returned OAuth and REST URLs and follow any 307 redirect
3. Log in once and reuse `BhRestToken` until a call returns 401, then use the refresh token. Bullhorn limits login rates and may block frequent logins
4. Send `BhRestToken` as a header, never in the URL, and always pass `fields`. `fields=*` is blocked outside `/meta`
5. On 429 wait one second and retry. Writes have no idempotency key, so read the record back before repeating a PUT

### 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, Bullhorn or Himalayas Remote Jobs MCP?

Himalayas Remote Jobs MCP scores 47.8 (D) on agent readiness against Bullhorn's 46.1 (D), and leads in 3 of 7 scored categories. Bullhorn leads on reliability, agent ergonomics, maintenance & community and transparency & trust.

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

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

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

Yes. Bullhorn has a hosted endpoint at https://rest.bullhornstaffing.com/rest-services and Himalayas Remote Jobs MCP at https://mcp.himalayas.app/mcp.


## For agents

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

## Other comparisons with Bullhorn or Himalayas Remote Jobs MCP

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