Employment Hero Payroll MCP by usefulapi
REMOTE · KEYPAY.USEFULAPI.IO
Read Employment Hero Payroll pay runs, payslips, timesheets and leave; approve or decline leave.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 0
- Server version: 1.5.2 → 1.5.3 functional
- Server version: 1.5.0 → 1.5.2 functional
- 24 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 23 Oct 26 0
- Server version: 1.0.1 → 1.1.0 functional
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- 21 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://keypay.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of keypay.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://keypay.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://keypay.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://keypay.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://keypay.usefulapi.io/mcp |
| Authorisation server | https://keypay.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://keypay.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/keypay/ |
| http (plaintext) | http://keypay.usefulapi.io/mcp | Inconclusive | 302 | http://keypay.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
keypay_approve_leave_request Approve leave request ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| employee_id | integer | yes | Employee id. |
| leave_request_id | integer | yes | Leave request id. |
No output schema declared.
No examples provided.
keypay_decline_leave_request Decline leave request ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| employee_id | integer | yes | Employee id. |
| leave_request_id | integer | yes | Leave request id. |
| reason | string | – | Reason shown to the employee. |
No output schema declared.
No examples provided.
keypay_get_business Get business ~62
One business by id: name, legal name, contact, address, ABN/company details, leave year, standard hours, pay cycle. GET /business/{businessId}.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
No output schema declared.
No examples provided.
keypay_get_employee Get employee ~127
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| employee_id | integer | yes | Employee id (from keypay_list_employees). |
No output schema declared.
No examples provided.
keypay_get_leave_balances Get employee leave balances ~97
An employee's leave balances per leave category (accrued amount and unit), optionally as at a date. GET /business/{businessId}/employee/{employeeId}/leavebalances.
| Name | Type | Req | Description |
|---|---|---|---|
| as_at_date | string | – | Balance as at this date (yyyy-mm-dd); default today. |
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| employee_id | integer | yes | Employee id. |
No output schema declared.
No examples provided.
keypay_get_leave_request Get leave request ~94
One leave request: employee, category, dates, hours, status, notes. GET /business/{businessId}/employee/{employeeId}/leaverequest/{leaveRequestId}.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| employee_id | integer | yes | Employee id. |
| leave_request_id | integer | yes | Leave request id (from keypay_list_leave_requests). |
No output schema declared.
No examples provided.
keypay_get_pay_run Get pay run ~83
One pay run by id: pay schedule, period, date paid, whether it is finalised, notation. GET /business/{businessId}/payrun/{payRunId}.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| pay_run_id | integer | yes | Pay run id (from keypay_list_pay_runs). |
No output schema declared.
No examples provided.
keypay_get_pay_run_payslips Get pay slip data of a pay run ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| pay_run_id | integer | yes | Pay run id. |
| show_all_data | boolean | – | Include all pay slip data, not only what is printed on the slip (default false). |
No output schema declared.
No examples provided.
keypay_get_pay_run_summary Get pay run summary ~71
One pay run with its total hours, gross wages and net wages. GET /business/{businessId}/payrun/{payRunId}/summary.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| pay_run_id | integer | yes | Pay run id. |
No output schema declared.
No examples provided.
keypay_get_pay_run_totals Get pay run totals per employee ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| pay_run_id | integer | yes | Pay run id. |
No output schema declared.
No examples provided.
keypay_get_timesheet Get timesheet line ~70
One timesheet line by id. GET /business/{businessId}/timesheet/{timesheetLineId}.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| timesheet_id | integer | yes | Timesheet line id (from keypay_list_timesheets). |
No output schema declared.
No examples provided.
keypay_get_user Get current user ~35
The Employment Hero Payroll user this API key belongs to: id, email, display name and time zone. GET /user.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
keypay_list_businesses List businesses ~189
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
keypay_list_employees List employees ~237
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_leave_categories List leave categories ~200
Leave categories of the business (annual, personal/sick, long service...): id, name, unit type, accrual rule. GET /business/{businessId}/leavecategory (OData).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_leave_requests List leave requests ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_locations List locations ~192
Locations of the business (sites, departments): id, name, parent, fully qualified name, state. GET /business/{businessId}/location (OData).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_pay_categories List pay categories ~202
Pay categories (earnings types) of the business: id, name, rate unit, loadings, super rate, whether leave accrues. GET /business/{businessId}/paycategory (OData).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_pay_run_summaries List pay run summaries ~200
Pay runs with their totals: total hours, gross wages and net wages, plus the usual pay run fields. GET /business/{businessId}/payrun/summary (OData).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_pay_run_warnings List pay run warnings ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| pay_run_id | integer | yes | Pay run id. |
No output schema declared.
No examples provided.
keypay_list_pay_runs List pay runs ~216
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_pay_schedules List pay schedules ~203
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_timesheets List timesheets ~250
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).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_list_work_types List work types ~192
Work types of the business: id, name, pay category, leave category, short code. GET /business/{businessId}/worktype (OData).
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_report_gross_to_net Gross to net report ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | integer | yes | 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). |
No output schema declared.
No examples provided.
keypay_report_leave_balances Leave balances report ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_at_date | string | – | Balances as at this date (yyyy-mm-dd); default today. |
| business_id | integer | yes | Business id (from keypay_list_businesses). |
| leave_category_id | integer | – | Only this leave category. |
| location_id | integer | – | Only this location. |
No output schema declared.
No examples provided.
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.
remote · keypay.usefulapi.io
claude mcp add --transport http io-usefulapi-keypay 'https://keypay.usefulapi.io/mcp'
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.