# Check > Check is an embedded payroll API from Check Technologies in New York. Software platforms build US payroll on it for their own customers, with tax calculation, payment and filing handled by Check. Access is by partner agreement. - Canonical: https://www.anchorterminal.com/tools/check-payroll - Markdown: https://www.anchorterminal.com/tools/check-payroll.md (~7,700 tokens) - Slim: https://www.anchorterminal.com/tools/check-payroll.min.md (~1,980 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/check-payroll.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade B · 67.5/100 · rank #193 of 629 · #2 in Payroll infrastructure · not agent-ready · confidence medium** ## Assessment Graded as embedded payroll through a partner API key, not access to an existing employer's payroll account. The API has idempotency keys on writes, a required preview before approval and queryable request logs. No price is public, a sandbox key comes through Check's sales team, and one API key carries the whole partner account. ## Facts | Field | Value | | --- | --- | | Vendor | Check Technologies, Inc. (https://www.checkhq.com) | | Kind | HTTP API | | Category | Payroll infrastructure (https://www.anchorterminal.com/categories/payroll) | | Transport | HTTP | | Endpoint | `https://api.checkhq.com` | | Auth | OAuth or key · A partner API key sent as `Authorization: Bearer`, one for sandbox and one for production, issued by Check after a request through its sales contact. The key carries the whole partner account, with no per-key scopes found. Check says unused keys expire, last activity is shown and IP restrictions can be set through the account team. Integration partners get OAuth tokens (authorisation code grant, with refresh tokens) limited to one employer and one permission level, after a Check partner authorises them. The hosted MCP server accepts the API key or a Console OAuth login that runs with the Console user's permissions. This listing grades embedded-payroll partner access. Check has no route to an existing employer's payroll account outside a partner platform. | | Pricing | Paid (Paid) · No public prices. checkhq.com/pricing returns 404 and the site's buttons open a sales contact form. A sandbox exists at sandbox.checkhq.com under a Sandbox User Agreement, but the documentation says to request an API key from Check, so an agent can't start without a person contacting sales. Production needs a partner agreement. The Usage API reports billable companies, employees and contractors each month, with no unit price published (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the documentation index, the API reference pages read or the website (checked 2026-10-08). | | Licence | Proprietary service under Check's terms of service and partner agreement. The MCP server and CLI on GitHub are MIT | | Source | https://github.com/check-technologies/mcp-server-check | | Docs | https://docs.checkhq.com | | llms.txt | https://docs.checkhq.com/llms.txt | | Last release | 2026-10-07 | | GitHub stars | 18 (as of 2026-10-08) | | Surface graded | The REST API used by a software platform under an embedded-payroll partnership, with the hosted MCP server as a second route to the same endpoints. Check has no API for reaching an existing employer's payroll account outside a partner platform | | Base URLs | https://sandbox.checkhq.com (sandbox) and https://api.checkhq.com (production). MCP at https://mcp.sandbox.checkhq.com/check/mcp and https://mcp.checkhq.com/check/mcp | | Credentials | Partner API key as a Bearer token, one per environment. Unused keys expire, last activity is shown, and IP restrictions are available through the account team. Integration partners receive OAuth access and refresh tokens limited to one employer and one permission level. Hosted MCP also accepts a Console OAuth login | | Payroll flow | Create a payroll, add payroll items and contractor payments, preview (synchronous up to 500 of each, asynchronous up to 2,500), approve, and reopen a pending payroll to edit it. Approval needs a succeeded preview | | Rate limits | 10, 20, 40 or 80 requests a second by payees paid in the prior month (under 1,000, 1,000 to 10,000, 10,000 to 50,000, 50,000 and over), 100 concurrent requests, 10 a second in sandbox. 429 with `Retry-After` | | Pagination | Cursor pagination with `next` and `previous` URLs. Default page size 25, with `limit` up to 100 or 500 on 19 listed endpoints | | Idempotency | `X-Idempotency-Key` header. The first response is stored for 24 hours and replayed, including 500 errors | | Errors | JSON envelope with `type`, `message` and optional `input_errors` carrying `field` and `field_path`. A published table of error types (https://docs.checkhq.com/reference/error-codes) | | Versioning | Dated versions through the `Check-Version` header, with an account default. Six versions since 2021-01-15, the latest 2025-01-01 (https://docs.checkhq.com/page/api-changelog) | | Logs | GET /logs and GET /logs/{id}, `X-Request-Log-Id` on every response, and an API Logs tab in Console covering 14 days | | MCP server and CLI | check-technologies/mcp-server-check, MIT, Python 3.10 or later, version 0.1.0, installed from a git clone with uv. 270 tools in 18 toolsets behind `search_tools`, `run_tool` and `list_toolsets`. Read-only mode, toolset and tool filters, and `CHECK_CONFIRM_DESTRUCTIVE` | | Sensitive data | SSNs and bank account numbers are returned only by the Sensitive Data API, which needs Check's approval, MFA for all users and additional terms | | Certifications | SOC 2 Type II per checkhq.com/company/security. Bug bounty through Federacy. Money transmitter licences in 50 US states and DC | | Status | status.checkhq.com on Atlassian Statuspage with four components (API, Console, Onboard, Payments) | | Capabilities | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors | | Tags | hosted, embedded-payroll, us-payroll, api-key, oauth, mcp, llms-txt, sandbox, webhooks, sales-led, partner-approval, status-page, bug-bounty, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/check-payroll.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 80 | 16.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 78 | 12.7 | | Agent ergonomics | 13% | 16.2 | 83 | 13.5 | | Security & auth | 14% | 17.5 | 74 | 12.9 | | Payments & pricing | 10% | 12.5 | 5 | 0.6 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 72 | 6.3 | | Transparency & trust (editorial 38, provenance 86) | 7% | 8.8 | 62 | 5.4 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **67.5 → B** | ### Why each score - Reliability 80: Read with the hosted lines and scored on the REST API under an embedded-payroll partnership. status.checkhq.com on Atlassian Statuspage lists four components (API, Console, Onboard, Payments) with incident history (20). Three incidents between 10 July and 8 October 2026. The Usage API was unavailable for about 100 minutes on 9 September, marked minor, and notices on 31 July and 4 September concerned deposits delayed at receiving banks, with no failed processing found on Check's side. Payroll endpoints were not affected in the window, so this reads as minor incidents only (20). An earlier incident on 6 June 2026, marked major, returned errors on payroll preview and approval for about four and a half hours and falls outside the 90 days. Limits with numbers, 10 to 80 requests a second by tier and 100 concurrent requests (15). 429 carries `Retry-After`, every response carries `RateLimit-Limit` and `RateLimit-Remaining`, and `X-Idempotency-Key` covers writes for 24 hours (15). No SLA is published, and the terms of service make no representation about uptime unless agreed in writing. The startups page claims 99.999 per cent historical uptime, which is a vendor claim (0). The REST API carries no beta label. The MCP server is labelled beta in its usage terms (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 78: Each reference page embeds an OpenAPI 3.1 fragment for its one operation, with typed parameters and request bodies. No single downloadable specification was found, and response bodies are given as examples, not schemas (15 of 25). llms.txt indexes 367 lines of guides and reference, and each page is served as Markdown (10). Guides say when to use synchronous or asynchronous preview and how sandbox differs from production. Reference descriptions are one line on most operations read (14 of 20). Request bodies list required fields and formats such as dates. No enums were seen on the operations read, and query filters are plain strings (10 of 15). Curl examples in the quickstart and guides, an error envelope with `input_errors` and `field_path`, and a table of error types. Most reference pages document only the success response (14 of 15). Dated versions through `Check-Version`, an API upgrades page listing six versions since 2021-01-15, and a product changelog (15). - Agent ergonomics 83: `limit` sizes a page, and since version 2025-01-01 payrolls omit items unless `include_items` is set. No field selection. The MCP server exposes three meta-tools over 270 tools, with toolset filters and a read-only mode (20 of 25). Cursor pagination with `next` and `previous`, page sizes up to 100 or 500 on 19 endpoints, filters by company, workplace, status, ids and metadata (18 of 20). Typed error codes, `field_path` pointing at the invalid input, `X-Request-Log-Id` on every response and 409 `preview_superseded` on a stale approval (18 of 20). `X-Idempotency-Key` on writes with a stated 24-hour window and retry guidance, and the MCP server's source sets readOnlyHint, destructiveHint and idempotentHint on every tool (20). Few required fields on the operations read. No official SDK in a general programming language was found, only a Postman collection, a Python CLI and React Components (7 of 15). - Security & auth 74: A partner API key in the `Authorization` header, one per environment, carrying the whole partner account. Check says unused keys expire, last activity is shown and IP restrictions are available. Integration partners get OAuth tokens limited to one employer and permission level, and hosted MCP accepts a Console OAuth login bound to that user's role. No per-key scopes were found (22 of 30). The MCP server has read-only mode, toolset and tool filters and optional confirmation for destructive tools. The API requires a succeeded preview before approval and gates SSNs and account numbers behind the separately approved Sensitive Data API. No read-only API key was found (15 of 20). The MCP server's instructions tell the model to confirm before writes that affect payroll or money movement. No guidance on untrusted text in records was found (6 of 15). GET /logs with filters, `X-Request-Log-Id`, Console API logs for 14 days, last activity per key, and sensitive-data access logged (14 of 15). SOC 2 Type II, a bug bounty through Federacy and regular penetration tests per the security page. No security.txt (17 of 20). - Payments & pricing 5: Read with the hosted rubric. No x402, MPP or L402 (0). No public price. checkhq.com/pricing returns 404 and the site asks visitors to get in touch (0). A sandbox exists under a Sandbox User Agreement, but the key is requested from Check through its sales contact, so partial credit (5 of 20). A person must contact sales and sign a partner agreement before production (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 72: The product changelog's latest entry is 10 September 2026 and the MCP server repository's latest commit 7 October 2026 (30). Four dated changelog entries since 10 July (13 and 20 August, 9 and 10 September), and 109 commits to the MCP repository on 27 days in the same period (20). Closed service with a dated changelog, a help centre and developer support. The MCP repository is public with 10 open issues and pull requests, whose replies we couldn't read (10 of 15). No official SDK in a general programming language was found, and the official MCP registry returned no entry for Check. The CLI and MCP server are current (5 of 15). The repository runs lint and 465 tests in CI with a lock file. It has no tags and isn't published to PyPI (7 of 10). - Transparency & trust 62: Closed service. Terms of service (3 September 2021), a Sandbox User Agreement and employer terms are published. The partner agreement that governs API use is not. The MCP server and CLI are MIT (17 of 30). The privacy policy (effective 18 April 2024) says information is kept as long as needed, with no periods. The security page mentions a DPA, of which no public copy was found. The documentation states what request logs redact and that Console shows 14 days (12 of 30). Breaking changes ship as dated versions with a written definition of what counts as breaking, and a migration guide covers the legacy Tax Filings API. No notice period or removal dates were found (9 of 20). No sub-processor list or hosting locations were found on the security, privacy or terms pages (0). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (17 items): https://www.anchorterminal.com/fixes/check-payroll.md (JSON https://www.anchorterminal.com/fixes/check-payroll.json) ### What we couldn't check - unchecked: live API behaviour. We had no sandbox key, so limits, errors and the preview flow are as documented, apart from a 403 `not_authenticated` response and `X-Request-Log-Id` header seen on an unauthenticated request - unchecked: whether a single OpenAPI file can be downloaded. docs.checkhq.com/openapi and /openapi.json answered 429 to our reader, and the reference pages embed one operation each - unchecked: the partner agreement, the DPA and any SLA in it. None is published - unchecked: per-key scopes or read-only API keys in Console, which sits behind a login - unchecked: the Federacy bug bounty terms, which sit behind a sign-in at federacy.com/check - unchecked: replies on the MCP repository's 10 open issues and pull requests, which aren't in the git clone - Changelog entries older than the first page (81 pages) were not read, so the count of entries in the last 90 days is a minimum of four ### Sources - documentation index for agents: (seen 2026-10-08) - authentication: (seen 2026-10-08) - rate limits and 429 handling: (seen 2026-10-08) - idempotent requests: (seen 2026-10-08) - pagination: (seen 2026-10-08) - errors and error codes: (seen 2026-10-08) - request logs: (seen 2026-10-08) - payroll preview and approval: (seen 2026-10-08) - approve a payroll reference: (seen 2026-10-08) - sandbox and production differences: (seen 2026-10-08) - versioning and API upgrades: (seen 2026-10-08) - hosted MCP server: (seen 2026-10-08) - integration partner OAuth guide: (seen 2026-10-08) - sensitive data API: (seen 2026-10-08) - MCP server and CLI source, usage terms, CI: (seen 2026-10-08) - status incidents: (seen 2026-10-08) - security page: (seen 2026-10-08) - product changelog: (seen 2026-10-08) - terms of service: (seen 2026-10-08) - sandbox user agreement: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - official MCP registry search: (seen 2026-10-08) - domain registration: (seen 2026-10-08) ## Who's behind it (provenance 86/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Check Technologies, Inc. | 20/20 | | Domain age | checkhq.com, registered 2006-10-28 (19 years) | 15/15 | | Endpoint on the vendor's domain | api.checkhq.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.checkhq.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The privacy policy (effective 18 April 2024) names Check Technologies, Inc., 228 Park Ave. S, PMB 14961, New York, NY 10003. The site footer also names Check Payments LLC (NMLS #2103307). The terms of service are dated 3 September 2021. Sandbox use is also governed by a Sandbox User Agreement at checkhq.com/company/sandbox-user-agreement. www.checkhq.com/.well-known/security.txt and checkhq.com/.well-known/security.txt return 404. The security page sends vulnerability reports to a bug bounty at federacy.com/check. The API answers at api.checkhq.com and sandbox.checkhq.com, and the hosted MCP server at mcp.checkhq.com and mcp.sandbox.checkhq.com. RDAP for checkhq.com gives a registration date of 2006-10-28 and Squarespace Domains II LLC as registrar. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.checkhq.com/company/terms), read 2026-10-08, dated 2021-09-03, states 6 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "Use any data mining, robots or similar data gathering or extraction methods designed to scrape or extract data from the Services;" - To know. Says access can be ended without notice or for any reason. "Except as otherwise agreed by us in writing, we reserve the right to modify the Services or to suspend or stop providing all or portions of the Services at any time." - To know. Has not been updated for three years or more. "Last updated: September 3, 2021" - Gives the date it was last updated. Last updated 2021-09-03. - Names the governing law or courts. Disputes go to the courts of New York. - States a limit on its liability. Capped at the fees paid in the 6 months before the claim. - Not found in the text. Says how changes to the terms are announced. - Also in the text (2026-10-08). Check takes a perpetual, irrevocable and sublicensable licence over User Content and over any name, username or likeness supplied with it. "You grant us a perpetual, irrevocable, nonexclusive, royalty-free, worldwide, fully paid, and sublicensable license to use, reproduce, modify, adapt, publish, translate, create derivative works from, distribute, publicly perform and display your User Content" - Also in the text (2026-10-08). Developing or using an application that interacts with the Services requires Check's prior written consent. "Develop or use any applications that interact with the Services without our prior written consent;" - Also in the text (2026-10-08). Total liability is capped at the amounts paid to Check in the six months before the events behind the claim. "will not exceed the amounts you have paid to us for use of the Services in the six (6) month period immediately preceding the events giving rise to the applicable claim." **Privacy policy** (https://www.checkhq.com/company/privacy), read 2026-10-08, dated 2024-04-18, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "These disclosures may be considered a “sale” or the processing/sharing of information for targeted advertising purposes under applicable law." - Gives the date it was last updated. Last updated 2024-04-18. - Gives a privacy contact. privacy@checkhq.com. - Not found in the text. Says where data is transferred or stored. ## Live (updated 2026-10-08 17:38 UTC) - Right now: up, HTTP 200, 1 s, checked 2026-10-08 17:36 UTC (get on `https://api.checkhq.com`) - Uptime 24h 100.0% (25 probes) · 30 days 100.0% (25 probes) · p50 728 ms · p95 1 s - Vendor status page: none, All Systems Operational - security.txt: none - Always current: https://www.anchorterminal.com/api/v1/live/check-payroll.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - `X-Idempotency-Key` is accepted on writes and stored for 24 hours, and a 429 carries `Retry-After` with `RateLimit-Limit` and `RateLimit-Remaining` on every authenticated response - A payroll must have a succeeded preview before approval, and `preview_started_at` makes approval fail with 409 `preview_superseded` if the preview is stale - Every response carries `X-Request-Log-Id`, and GET /logs returns request logs with SSNs, bank account numbers and the `Authorization` header redacted - The MCP server starts with three meta-tools over 270 tools, with read-only mode, toolset filters and optional confirmation for destructive tools - llms.txt indexes the documentation, and each page is served as Markdown with an OpenAPI 3.1 fragment per operation ## Weaknesses - No public price and no self-serve signup. The documentation says to request an API key through Check's sales contact - An API key carries the whole partner account. No per-key scopes or read-only keys were found in the reviewed documentation - No official SDK in a general programming language was found. The CLI and MCP server install from a git clone, not from PyPI - No SLA is published. The terms of service make no representation about uptime unless agreed in writing - No sub-processor list, hosting location or published DPA text was found, and the privacy policy states no retention periods ## Before you call it (notes for agents) 1. Use https://sandbox.checkhq.com with the sandbox key and https://api.checkhq.com with the production key. A key is not valid across environments 2. Preview a payroll before approving it, then pass `preview_started_at` to POST /payrolls/{id}/approve so a stale preview fails with 409 3. Send `X-Idempotency-Key` on every write. Keys expire after 24 hours, so list the resource before retrying later than that 4. On 429 wait for `Retry-After`. The limit is 10 requests a second in sandbox and for partners paying fewer than 1,000 payees a month, with 100 concurrent requests 5. Connect the MCP server with `?read_only=true` or `X-MCP-Readonly: true` unless writes are intended. In production, approving a payroll moves money ## Connect First request: ```bash curl -X POST https://sandbox.checkhq.com/companies \ -H 'Content-Type: application/json' \ -H 'Authorization: Bearer ' \ -d '{"address": {"line1": "20 W 34th St", "postal_code": "10001", "city": "New York", "state": "NY"}, "start_date": "2020-05-20", "trade_name": "Good Web Design", "legal_name": "Good Web Design, Inc."}' ``` Claude Code: ```bash claude mcp add --transport http check https://mcp.sandbox.checkhq.com/check/mcp \ --header "Authorization: Bearer your-api-key-here" ``` MCP client configuration: ```json { "mcpServers": { "check": { "type": "url", "url": "https://mcp.sandbox.checkhq.com/check/mcp" } } } ``` Through letme (picks today, calling later): https://letme.dev/check-payroll (letme picks it for payroll.embedded, the top-graded tool for the job, letme picks it for payroll.run, the top-graded tool for the job, letme picks it for payroll.tax-filing, the top-graded tool for the job). letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Gusto | B | 63.3 | 283 | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors | no | https://www.anchorterminal.com/tools/gusto.md | | Salsa | D | 46.1 | 565 | payroll.run, payroll.embedded, payroll.employees, payroll.tax-filing, payroll.contractors | no | https://www.anchorterminal.com/tools/salsa.md | | Zeal | E | 45.4 | 569 | payroll.run, payroll.embedded, payroll.employees, payroll.contractors, payroll.tax-filing | no | https://www.anchorterminal.com/tools/zeal.md | | Finch | BB | 71.6 | 99 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/finch.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The API creates companies, workplaces, employees and contractors, builds payrolls from payroll items and contractor payments, previews and approves them, and exposes paystubs, payments, tax filings and W-2 statements (source: ) - Payrolls with up to 500 payroll items and 500 contractor payments preview synchronously, and up to 2,500 of each asynchronously, as of API version 2025-01-01 (source: ) - The hosted MCP server at https://mcp.checkhq.com/check/mcp and https://mcp.sandbox.checkhq.com/check/mcp accepts a Console OAuth login or an API key, and exposes 270 tools in 18 toolsets through three meta-tools (source: ) - Check's MCP Usage Terms label the MCP server beta and say it may change or be discontinued at any time (source: ) - Rate limits scale with payees paid in the prior month, from 10 to 80 requests a second, with 100 concurrent requests per partner (source: ) - Sandbox relaxes production rules. EIN and bank account verification succeed automatically, and payroll can run while onboarding steps are still blocking (source: ) - The security page lists SOC 2 Type II, money transmitter licences in 50 US states and DC, and a bug bounty run through Federacy (source: ) - status.checkhq.com lists three incidents between 10 July and 8 October 2026. The Usage API was unavailable for about 100 minutes on 9 September, and two notices on 31 July and 4 September concerned deposits delayed at receiving banks (source: ) ## Compare - [Check vs Gusto](https://www.anchorterminal.com/compare/check-payroll-vs-gusto.md): B 67.5 vs B 63.3 - [Check vs Salsa](https://www.anchorterminal.com/compare/check-payroll-vs-salsa.md): B 67.5 vs D 46.1 - [Check vs Zeal](https://www.anchorterminal.com/compare/check-payroll-vs-zeal.md): B 67.5 vs E 45.4 - [Check vs Finch](https://www.anchorterminal.com/compare/check-payroll-vs-finch.md): B 67.5 vs BB 71.6 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on checkhq.com or one of its subdomains, or the README of github.com/check-technologies/mcp-server-check. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "check-payroll", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Check on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Check on Anchor Terminal](https://www.anchorterminal.com/badges/check-payroll.svg)](https://www.anchorterminal.com/tools/check-payroll) ``` Plain link: ```html Check on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Check is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/check-payroll-dark.png - Light: https://www.anchorterminal.com/assets/share/check-payroll-light.png