Himalayas Remote Jobs MCP vs Manatal

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.

Manatal 75

Graded on the Open API with the hosted lines. Manatal's Terms and Conditions bar using its website content and services through programs that send automatic requests, so status.manatal.com and the docs weren't re-read on 4 November and their findings are per the 9 October check, not re-read on 4 November. Statuspage site at status.manatal.com with an API component and incident history (20). The feed showed only scheduled database maintenance between 11 July and 9 October 2026, and the last incident was increased latency on app.manatal.com on 10 July 2026. The window since 10 October is unread, so the line keeps its recorded award and gains nothing for the unread part (30). The MCP help article gives the standard API rate limit as 100 requests a minute. The API reference states no limit (15). No 429 handling, backoff guidance or idempotency keys were found in the reviewed documentation (0). The security page states uptime of 99.9 per cent or higher, and the Terms of Service of 25 March 2024 allow refunds at Manatal's discretion up to the monthly fee. A stated uptime figure with no committed percentage or credit isn't an SLA, so 0 (was 5). The API is at v3 with no beta label, though the docs call it a work in progress covering a subset of the product (10). 20+30+15+0+0+10 = 75.

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.

Manatal 6

Findings per the 9 October check, not re-read on 4 November (terms pause). The newest API reference page read carried an update date of 6 July 2026 (the candidate skills bulk endpoint), but the record shows no API change on that date, and a page date that records no change doesn't set recency. No dated API change was found (0). The product changelog is drawn by script inside an embedded frame and went unread, so no dated entries in the last 90 days could be counted (0). The help centre's sitemap dated changes to the MCP articles on 23 September, 2 October and 9 October 2026. Support is by email and chat, with priority support on Enterprise Plus (6). No official SDK was found (0). No packages to assess (0). 0+0+6+0+0 = 6.

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.

Manatal 30

All findings per the 9 October check, not re-read on 4 November (terms pause). No x402, MPP or L402 (0). Plan prices are public per user per month, $15, $35 and $55 billed annually or $19, $39 and $59 monthly, with API access only on the $55 plan (10). 14-day trial without a card. The trial covers what all three plans include, with some exceptions, and the Open API must still be enabled by support (20). A person signs up in a browser and an admin generates the token in settings (0).

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.

Manatal 53

All findings per the 9 October check, not re-read on 4 November (terms pause). Every reference page on developers.manatal.com carries an OpenAPI 3.0 fragment for its operation and is served as Markdown. No single downloadable description file was found (20). llms.txt lists 158 reference pages with Markdown twins (10). Descriptions are one line each, many of them generic class comments, and most query parameters have an empty description (5). Parameters and body fields are typed, with titles and maximum lengths, but date filters are plain strings, gender and source_type have no enum and custom_fields is a free object (8). Most operations list only a 200 or 201 response with no description. The skills bulk endpoint lists 400, 404 and 409, and no error reference was found (3). The version is in the path as v3, v1 and v2 were retired with a dated notice, and the developer changelog has two entries (7).

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.

Manatal 43

All findings per the 9 October check, not re-read on 4 November (terms pause). List endpoints take page_size, with no field selection found (10). page and page_size, with filters by name, email, owner, tags and created or updated date ranges on candidates and jobs (17). Errors are not documented beyond a few status codes on some reference pages. The 9 October note also leaned on an unauthenticated test request, which this run strikes; the line keeps its earlier partial, flagged (6). No idempotency keys. external_id on candidates and matches allows a lookup before a retry, and a candidate can be matched to a job only once (4). Few required parameters, and no official SDK was found (6).

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.

Manatal 61

Findings per the 9 October check, not re-read on 4 November (terms pause), except the Terms and Conditions, re-read on 4 November (effective 7 September 2026, unchanged). Closed service with published Terms and Conditions effective 7 September 2026, governed by Thai law. No document read names the contracting legal entity (12). The DPA of 7 September 2026 says personal data is deleted or returned at termination, while the Terms and Conditions say Manatal stores customer data for up to 10 years after termination. The privacy policy of 3 July 2026 gives no retention periods (12). v1 and v2 of the API were retired on 7 February 2025 with a dated notice. No deprecation policy was found (8). The DPA links a sub-processor list with seven days to object to a change, and the list is a script-drawn Notion page that went unread. The security page says all customer data is stored in the USA on AWS (10).