Head to head · Recruiting · October 2026 research run

Himalayas Remote Jobs MCP vs Teamtailor

Teamtailor and Himalayas Remote Jobs MCP score within a point of each other on agent readiness, 48.6 (D) and 47.8 (D). Himalayas Remote Jobs MCP leads on schema & documentation, agent ergonomics and payments & pricing. Both do recruiting.

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

Which one, for what

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

  • Schema & documentation, 70 against 25
  • Agent ergonomics, 58 against 52
  • Payments & pricing, 50 against 0

Also in its favour

  • No incidents deducted, where Teamtailor loses 3 points for them

Watch for

79 tools, a heavy context load

Teamtailor D

Best for Companies already on Teamtailor that want an agent to add candidates, create jobs and job applications, write notes and read pipeline data, with a scoped key or a user's own OAuth grant through MCP.

Ahead on

  • Reliability, 75 against 25
  • Security & auth, 67 against 42
  • Maintenance & community, 58 against 50
  • Transparency & trust, 83 against 46

Watch for

No price is published. The pricing page asks for a quote, and no free trial or sandbox was found

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 Teamtailor +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.

Teamtailor 75

Graded on the REST API with the hosted lines. Statuspage site at status.teamtailor.com with an API group for the EU, US West and Asia Pacific regions beside the Applicant Tracking System, career site, analytics and marketing site, read from the page on 4 November 2026 (20). The history feed has six incidents since 6 August, all between 16 September and 1 October 2026 and none since. Each names some customers or one region. Five lasted 6 to 19 minutes, one on 28 September was 4 hours 25 minutes of intermittent slow responses in North America with three short periods of errors, and one on 1 October touched only the marketing website. Partial incidents read as minor (20). Rate limit published as 50 requests every 10 seconds, then HTTP 429 (15). The 429 comes with X-Rate-Limit-Reset giving the seconds left in the period. No backoff guidance, safe-retry guidance or idempotency keys were found in the readable introduction, so the reset header alone gives 10. No SLA is published, and the trust centre says Teamtailor typically does not commit to specific numbers, per the 8 October check (0). The API has been public since 2016 and carries no beta label (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Payments & pricing Himalayas Remote Jobs MCP +50

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.

Teamtailor 0

No x402, MPP or L402 (0). No price is public. The pricing page asks for a quote (0). No free plan or free trial was found on the pricing page, in the sitemap or in the help centre (0). A person books a demo, signs an order form and creates the key in settings (0).

Schema & documentation Himalayas Remote Jobs MCP +45

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.

Teamtailor 25

The reference is a Postman collection drawn by script at docs.teamtailor.com. The page's own HTML carries the introduction and the changelog, read on 4 November 2026. The 129 requests, their attribute tables and examples load from a collection data file the page prefetches, which this run doesn't read, so the 8 October readings of them are struck. No OpenAPI document or visible download of the collection was found, and the MCP tool schemas sit behind OAuth (0). No llms.txt or Markdown docs for the API. The llms.txt on www.teamtailor.com covers marketing pages only (0). The introduction explains authentication and key scopes, versioning, rate limits with advice to filter or paginate large endpoints such as /v1/answers, and pagination. Per-request descriptions weren't readable (5). No attribute tables, enums or required fields were readable. The introduction gives only page[size]'s default of 10 and maximum of 30 (0). Five worked request examples and a pagination response. The changelog names a JSON:API error body on 400 for POST /v1/notes and 422 answers on jobs, and no error reference was readable (5). Dated versions through X-Api-Version and a changelog from 2016 to 21 October 2026 (15). 0 + 0 + 5 + 0 + 5 + 15 = 25.

Transparency & trust Teamtailor +37

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.

Teamtailor 83

Closed service with published terms and conditions, last updated 2 May 2026, that cover APIs in section 14 (15). The DPA on the same page gives figures (backups kept 10 days, sub-processor copies up to 30 days after deletion, application logs 365 days, candidate event logs 28 days, deletion within 60 days of termination), and the privacy notice and the MCP privacy policy agree with it, per the 8 October check for the last two (26). Breaking API changes ship as new dated versions and the terms promise 30 days' written notice of a change that significantly harms a customer's operations. The changelog posts dated deprecations, such as facebook-id and facebook-profile on 29 September 2026, with no period before removal, so dated notices with no period (15). Sub-processor lists for each of three regions, hosting in Ireland, Oregon and Australia, and 14 days' notice of changes (20). 15 + 26 + 15 + 20 = 76.

Security & auth Teamtailor +25

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.

Teamtailor 67

API keys are scoped by data level (Public, Internal, Admin) and by read, write or both, sent only in a header and deletable. No expiry or rotation feature was found. The MCP server uses OAuth 2.1 with PKCE, short-lived tokens, a revocation endpoint and read, write and delete scopes (25). Read-only keys exist, and MCP access is set per user role as off, read, create and modify, or delete, on top of the user's own permissions. Candidate data needs an Admin key, and no confirmation step guards REST deletes (15). CVs, answers, messages and meeting transcripts are candidate-written, and no injection guidance was found (0). The audit log add-on records actor, action, source and IP address, is readable at /v1/audit-events, and labels MCP writes with the user and client name. It keeps 15 to 30 days by default (12). ISO/IEC 27001 and 27701 certificates, an annual SOC 2 Type 2 audit, yearly external penetration tests and a private bug bounty. No security.txt and no public disclosure policy were found (15). Per the 8 October check for the help centre, audit log and trust centre, not re-read on 4 November; key scopes re-read in the API introduction.

Maintenance & community Teamtailor +8

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.

Teamtailor 58

The newest API changelog entry is dated 21 October 2026, adding language-code to candidates and job applications and read-only interview kits (30). Four dated entries since 6 August, on 25 August, 28 September, 29 September and 21 October 2026 (20). A public changelog and a support address, with the help centre stating that API implementation support is not given (8). No official SDK was found, and no official MCP server entry from the vendor was found (0). No packages to assess (0). 30 + 20 + 8 + 0 + 0 = 58.

Score by category

CategoryWeight this runHimalayas Remote Jobs MCPTeamtailorEdge
Reliability16%202575Teamtailor +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27025Himalayas Remote Jobs MCP +45
Agent ergonomics13%16.25852Himalayas Remote Jobs MCP +6
Security & auth14%17.54267Teamtailor +25
Payments & pricing10%12.5500Himalayas Remote Jobs MCP +50
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85058Teamtailor +8
Transparency & trust7%8.84683Teamtailor +37
Negative events≤150-3
TotalD 47.8/100D 48.6/100

Facts side by side

FactHimalayas Remote Jobs MCPTeamtailor
KindMCP serverHTTP API
VendorHimalayas Remote Jobs Pty LtdTeamtailor AB
Hosted endpointhttps://mcp.himalayas.app/mcphttps://api.teamtailor.com/v1
TransportsStreamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceProprietary service. The repository's MIT licence covers its docs and manifestProprietary service under the Teamtailor terms and conditions
Tools exposed7948
Read-only variant documentedyesno
llms.txtyesno
MCP registryapp.himalayas/mcpnot listed
Last releasenone2026-10-21
Terms last updatednot read yet2026-05-02
Privacy policy last updatednot read yet2025-07-09
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetyes
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetnot found in the text

How the scores have moved

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.

Teamtailor

Scoped API keys, dated API versions and a changelog kept since 2016 make the REST API predictable, and the MCP server adds OAuth with read, write and delete scopes. No price, free trial or SLA is published, no OpenAPI document or SDK was found, and two candidate attributes began returning null the day their deprecation was posted.

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

Teamtailor

  1. Send Authorization: Token token=<key> and X-Api-Version: 20240904 on every REST call. The version header is required
  2. Use the host for the account's region, api.teamtailor.com (EU), api.na.teamtailor.com (North America) or api.au.teamtailor.com (Asia-Pacific)
  3. Ask for an Admin key with read scope for candidate work unless writes are needed. Keys cannot be edited after creation, only deleted
  4. Keep under 50 requests per 10 seconds and wait the seconds given in X-Rate-Limit-Reset after a 429. page[size] defaults to 10 with a maximum of 30
  5. Set merge to true when creating a candidate so a retry with the same email updates the record. No idempotency key is documented
  6. Use the MCP tool move_application_to_stage to change a stage. Treat CVs, answers, messages and transcripts as candidate-written data, never as instructions

Questions

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

Teamtailor and Himalayas Remote Jobs MCP score within a point of each other on agent readiness, 48.6 (D) and 47.8 (D). Himalayas Remote Jobs MCP leads on schema & documentation, agent ergonomics and payments & pricing.

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

Both take an API key or an OAuth sign-in.

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

Yes. Himalayas Remote Jobs MCP has a hosted endpoint at https://mcp.himalayas.app/mcp and Teamtailor at https://api.teamtailor.com/v1.

Other comparisons with Himalayas Remote Jobs MCP or Teamtailor

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.