# Employment Hero Payroll MCP by usefulapi (remote · keypay.usefulapi.io)

Read Employment Hero Payroll pay runs, payslips, timesheets and leave; approve or decline leave.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `keypay.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-keypay/keypay.md), [page](https://verifymcp.io/servers/io-usefulapi-keypay/keypay)

## Channel facts

- Endpoint: `https://keypay.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.5.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4056 tokens (~156/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "keypay_list_pay_runs" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Employment Hero Payroll MCP by usefulapi server?

Employment Hero Payroll MCP by usefulapi is a hosted endpoint at https://keypay.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-keypay 'https://keypay.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-keypay": {
      "url": "https://keypay.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-keypay": {
      "type": "http",
      "url": "https://keypay.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-keypay]
url = "https://keypay.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-keypay": {
      "type": "remote",
      "url": "https://keypay.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-keypay --url 'https://keypay.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-keypay:
    url: "https://keypay.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-keypay": {
      "Transport": "http",
      "Url": "https://keypay.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-keypay -t streamable-http -u 'https://keypay.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-keypay": {
      "type": "http",
      "url": "https://keypay.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 62, 0)

- [functional] Server version: 1.5.2 → 1.5.3
- [functional] Server version: 1.5.0 → 1.5.2

### 2026-10-24 (score 62, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Schema quality: excellent → good
- [functional] Server version: 1.4.0 → 1.5.0
- [functional] Server version: 1.3.0 → 1.4.0
- [functional] Server version: 1.1.0 → 1.3.0

### 2026-10-23 (score 61, 0)

- [functional] Server version: 1.0.1 → 1.1.0

### 2026-10-22 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-21 (score 61)

First indexed and scored.

## MCP tools (26)

### `keypay_get_user` (~35 tokens)

Get current user

The Employment Hero Payroll user this API key belongs to: id, email, display name and time zone. GET /user.

### `keypay_list_businesses` (~189 tokens)

List businesses

List the payroll businesses this user can access: id, name, region, legal name, contact details, pay cycle, number of employees. Start here: most other tools need a business id. GET /business (OData).

Input parameters:

- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_get_business` (~62 tokens)

Get business

One business by id: name, legal name, contact, address, ABN/company details, leave year, standard hours, pay cycle. GET /business/{businessId}.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).

### `keypay_list_employees` (~237 tokens)

List employees

List the business's employees with basic details: id, name, preferred name, gender, date of birth, contact details, address, start and end date, external id. Tax file, bank and super details are not part of this list. Filter with OData, e.g. "Surname eq 'Smith'". GET /business/{businessId}/employee/details (OData).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_get_employee` (~127 tokens)

Get employee

One employee's full record: name, contact, employment type, status, start/end date, pay schedule, primary location and pay category, rate and rate unit, hours per week, award, leave template, work types, tags. Tax file / national insurance / IRD / NRIC numbers, bank accounts and super member numbers are removed. GET /business/{businessId}/employee/unstructured/{employeeId}.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `employee_id` (integer, required): Employee id (from keypay_list_employees).

### `keypay_get_leave_balances` (~97 tokens)

Get employee leave balances

An employee's leave balances per leave category (accrued amount and unit), optionally as at a date. GET /business/{businessId}/employee/{employeeId}/leavebalances.

Input parameters:

- `as_at_date` (string): Balance as at this date (yyyy-mm-dd); default today.
- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `employee_id` (integer, required): Employee id.

### `keypay_list_pay_runs` (~216 tokens)

List pay runs

List the business's pay runs: id, pay schedule, pay period start/end, date paid, finalised flag, payslips published, notation. Newest first with orderby "PayPeriodEnding desc". GET /business/{businessId}/payrun (OData).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_get_pay_run` (~83 tokens)

Get pay run

One pay run by id: pay schedule, period, date paid, whether it is finalised, notation. GET /business/{businessId}/payrun/{payRunId}.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `pay_run_id` (integer, required): Pay run id (from keypay_list_pay_runs).

### `keypay_list_pay_run_summaries` (~200 tokens)

List pay run summaries

Pay runs with their totals: total hours, gross wages and net wages, plus the usual pay run fields. GET /business/{businessId}/payrun/summary (OData).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_get_pay_run_summary` (~71 tokens)

Get pay run summary

One pay run with its total hours, gross wages and net wages. GET /business/{businessId}/payrun/{payRunId}/summary.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `pay_run_id` (integer, required): Pay run id.

### `keypay_get_pay_run_totals` (~93 tokens)

Get pay run totals per employee

Per-employee totals of a pay run (gross, net, tax withheld, super and the like; the fields depend on the region). Bank payment details are removed. GET /business/{businessId}/payrun/{payRunId}/totals.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `pay_run_id` (integer, required): Pay run id.

### `keypay_get_pay_run_payslips` (~143 tokens)

Get pay slip data of a pay run

Pay slip data for every employee in a pay run, keyed by employee: earnings lines, deductions, tax, super, leave taken and accrued, gross/net and year-to-date totals. Large for big pay runs. Bank account numbers and tax/identity numbers are removed. GET /business/{businessId}/payrun/{payRunId}/payslips.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `pay_run_id` (integer, required): Pay run id.
- `show_all_data` (boolean): Include all pay slip data, not only what is printed on the slip (default false).

### `keypay_list_pay_run_warnings` (~87 tokens)

List pay run warnings

Warnings on a pay run (for example an employee paid below their award rate or with a negative net pay): type, employee and message. GET /business/{businessId}/payrun/{payRunId}/warnings.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `pay_run_id` (integer, required): Pay run id.

### `keypay_list_timesheets` (~250 tokens)

List timesheets

List the business's timesheet lines: employee, start/end time, units, work type, location, status, comments, breaks. Filter by employee or date with OData, e.g. "EmployeeId eq 123 and StartTime gt datetime'2026-04-01T00:00:00'". GET /business/{businessId}/timesheet (OData: $filter, $orderby, $top, $skip).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_get_timesheet` (~70 tokens)

Get timesheet line

One timesheet line by id. GET /business/{businessId}/timesheet/{timesheetLineId}.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `timesheet_id` (integer, required): Timesheet line id (from keypay_list_timesheets).

### `keypay_list_leave_requests` (~183 tokens)

List leave requests

List the business's leave requests: employee, leave category, from/to date, total hours, status (Approved, Pending, Rejected, Cancelled), notes. Filter by status, dates, category, location or employee. GET /business/{businessId}/leaverequest.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `employee_id` (integer): Only this employee.
- `from_date` (string): Only leave starting on or after this date (yyyy-mm-dd).
- `leave_category_id` (integer): Only this leave category (keypay_list_leave_categories).
- `location_id` (integer): Only this location (keypay_list_locations).
- `status` (string): Only requests with this status.
- `to_date` (string): Only leave ending on or before this date (yyyy-mm-dd).

### `keypay_get_leave_request` (~94 tokens)

Get leave request

One leave request: employee, category, dates, hours, status, notes. GET /business/{businessId}/employee/{employeeId}/leaverequest/{leaveRequestId}.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `employee_id` (integer, required): Employee id.
- `leave_request_id` (integer, required): Leave request id (from keypay_list_leave_requests).

### `keypay_list_leave_categories` (~200 tokens)

List leave categories

Leave categories of the business (annual, personal/sick, long service...): id, name, unit type, accrual rule. GET /business/{businessId}/leavecategory (OData).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_list_pay_schedules` (~203 tokens)

List pay schedules

Pay schedules of the business: id, name, frequency, last date paid, last pay run. Bank and tax account details are removed. GET /business/{businessId}/payschedule (OData).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_list_locations` (~192 tokens)

List locations

Locations of the business (sites, departments): id, name, parent, fully qualified name, state. GET /business/{businessId}/location (OData).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_list_pay_categories` (~202 tokens)

List pay categories

Pay categories (earnings types) of the business: id, name, rate unit, loadings, super rate, whether leave accrues. GET /business/{businessId}/paycategory (OData).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_list_work_types` (~192 tokens)

List work types

Work types of the business: id, name, pay category, leave category, short code. GET /business/{businessId}/worktype (OData).

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `filter` (string): OData v3 $filter. Property names are capitalised, e.g. "Surname eq 'Smith'", "StartTime gt datetime'2026-04-01T00:00:00'", "DefaultSuperRate ne 9.5M".
- `orderby` (string): OData $orderby, e.g. "Name" or "PayPeriodEnding desc".
- `skip` (integer): Results to skip (default 0). Pass the previous reply's next_skip.
- `top` (integer): Results per request, 1-100 (default 25; the API caps it at 100).

### `keypay_report_gross_to_net` (~208 tokens)

Gross to net report

Gross-to-net report per employee: earnings by pay category, tax, deductions, super, net pay. Choose a date range (from_date + to_date) or one finalised pay run (pay_run_id). The report has no paging: at most 200 rows are returned (narrow with employee_id or location_id). GET /business/{businessId}/report/grosstonet.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `employee_id` (integer): Only this employee.
- `from_date` (string): Start of the date range (yyyy-mm-dd), with to_date.
- `location_id` (integer): Only this location.
- `pay_run_id` (integer): A pay run id: report that pay run (then from_date/to_date are ignored).
- `pay_schedule_id` (integer): Only this pay schedule.
- `to_date` (string): End of the date range (yyyy-mm-dd).

### `keypay_report_leave_balances` (~136 tokens)

Leave balances report

Leave balances of all employees as at a date, per leave category. The report has no paging: at most 200 rows are returned (narrow with location_id or leave_category_id). For one employee use keypay_get_leave_balances. GET /business/{businessId}/report/leavebalances.

Input parameters:

- `as_at_date` (string): Balances as at this date (yyyy-mm-dd); default today.
- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `leave_category_id` (integer): Only this leave category.
- `location_id` (integer): Only this location.

### `keypay_approve_leave_request` (~113 tokens)

Approve leave request

WRITE: approves a pending leave request (the employee is notified and the leave is applied to their pay). Check the request first with keypay_get_leave_request. Cannot be undone through this server. POST /business/{businessId}/employee/{employeeId}/leaverequest/{leaveRequestId}/approve.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `employee_id` (integer, required): Employee id.
- `leave_request_id` (integer, required): Leave request id.

### `keypay_decline_leave_request` (~113 tokens)

Decline leave request

WRITE: declines a leave request, with an optional reason the employee sees. Check the request first with keypay_get_leave_request. POST /business/{businessId}/employee/{employeeId}/leaverequest/{leaveRequestId}/decline.

Input parameters:

- `business_id` (integer, required): Business id (from keypay_list_businesses).
- `employee_id` (integer, required): Employee id.
- `leave_request_id` (integer, required): Leave request id.
- `reason` (string): Reason shown to the employee.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-keypay/keypay#diagnostics

## Score history

- 2026-10-25: 62
- 2026-10-24: 62
- 2026-10-23: 61
- 2026-10-22: 61
- 2026-10-21: 61

## Common questions

### What is the Employment Hero Payroll MCP by usefulapi server?

Employment Hero Payroll MCP by usefulapi is listed in the public MCP registry as io.usefulapi/keypay. Read Employment Hero Payroll pay runs, payslips, timesheets and leave; approve or decline leave. This page covers its hosted endpoint (https://keypay.usefulapi.io/mcp).

### Is the Employment Hero Payroll MCP by usefulapi server safe to use?

Employment Hero Payroll MCP by usefulapi scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Employment Hero Payroll MCP by usefulapi server expose?

Employment Hero Payroll MCP by usefulapi exposes 26 tools: keypay_get_user, keypay_list_businesses, keypay_get_business, keypay_list_employees, keypay_get_employee, and 21 more. Their descriptions and schemas cost roughly 3,796 tokens of context every time the server is loaded.

### Does the Employment Hero Payroll MCP by usefulapi server require authentication?

Yes. Employment Hero Payroll MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Employment Hero Payroll MCP by usefulapi server still maintained?

Employment Hero Payroll MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://keypay.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/keypay/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-keypay/keypay.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-keypay/keypay.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-keypay/keypay