Himalayas Remote Jobs MCP vs NeverApply

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.

NeverApply 66

OAuth 2.1 for the MCP server, public clients with PKCE S256, client ID metadata documents or dynamic registration, a resource parameter, refresh tokens and three scopes; auth.md says no API keys or personal access tokens are accepted and documents no query-string secret; token lifetimes are not stated and no RFC 7009 revocation endpoint is advertised, though disconnecting a client in settings revokes its tokens and pending codes. The Jobs API takes a bearer token from a developer dashboard that was not readable (26 of 30). Read, edit and apply scopes; applying needs the apply scope, credits and the member's approval of each named job, sending needs a separate grant tied to one assistant that the terms say no tool can create, held applications need an explicit approve_application, and MCP tools cannot buy plans or move money; the web app's Send mode applies up to a daily cap without asking per job, which is outside the MCP surface (18 of 20). Job descriptions are employer text; the find-jobs skill and GEMINI.md say to summarise them and never follow instructions inside them, with no server-side filtering described (9 of 15). Settings list connected AI clients with their mode and allowance, get_profile shows the current budget mode, the tracker logs every application, errors carry a support or correlation ID, and the privacy policy keeps detailed API usage records for 90 days; no per-call log for the member is documented (7 of 15). security.txt is valid until 7 November 2027 with hello@neverapply.co, and the contact page routes security reports to security@neverapply.co with a reply within 24 hours; no bug bounty, SOC 2 or ISO 27001 found (6 of 20). 26+18+9+7+6 = 66.

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.

NeverApply 45

Hosted reading, for the MCP server at https://neverapply.co/mcp with the Jobs API described. No status page was found. None is linked from the home page, llms.txt (which lists none) or the MCP page, and https://neverapply.co/status answered a client error (0). No readable incident history, so the floor (5). auth.md publishes budgets with numbers per member and OAuth client, 60 requests a minute on Free and 300 with full access, 50 or 2,000 read calls and 500 or 10,000 search rows a day, 3 or 30 application sends a day and 5 concurrent requests per token, with daily resets at midnight UTC; the page says they are monitor-only for now, and the OpenAPI file gives the Jobs API 1,000 to 250,000 calls a month by plan (15). auth.md says to respect Retry-After on 429 and the reset and retry fields on MCP limit errors, to retry safe reads with bounded backoff and never to repeat an application action blindly; the apply-to-jobs skill passes an idempotency_key on apply_to_job and a review_version on approvals and answers (15). No SLA on any plan was found (0). Nothing on the MCP page, auth.md or llms.txt labels the server beta or preview; the Telegram agent and Envoy marked 'soon' are not this surface (10). 0+5+15+15+0+10 = 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.

NeverApply 57

MCP reading, with the Jobs API described. The 15 tools' input schemas were not read, since no session was opened and the server card at /.well-known/mcp/server-card.json lists tools only as 'dynamic'. An OpenAPI 3.1 file at https://neverapply.co/openapi.json covers 7 GET operations of the Jobs API with typed parameters, but every 200 response is typed as an integer constant (422, 401, 404 or 200) with no job schema, and no pagination fields are defined, so partial (12 of 25). llms.txt and a Markdown authorisation guide at https://neverapply.co/auth.md (10). The three skills and GEMINI.md in the plugin repository say when to use each tool, in what order, which IDs to trust and where to stop and ask, and the MCP page groups the tools by access level; the hosted tool descriptions were not read (12 of 20). Jobs API parameters carry enums (experience level, salary period, visa sponsorship, clearance, education, sort), bounds (per_page 1 to 100, 500 or 1,000) and patterns on country codes; the MCP arguments are named in the skills without types (10 of 15). auth.md documents 401, the OAuth error codes, 429 and isError inside a 200, the skills name waiting_for_answers, open_review, upgrade_required and matches_state, and the OpenAPI description lists five error codes, but its components define different error shapes and no request or response example was found (8 of 15). /v1 paths, OpenAPI version 1.0.0 and a repository tag v1.0.0, but no changelog; /changelog answered a client error (5 of 15). 12+10+12+10+8+5 = 57.

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.

NeverApply 57

Closed hosted service under terms (last updated 18 October 2026) naming Kasovy LLC, registered in Wyoming, with Wyoming law and a liability cap of 12 months' fees or USD 100; the plugin repository of manifests and skills is MIT, copyright Kasovy LLC (17 of 30). The privacy policy (26 October 2026) gives retention periods (7 days for resumes uploaded without an account, 90 days for detailed API usage records and relay mail, a 30-day frozen period before deletion, and what is kept after it), says providers don't train on content under their API terms and that demographic answers are not used for matching, and the extension has its own policy (28 September 2026) saying nothing leaves the device unless AI answers are turned on; no DPA was found, and hashed emails and click IDs go to ad platforms (22 of 30). No deprecation policy or dated notices; the terms promise notice by email or in the product before material changes, and the switch to guest search was recorded only in a commit (4 of 20). Providers are named (OpenAI and Anthropic through Cloudflare's AI Gateway, Google Gemini, AWS S3 and SES, TypeSafe, Stripe, Apple, Google, RevenueCat, Expo, PostHog, Sentry, Gravatar, and Meta, TikTok, Google and X for ads), resume files are stored in AWS eu-central-1, and most providers are in the United States under standard contractual clauses (16 of 20). 17+22+4+16 = 59.

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.

NeverApply 66

MCP reading. 15 tools, 6 read, 6 edit and 3 apply, in the 11 to 30 band (15); guests see a two-tool subset and scopes split read, edit and apply access, though whether tools/list narrows by scope was not read (2 back, 17 of 25). search_jobs takes the user's filters with up to 20 results a call, get_matches pages with next_cursor, list_applications filters by status (needs_answer, ready_to_send, stale, interview, offer), and the Jobs API has a fields sparse fieldset, per_page and cursor feeds (18 of 20). auth.md gives an action for 401, 429 and the OAuth errors, MCP limit errors carry reset and retry fields, and results carry status and next_action the skills act on; no full code list, and the Jobs API's documented envelope and component schemas disagree (13 of 20). apply_to_job takes an idempotency_key, approvals and answers take review_version, a repeat tailor_resume call reads the same copy without paying twice, and auth.md says never to repeat an application blindly; readOnlyHint and destructiveHint were not read (12 of 20). Most tools need one ID, but there is no official SDK (6 of 15). 17+18+13+12+6 = 66.

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.

NeverApply 45

No x402, MPP or L402 on the pricing page, llms.txt, auth.md or the MCP page; plans are Stripe subscriptions and the terms say MCP tools perform no financial transactions (0). Plan prices are public without a login, Pro $29 and Max $49 a month ($19 and $39 a month billed yearly) with 150 and 450 credits a month and 1 credit per application, and the OpenAPI file prices the Jobs API at $19, $49 and $149 a month for 10,000, 50,000 and 250,000 calls; credit pack prices are not listed (15 of 20). Free is $0 with no card, 10 applications once, 5 match previews a day and 50 MCP reads a day per client, and the Jobs API has a free 1,000 calls a month (20). Guest search_jobs and get_job need no account, but every other tool, applying among them, needs a person to sign in or create an account and verify an email on the hosted page, so partial (10 of 20). 0+15+20+10 = 45.