Ashby vs NeverApply

Ashby 81

Graded on the public API, with the beta MCP server noted. Statuspage site at status.ashbyhq.com with separate Ashby API, Reports API and Job Post API components (20). The history feed, read on 2 November, lists 13 incidents between 4 August and 2 November 2026. Each touches one integration, one region, one feature or some users, namely Certn (7 to 9 August), Dropbox Sign (31 August and 21 October), bulk import (10 September), South East Asia (21 to 28 September), delayed data in search, reports and the API (5 October), candidate booking (6 October), job board submissions for 43 minutes (14 October), reporting data, AI functions and BambooHR (21 October), sporadic access failures through Cloudflare (23 October) and an hour of platform latency (26 October). None was an API outage, so minor only (20). 1,000 requests a minute per key, 15 report starts a minute and 120 MCP requests a minute (15). Reports document 429 with advice to wait and retry, and a changelog entry dated 14 October 2026 in its address and posted on 21 October says per-key rate limits answer 429 and partner-wide throttling adds an X-RateLimit-Scope header. No Retry-After header, backoff schedule or idempotency key was found (8). A 99.9 per cent uptime SLA with service credits is published, and applies only where the customer's Master Service Agreement references it (8). The API is generally available, the MCP server is beta (10). 20 + 20 + 15 + 8 + 8 + 10 = 81.

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.

Ashby 10

No x402, MPP or L402 (0). Foundations prices are public by company size, $300 to $900 a month. Plus and Enterprise are by quote, and nothing is priced per call (10). No free tier or trial found, and each plan starts with a sales call (0). An Organisation Admin creates the key in the web app (0). Total 10.

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.

Ashby 82

Every endpoint page carries an OpenAPI 3.1 definition with shared schemas, but we found no single downloadable spec file (20). llms.txt indexes 244 reference pages, all served as Markdown (10). Descriptions state purpose and the permission needed, and some say when to use a neighbouring endpoint, such as application.create against applicationForm.submit (14). Inputs are typed with UUID patterns, required lists, maximums and additionalProperties: false. auditLog.list filters are free strings checked against a published vocabulary (13). Request and response examples on each page. Error codes are listed for some endpoints, and the only documented response status is 200 with a success or error body (10). Date-based versions with a lifecycle table, version.list and a dated changelog (15). Total 82.

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.

Ashby 78

Closed service with published customer terms, AI terms and product-specific terms (15). Privacy policy, a DPA on request, a 30-day erasure clause after termination and AI terms that rule out training on customer data. Retention is set by each customer, and no default period is published (22). API versions have a lifecycle table and at least six months' notice before retirement. No version has been deprecated yet, so no dated notice exists (17). Sub-processors are listed with purposes on the trust centre, and data is stored in the United States on AWS (16). Total 70.

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.

Ashby 64

The newest changelog entry is dated 30 October 2026, three days before the check (30). The changelog's first three pages alone hold 30 dated entries from 4 September to 30 October 2026, none marked breaking (20). Public changelog and a support address that asks for the request id. No public forum or issue tracker found (10). No official SDK found, and the MCP server isn't in the official MCP registry under an Ashby namespace, per the 7 October check (0). Reference pages and their OpenAPI definitions are regenerated with each versioned release. There are no packages to check (4). 30 + 20 + 10 + 0 + 4 = 64.

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.

Ashby 59

limit up to 100 and opt-in expand keep responses sized. No field selection (15). Cursor pagination, sync tokens for incremental reads, date filters and separate .search endpoints for lookups (20). Errors carry a code, a message and a request id, and pagination errors say how to recover. Failures arrive as HTTP 200 with success: false, which a client checking status codes will miss (14). No idempotency keys. A 28 September 2026 fix stopped retried stage changes queueing duplicate rejection emails. MCP tool annotations need a login to read (3). Few required parameters on the calls we read, such as two for application.changeStage. No official SDK found (7). Total 59.

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.