Breezy HR vs Himalayas Remote Jobs MCP

Breezy HR 15

No x402, MPP or L402 (0). Startup, Growth and Business plan prices are public, but API access is an optional add-on to the custom Pro plan, which has no price. Partial credit for the public plans (5). The pricing page now says Breezy HR has no free plan. A 14-day trial of every capability needs no card. Whether the trial includes API access is not stated, and the docs return 403 for a company on a plan without it, so half credit (10). A person signs up in a browser and creates the token in settings (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.

Breezy HR 63

Closed service with published terms, updated 10 August 2026 (15). The terms (updated 10 August 2026), the group data protection addendum and the group privacy notice (last updated October 2026) agree, and the terms say customer content is not used to train AI models. No retention period after termination is stated. The addendum leaves deletion to the main agreement and the privacy notice leaves it to the customer contract (16). No deprecation policy was found, and the terms let Breezy HR change or stop the service without notice. The docs keep some old paging behaviour for backward compatibility (3). Per the 9 October check, not re-read on 4 November, sub-processors for Breezy HR are listed with purpose and countries, with 30 days to object to a new one, and hosting in Germany or the USA by client choice (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.

Breezy HR 40

Graded on the REST API with the hosted lines. Status page at status.breezy.hr on Pulsetic, per the 9 October check, not re-read on 4 November because the host answers robots.txt with its HTML app page. On 9 October the page was drawn by script and showed no components or incidents. With no component history ever read, the status-page line scores 0, as meta-model-api's script-drawn page (0), and the 90-day record is unread and scored as no readable history (5). The API reference's introduction states 100 requests a minute per access token, and 300 a minute per customer for partner integrations (15). It says a request over the limit gets 429 with a Retry-After header in seconds, to retry after that wait, and not to retry other 4xx errors. No idempotency key or safe-retry guidance for writes was found, so Retry-After alone (10). No SLA was found, and the terms supply the service as is (0). The v3 API carries no beta label, though the docs overview calls the documentation and API a work in progress (10). 0 + 5 + 15 + 10 + 0 + 10 = 40.

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.

Breezy HR 60

The newest API changelog entry is dated 30 October 2026 (30). Nine dated entries between 6 August and 4 November 2026, on 19 and 26 August, 9, 16 and 30 September and 7, 14, 28 and 30 October (20). A public changelog, a support address in the docs and a 24-hour reply target on weekdays in the terms (10). No official SDK was found (0). No packages to assess (0).

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.

Breezy HR 79

Each of the 65 operations in the docs index has an OpenAPI 3.1 fragment on its reference page. No single downloadable file was found (20). llms.txt on developer.breezy.hr, and every page is served as Markdown (10). Descriptions state purpose, side effects and edge cases, for example that page=0 and page=1 both return the first page, and the changelog of 15 July 2026 says they were verified against live traffic (16). Inputs are typed with enums, patterns, maxima and required fields (12). One error shape is documented, with status codes and their meaning on each operation. Request examples sit mainly in the webhook guides (10). The version is in the path and the changelog is dated, but entries name only the paths changed and not what changed (11).

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.

Breezy HR 50

Personal access tokens are named, shown once, given an expiry at creation and invalidated when the user leaves the account. They travel only in a header and have no scopes. The MCP server also accepts OAuth with PKCE and nine scopes. A session token from POST /signin with email and password is a documented alternative (22). A token acts with its user's permissions and the help centre says admins create them. Custom roles need the Business or Pro plan. The OAuth scopes split read from write. No confirmation step was found, though the API has only two delete operations (9). CVs, notes and messages are candidate-written, and no injection guidance was found (0). Activity streams record changes per candidate and position, and webhook endpoints report delivery counts. No API call log was found (6). Per the 9 October check, not re-read on 4 November, Learning Technologies Group publishes ISO 27001:2022 and ISO 27701 certificates and lists a 2026 SOC 2 Type II report on request. breezy.hr/.well-known/security.txt answered 403 AccessDenied from storage again on 4 November. No security.txt, bounty or disclosure address was found (13).

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.