# intelliHR MCP by usefulapi (remote · intellihr.usefulapi.io)

Read intelliHR people, jobs, leave, skills and training; create and update people records.

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

## Components

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

## Channel facts

- Endpoint: `https://intellihr.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.1.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**: 77/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 3011 tokens (~136/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "intellihr_list_pay_grades" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 23 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 intelliHR MCP by usefulapi server?

intelliHR MCP by usefulapi is a hosted endpoint at https://intellihr.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-intellihr 'https://intellihr.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-intellihr": {
      "type": "http",
      "url": "https://intellihr.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 60, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.1.0 → 1.1.3

### 2026-10-24 (score 59)

First indexed and scored.

## MCP tools (22)

### `intellihr_list_people` (~261 tokens)

List people

List the people (employees) in intelliHR as at today: name, employee number, email, phone, addresses, emergency contact, employment status, their jobs (summary) and custom fields. Filter by name (matches any part of the name), email, employee number, job id, recently updated, or who is on extended leave. Health information is never returned. GET /people.

Input parameters:

- `email` (string): Exact primary email address.
- `employee_number` (string): Exact employee number.
- `job_id` (string): Current job id(s), comma separated: the people who hold them.
- `limit` (integer): Results per page, 1-100 (default 25).
- `name` (string): Match any part of a person's name (case-insensitive, any name order).
- `newest_first` (boolean): Sort by creation date, newest first (default: API order).
- `on_extended_leave` (boolean): true = only people on extended leave, false = only people not on extended leave.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `updated_within_days` (integer): Only people updated within this many days.

### `intellihr_get_person` (~71 tokens)

Get person

One person's full record by id: names, date of birth, gender, employee number, contact details, addresses, emergency contact, employment status, jobs, work rights, user account and custom fields. Health information is never returned. GET /people/{id}.

Input parameters:

- `person_id` (string, required)

### `intellihr_list_person_documents` (~100 tokens)

List a person's documents

The documents stored on a person's record (file name, type, size, upload status and a download link). Contents are not read. GET /people/{personId}/documents.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `person_id` (string, required)

### `intellihr_list_person_skills` (~58 tokens)

List a person's skills

The skills assigned to a person (with their level and review details as intelliHR returns them). The whole list comes back at once. GET /people/{personId}/skills.

Input parameters:

- `person_id` (string, required)

### `intellihr_list_person_tasks` (~126 tokens)

List a person's tasks

Tasks (forms, reviews, check-ins, onboarding steps) for a person, by tab: DUE (default), ABOUT_ME, ABOUT_OTHERS, DONE or IGNORED. GET /people/{personId}/tasks.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `person_id` (string, required)
- `tab` (string): Which tab of tasks (default DUE).

### `intellihr_list_jobs` (~349 tokens)

List jobs

List jobs (roles people hold, past, current and future) as at today: person, position title, location, business unit and entity, supervisor, work type, FTE, remuneration schedule, start/end dates and status. Filter by person, job title, status (Current Job, Future Job, Ending Job, Past Job), work type, primary job, or upcoming/recent end dates. GET /jobs.

Input parameters:

- `email` (string): The holder's primary email.
- `employee_number` (string): The holder's employee number.
- `employment_condition_id` (string)
- `ended_within_days` (integer): Jobs that ended in the last N days (including today).
- `ending_within_days` (integer): Jobs with an end date in the next N days (including today).
- `job_id` (string): One UUID, or several separated by commas.
- `job_name` (string): The job (position title) name.
- `limit` (integer): Results per page, 1-100 (default 25).
- `newest_first` (boolean): Sort by creation date, newest first.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `person_id` (string): Person id(s), comma separated: the jobs of those people.
- `person_name` (string): The holder's name.
- `primary_only` (boolean): true = only primary jobs, false = only non-primary jobs.
- `status` (string)
- `updated_within_days` (integer)
- `work_type` (string): Work type name, e.g. Fixed Contract.

### `intellihr_get_job` (~50 tokens)

Get job

One job by id with its person, position title, location, business unit, supervisor, pay grade, remuneration and dates. GET /jobs/{id}.

Input parameters:

- `job_id` (string, required)

### `intellihr_get_job_timeline` (~46 tokens)

Get job timeline

The upcoming changes and current information about a job (scheduled changes, end date). GET /jobs/{jobId}/timeline.

Input parameters:

- `job_id` (string, required)

### `intellihr_list_locations` (~79 tokens)

List locations

The organisation's locations (sites) with parent location, code, address, enabled flag and representatives. GET /locations.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_business_units` (~105 tokens)

List business units

The organisation's business units (departments, teams). Filter by name or identifier. GET /business-units.

Input parameters:

- `identifier` (string): The customer identifier of the unit.
- `limit` (integer): Results per page, 1-100 (default 25).
- `name` (string): Part of the business unit name.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_business_entities` (~71 tokens)

List business entities

The organisation's business entities (legal employers). GET /business-entities.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_position_titles` (~91 tokens)

List position titles

The position titles (job names) defined in intelliHR. Filter by name. GET /position-titles.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `name` (string): Part of the position title.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_pay_grades` (~135 tokens)

List pay grades

The pay grades and their rates, optionally as at a date. GET /pay-grades.

Input parameters:

- `as_at` (string): Show the pay grades as at this point in time: an RFC3339 datetime (2026-10-01T09:00:00+10:00) or a date yyyy-mm-dd (= 00:00 UTC that day). Default now.
- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_users` (~83 tokens)

List users

The user accounts that can sign in to intelliHR: username, enabled flag, permission groups and the linked person. GET /users.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_custom_field_definitions` (~89 tokens)

List custom field definitions

The custom fields defined in intelliHR (what each field on a person, job or location means and its type). GET /custom-field-definitions.

Input parameters:

- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_reference_data` (~139 tokens)

List reference data

Look up one of intelliHR's reference lists: employment_conditions, work_classes, work_types, work_rights, recruitment_sources, extended_leave_types, job_change_reasons, skill_disciplines, training_types, training_providers, qualification_types, qualification_library_items, onboarding_templates, permission_groups or representative_types. Use it to find the ids and names other tools need.

Input parameters:

- `kind` (string, required)
- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_skills` (~112 tokens)

List skills

The skills catalogue, optionally only business-critical skills or one discipline. GET /skills.

Input parameters:

- `business_critical` (boolean): true = only business-critical skills.
- `discipline_id` (string): Only skills in this skill discipline (see list_reference_data kind skill_disciplines).
- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.

### `intellihr_list_qualifications` (~120 tokens)

List qualifications

Qualification records held by people (licences, certificates) with status and dates. Filter by person, employee number or library item. GET /qualifications.

Input parameters:

- `employee_number` (string)
- `limit` (integer): Results per page, 1-100 (default 25).
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `person_id` (string): Person id(s), comma separated.
- `qualification_library_item_id` (string)

### `intellihr_list_trainings` (~149 tokens)

List trainings

Training records completed or booked by people, with provider, type and dates. Filter by training name, provider, type, employee number or email. GET /trainings.

Input parameters:

- `email` (string): The person's primary email.
- `employee_number` (string)
- `limit` (integer): Results per page, 1-100 (default 25).
- `name` (string): Training name.
- `newest_first` (boolean): Sort by creation date, newest first.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `provider_name` (string)
- `type_name` (string)

### `intellihr_create_person` (~186 tokens)

Create person

WRITE: create a new person record in intelliHR (last name required). It creates the person only: no job, no user account and no welcome email is sent. A job is added separately in intelliHR. Check with list_people first to avoid duplicates. POST /people.

Input parameters:

- `date_of_birth` (string): yyyy-mm-dd.
- `email` (string): Primary email address.
- `email_is_personal` (boolean): true if the email is personal rather than a work address (default false).
- `employee_number` (string)
- `first_name` (string)
- `gender` (string)
- `last_name` (string, required)
- `middle_name` (string)
- `phone` (string): Primary phone number.
- `preferred_name` (string)
- `title` (string): For example Mr, Ms, Dr.

### `intellihr_update_person` (~156 tokens)

Update person

WRITE: change fields on an existing person (only the fields you pass change): names, date of birth, gender, employee number, title and emergency contact. Contact details, addresses and jobs are not changed by this tool. PATCH /people/{id}.

Input parameters:

- `date_of_birth` (string): yyyy-mm-dd.
- `emergency_contact` (object): Emergency contact details to set.
- `employee_number` (string)
- `first_name` (string)
- `gender` (string)
- `last_name` (string)
- `middle_name` (string)
- `person_id` (string, required)
- `preferred_name` (string)
- `title` (string): For example Mr, Ms, Dr.

### `intellihr_create_extended_leave` (~181 tokens)

Create extended leave

WRITE: record extended leave (parental, long service, unpaid, etc.) on an existing job. It changes the person's employment record and can trigger intelliHR workflows. The leave is created with the end date you give as expected; finalise it in intelliHR when the person returns. Find leave types with list_reference_data kind extended_leave_types. POST /extended-leave.

Input parameters:

- `end_date` (string, required): Expected end date, yyyy-mm-dd.
- `fte` (string): FTE during the leave, e.g. 0.6.
- `job_id` (string, required): The job the leave belongs to.
- `leave_type_id` (string): Extended leave type id.
- `leave_type_name` (string): Extended leave type name (used when no id is given).
- `start_date` (string, required)

## Diagnostics

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

## Score history

- 2026-10-25: 60
- 2026-10-24: 59

## Common questions

### What is the intelliHR MCP by usefulapi server?

intelliHR MCP by usefulapi is listed in the public MCP registry as io.usefulapi/intellihr. Read intelliHR people, jobs, leave, skills and training; create and update people records. This page covers its hosted endpoint (https://intellihr.usefulapi.io/mcp).

### Is the intelliHR MCP by usefulapi server safe to use?

intelliHR MCP by usefulapi scores 60 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 intelliHR MCP by usefulapi server expose?

intelliHR MCP by usefulapi exposes 22 tools: intellihr_list_people, intellihr_get_person, intellihr_list_person_documents, intellihr_list_person_skills, intellihr_list_person_tasks, and 17 more. Their descriptions and schemas cost roughly 2,757 tokens of context every time the server is loaded.

### Does the intelliHR MCP by usefulapi server require authentication?

Yes. intelliHR 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 intelliHR MCP by usefulapi server still maintained?

intelliHR 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://intellihr.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/intellihr/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-intellihr/intellihr.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-intellihr/intellihr.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-intellihr/intellihr