Talenox MCP by usefulapi
REMOTE · TALENOX.USEFULAPI.IO
Review employees, payroll and leave, and approve or reject Talenox leave applications.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- New prompt “approve_a_selected_leave_application” functional
- New prompt “check_an_employee_leave_balance” functional
- New prompt “review_leave_for_a_date_range” functional
- New prompt “review_payroll_run_status” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.2 → 1.1.0 functional
- 30 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 5 Nov 2026 · Probed https://talenox.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 talenox.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://talenox.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/talenox/ |
| http (plaintext) | http://talenox.usefulapi.io/mcp | Inconclusive | 302 | http://talenox.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 →
talenox_approve_leave_application Approve a leave application ~67
WRITE: approve a leave application as the token's user. The employee's balance and payroll are affected and Talenox may notify them. Read the application first (talenox_get_leave_application) and confirm with the user.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The leave application id. |
No output schema declared.
No examples provided.
talenox_get_branch Get a branch ~31
Get one branch (name, address, head, employee ids).
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The branch id. |
No output schema declared.
No examples provided.
talenox_get_company_settings Get company settings ~30
Get the company's API-related settings (for example whether an employee may belong to several cost centres).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
talenox_get_employee Get an employee ~100
Get one employee's full record: personal details, jobs, cost centres, custom fields. National id, passport, bank account and health fields are left out unless include_sensitive is true.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The employee's Talenox id (the numeric `id` from talenox_list_employees). |
| include_sensitive | boolean | – | Include national id (ssn), passport, bank account, religion/race and vaccination fields. Default false. |
No output schema declared.
No examples provided.
talenox_get_holiday_policy Get a holiday policy ~61
Get one holiday policy with its calendar events between two dates.
| Name | Type | Req | Description |
|---|---|---|---|
| end_at | string | yes | End date, yyyy-mm-dd. |
| id | – | yes | The holiday policy id. |
| start_at | string | yes | Start date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
talenox_get_job Get a job record ~60
Get one job record of an employee (title, department, start/end date, pay amount and rate, currency). Job ids are in the employee's `jobs` list.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The job id (from an employee's jobs list). |
No output schema declared.
No examples provided.
talenox_get_leave_application Get a leave application ~42
Get one leave application (employee, dates, half-day markers, amount, status, approvers, attachments).
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The leave application id. |
No output schema declared.
No examples provided.
talenox_get_leave_balance Get leave balances ~96
Get an employee's leave balance on a date, for every leave type or for one (leave_type_id). A type that does not apply to the employee comes back with an error text instead of a balance.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | – | yes | The employee's Talenox id. |
| leave_type_id | – | – | Only this leave type. |
| query_date | string | yes | The date to compute the balance for, yyyy-mm-dd. |
No output schema declared.
No examples provided.
talenox_get_leave_entitlement_period Get leave entitlement periods ~72
Get the entitlement periods (start and end dates) of one leave type for an employee around a date.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | – | yes | The employee's Talenox id. |
| leave_type_id | – | yes | The leave type id. |
| query_date | string | yes | Reference date, yyyy-mm-dd. |
No output schema declared.
No examples provided.
talenox_get_leave_type Get a leave type ~37
Get one leave type (name, half-day allowed, quantity type, policy dates).
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The leave type id. |
No output schema declared.
No examples provided.
talenox_get_off_in_lieu_balance Get off in lieu balances ~88
Get an employee's off-in-lieu balance on a date, for every off in lieu or for one (off_in_lieu_id).
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | – | yes | The employee's Talenox id. |
| off_in_lieu_id | – | – | Only this off in lieu. |
| query_date | string | yes | The date to compute the balance for, yyyy-mm-dd. |
No output schema declared.
No examples provided.
talenox_get_payroll_payment Get a payroll payment ~48
Get one payroll payment run (period, status, bank file and cheque export state).
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The payment id (payment_id from talenox_list_payroll_payments). |
No output schema declared.
No examples provided.
talenox_get_payslips_data Get payslip data ~105
Get the payslip figures (gross, net, deductions, year-to-date) of a month as data, for all employees or the listed ones. Read only: nothing is created, processed or published. Contains salary data.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_ids | array | – | Only these employees (default: all). |
| month | string | yes | Month name in English, e.g. September. |
| year | integer | yes | Year, e.g. 2026. |
No output schema declared.
No examples provided.
talenox_get_role Get an employee role ~23
Get one employee role.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The role id. |
No output schema declared.
No examples provided.
talenox_get_working_day Get a working-day schedule ~28
Get one working-day schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The working-day schedule id. |
No output schema declared.
No examples provided.
talenox_list_branches List branches ~22
List the company's branches with their head and employee ids.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
talenox_list_company_holidays List company holidays ~61
List the company's holidays (from its default holiday policy) for a year.
| Name | Type | Req | Description |
|---|---|---|---|
| show_inactive | boolean | – | Include inactive holidays (default false). |
| year | integer | – | Calendar year (default: the current year at Talenox). |
No output schema declared.
No examples provided.
talenox_list_cost_centres List cost centres ~22
List the company's cost centres with their employee ids.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
talenox_list_custom_pay_items List custom pay items ~36
List the company's pay item definitions (name, category such as Adhoc or Recurring, taxable, gross/net setting).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
talenox_list_employees List employees ~181
List the company's employees as a short summary (id, employee_id, names, email, hired/resign dates, current job). Talenox returns every employee in one reply, so use search to narrow and limit/offset to page here. Use talenox_get_employee for the full record. Sensitive fields (national id, passport, bank account) are never included.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Employees to return, 1-200 (default 50). |
| offset | integer | – | Employees to skip (default 0); use next_offset from the previous reply. |
| search | string | – | Words that must all appear in the name, employee id, nickname or email (case-insensitive). |
| status | string | – | active = no resign date or one in the future; resigned = a resign date in the past. Default all. |
No output schema declared.
No examples provided.
talenox_list_holiday_policies List holiday policies ~88
List the company's public-holiday policies (country, state, default flag). Paged: pass next_last_seen_id as last_seen_id.
| Name | Type | Req | Description |
|---|---|---|---|
| last_seen_id | integer | – | Pagination: return results after this id (next_last_seen_id of the previous reply). |
| limit | integer | – | Results per page, 1-50 (Talenox default 20). |
No output schema declared.
No examples provided.
talenox_list_leave_applications List leave applications ~210
List leave applications that overlap a date range, optionally by status, employee, approver or leave type. Paged: pass next_last_seen_id as last_seen_id. Uses Talenox's leave API (beta).
| Name | Type | Req | Description |
|---|---|---|---|
| approver_id | – | – | Only applications this employee approves. |
| category | string | – | type = leave type, oil = off in lieu. |
| category_id | – | – | Leave type id (category type) or off in lieu id (category oil). |
| employee_id | – | – | Only this employee's applications. |
| last_seen_id | integer | – | Pagination: return results after this id (next_last_seen_id of the previous reply). |
| limit | integer | – | Results per page, 1-50 (Talenox default 20). |
| overlap_from | string | yes | Start of the date range, yyyy-mm-dd. |
| overlap_to | string | yes | End of the date range, yyyy-mm-dd. |
| status | string | – | Only applications with this status. |
No output schema declared.
No examples provided.
talenox_list_leave_types List leave types ~104
List the leave types of the company, or those an employee may apply for (employee_id). Paged: pass next_last_seen_id as last_seen_id.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | – | – | Only the leave types open to this employee. |
| last_seen_id | integer | – | Pagination: return results after this id (next_last_seen_id of the previous reply). |
| limit | integer | – | Results per page, 1-50 (Talenox default 20). |
No output schema declared.
No examples provided.
talenox_list_off_in_lieus List off in lieu types ~82
List the off-in-lieu types of the company, or of one employee. Paged: pass next_last_seen_id as last_seen_id.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | – | – | Only this employee's off in lieus. |
| last_seen_id | integer | – | Pagination: return results after this id (next_last_seen_id of the previous reply). |
No output schema declared.
No examples provided.
talenox_list_payroll_payments List payroll payments ~84
List the payroll payment runs of a month (period, pay group, status Draft or Processed, bank file state).
| Name | Type | Req | Description |
|---|---|---|---|
| created_by_webhook | boolean | – | Only payments created by a webhook. |
| month | string | yes | Month name in English, e.g. September. |
| year | integer | yes | Year, e.g. 2026. |
No output schema declared.
No examples provided.
talenox_list_roles List employee roles ~19
List the company's employee roles (access roles).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
talenox_list_working_days List working-day schedules ~43
List the working-day schedules (weekly pattern Sunday to Saturday: full_day, first_half, second_half, not_working) and who is on each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
talenox_reject_leave_application Reject a leave application ~59
WRITE: reject a leave application as the token's user. Talenox may notify the employee. Read the application first (talenox_get_leave_application) and confirm with the user.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The leave application id. |
No output schema declared.
No examples provided.
How do I install the Talenox MCP by usefulapi server?
Talenox MCP by usefulapi is a hosted endpoint at https://talenox.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 · talenox.usefulapi.io
claude mcp add --transport http io-usefulapi-talenox 'https://talenox.usefulapi.io/mcp'
What is the Talenox MCP by usefulapi server?
Talenox MCP by usefulapi is listed in the public MCP registry as io.usefulapi/talenox. Review employees, payroll and leave, and approve or reject Talenox leave applications. This page covers its hosted endpoint (https://talenox.usefulapi.io/mcp).
Is the Talenox MCP by usefulapi server safe to use?
Talenox MCP by usefulapi scores 18 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 Talenox MCP by usefulapi server expose?
Talenox MCP by usefulapi exposes 28 tools: talenox_list_employees, talenox_get_employee, talenox_get_job, talenox_list_branches, talenox_get_branch, and 23 more. Their descriptions and schemas cost roughly 1,899 tokens of context every time the server is loaded.
Does the Talenox MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Talenox MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Talenox MCP by usefulapi server still maintained?
Talenox MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Talenox MCP by usefulapi server?
VerifyMCP ran 4 checks on Talenox MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Talenox MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.