NeverApply vs Workable

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.

Workable 83

Graded on the REST API with the hosted lines. Statuspage site at workable.statuspage.io with 24 components and incident history, none named for the API (20). Three incidents since 4 August 2026, read from the history feed and each incident's page. They are 4 September (email delays to Microsoft 365 recipients, Login & signup), 21 October (the e-signature provider's emergency maintenance, E-signatures, 76 minutes) and 29 October (a blank page when creating or editing jobs in the app, Workable Recruiting, about 2 hours 20 minutes). The 21 October incident names errors when approving in e-signature workflows, offer letters included, and the API has an approval call for them, so it touches the product. It is partial (one provider, 76 minutes), so minor. The other two are an outside email path and the app's job editor, while jobs are read-only through the API, so neither counts. Minor incidents only (20). The earlier 25 wasn't a checklist value. Rate limits published as 10 requests per 10 seconds for account tokens and 50 for OAuth and partner tokens (15). 429 with X-Rate-Limit-Limit, -Remaining and -Reset headers on every response, but no backoff guidance and no idempotency keys for writes (8). A 99.8 per cent monthly uptime SLA with service credits, per the 7 October check (10). The API is v3 and the MCP page carries no beta label (10). 20 + 20 + 15 + 8 + 10 + 10 = 83.

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.

Workable 30

No x402, MPP or L402 (0). Plan prices are public, from $299 a month for 1 to 20 employees, and nothing is priced per API call (10). 15-day trial without a card (20). A person registers in a browser and an admin generates the token in settings. The site's in-browser start_free_trial WebMCP tool fills the same form, which we read as a human signup flow (0).

NeverApply 50

Closed service. The latest dated change is a commit of 31 October 2026 to kasovy/neverapply-mcp documenting guest access to search_jobs and get_job, after a tag v1.0.0 on 21 October; the privacy policy was updated on 26 October and the terms on 18 October (30). One tagged release and 16 commits from 25 September to 31 October 2026, with no changelog or release notes, so partial (10 of 20). No public changelog; support is a contact form, hello@neverapply.co and security@neverapply.co, with a stated reply within one business day and a median first reply of about two hours in staffed hours; GitHub issues could not be read because the GitHub API was not available to us (5 of 15). The server card names co.neverapply/neverapply and llms.txt says it was published to the official MCP registry on 25 September 2026, but the registry could not be read, so it is scored absent; no official SDK (0 of 15). The plugin repository has no runtime dependencies and a CI workflow that validates every manifest against its published schema, with a release workflow on tags; actions are pinned to major tags and the run results were not readable (5 of 10). 30+10+5+0+5 = 50.

Workable 35

Reference pages for surveys and performance review cycles were updated on 22 October 2026 (30). In a sample of 19 of the 110 reference pages, two dated documentation changes fall in the last 90 days, 5 October (requisition custom attributes) and 22 October, and no changelog exists, so fewer than three (0). No public changelog. Support is by email at integrations@workable.com and a help centre (5). No official SDK was found. The official MCP registry lists io.github.external-submissions-workable/jobs-by-workable at jobs.workable.com/mcp, a public job-search server outside the graded API, and third-party entries (0). No packages to assess (0).

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.

Workable 69

Closed service with published terms, last updated 2 March 2026, with archived versions (15). The privacy policy, the DPA and the terms agree. The DPA allows deletion of personal data 90 days after termination and promises 30 days' notice before a new sub-processor (24). No deprecation policy or dated notices found (0). 26 sub-processors listed with corporate location and purpose, with hosting on AWS and Google Cloud in US East (18).

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.

Workable 55

List endpoints take limit and there is no field selection on the REST API. The MCP server lists 94 tools with no documented toolsets, though its advanced search tools take column selection (12). limit, since_id, max_id, created_after and updated_after, a paging.next URL, and filters by stage, email and state (18). JSON error messages with validation_errors by field on 422, and 400, 401, 403, 404 and 409 documented. Messages are short, such as Not found (13). No idempotency keys. Rating a candidate has an upsert endpoint, and we couldn't read MCP tool annotations without a token (5). Few required parameters and a default limit of 50, but no official SDK was found (7).

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.

Workable 67

llms.txt now lists 104 operations on 110 reference pages (85 operations on 7 October), with survey and performance review cycle endpoints whose pages are dated 22 October 2026. Each operation has an OpenAPI 3.1 fragment (spec version 3.16.2) on its reference page. No single downloadable spec was found, and workable.readme.io/openapi redirects to a 404 page (18). llms.txt on workable.readme.io and every page served as Markdown (10). Every llms.txt entry names the required scope and the token types accepted, and the MCP page says when to pick one tool over another, such as copy_candidate against relocate_candidate (15). Typed parameters, but only 11 enums across the fragments on 7 October, and values such as event types sit in prose. The new survey pages list states[] values in prose (8). 259 example blocks on 7 October, with 401 documented on 54 operations, 404 on 55 and 422 on 15, and 429 on none; the counts weren't redone over the new pages (11). The version is in the path (v3) and the spec carries a number, but no changelog was found, and workable.readme.io/changelog returns 404 (5).