Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

intelliHR MCP by usefulapi

REMOTE · INTELLIHR.USEFULAPI.IO

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

60 Trust /100

Last scanned (5 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 25 Oct 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability77
  • 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 3011 tokens (~136/item across 22 items; 22 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 Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 23 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
Changelog

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 +1
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.1.0 → 1.1.3 functional
  • 24 Oct 26 59

    First indexed and scored.

Diagnostics

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://intellihr.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 intellihr.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://intellihr.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://intellihr.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://intellihr.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://intellihr.usefulapi.io/mcp
Authorisation server https://intellihr.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://intellihr.usefulapi.io/mcp Redirected 302 https://usefulapi.io/intellihr/
http (plaintext) http://intellihr.usefulapi.io/mcp Inconclusive 302 http://intellihr.usefulapi.io/mcp
MCP tools · 22 exposed · ~2,757 tokens

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 →

Tool Tokens
intellihr_create_extended_leave ~181

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.

NameTypeReqDescription
end_datestringyesExpected end date, yyyy-mm-dd.
ftestring–FTE during the leave, e.g. 0.6.
job_idstringyesThe job the leave belongs to.
leave_type_idstring–Extended leave type id.
leave_type_namestring–Extended leave type name (used when no id is given).
start_datestringyes–

No output schema declared.

No examples provided.

intellihr_create_person ~186

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.

NameTypeReqDescription
date_of_birthstring–yyyy-mm-dd.
emailstring–Primary email address.
email_is_personalboolean–true if the email is personal rather than a work address (default false).
employee_numberstring––
first_namestring––
genderstring––
last_namestringyes–
middle_namestring––
phonestring–Primary phone number.
preferred_namestring––
titlestring–For example Mr, Ms, Dr.

No output schema declared.

No examples provided.

intellihr_get_job ~50

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

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

intellihr_get_job_timeline ~46

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

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

intellihr_get_person ~71

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}.

NameTypeReqDescription
person_idstringyes–

No output schema declared.

No examples provided.

intellihr_list_business_entities ~71

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

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_list_business_units ~105

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

NameTypeReqDescription
identifierstring–The customer identifier of the unit.
limitinteger–Results per page, 1-100 (default 25).
namestring–Part of the business unit name.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_list_custom_field_definitions ~89

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

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_list_jobs ~349

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.

NameTypeReqDescription
emailstring–The holder's primary email.
employee_numberstring–The holder's employee number.
employment_condition_idstring––
ended_within_daysinteger–Jobs that ended in the last N days (including today).
ending_within_daysinteger–Jobs with an end date in the next N days (including today).
job_idstring–One UUID, or several separated by commas.
job_namestring–The job (position title) name.
limitinteger–Results per page, 1-100 (default 25).
newest_firstboolean–Sort by creation date, newest first.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
person_idstring–Person id(s), comma separated: the jobs of those people.
person_namestring–The holder's name.
primary_onlyboolean–true = only primary jobs, false = only non-primary jobs.
statusstring––
updated_within_daysinteger––
work_typestring–Work type name, e.g. Fixed Contract.

No output schema declared.

No examples provided.

intellihr_list_locations ~79

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

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_list_pay_grades ~135

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

NameTypeReqDescription
as_atstring–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.
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_list_people ~261

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.

NameTypeReqDescription
emailstring–Exact primary email address.
employee_numberstring–Exact employee number.
job_idstring–Current job id(s), comma separated: the people who hold them.
limitinteger–Results per page, 1-100 (default 25).
namestring–Match any part of a person's name (case-insensitive, any name order).
newest_firstboolean–Sort by creation date, newest first (default: API order).
on_extended_leaveboolean–true = only people on extended leave, false = only people not on extended leave.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
updated_within_daysinteger–Only people updated within this many days.

No output schema declared.

No examples provided.

intellihr_list_person_documents ~100

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.

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
person_idstringyes–

No output schema declared.

No examples provided.

intellihr_list_person_skills ~58

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.

NameTypeReqDescription
person_idstringyes–

No output schema declared.

No examples provided.

intellihr_list_person_tasks ~126

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.

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
person_idstringyes–
tabstring–Which tab of tasks (default DUE).

No output schema declared.

No examples provided.

intellihr_list_position_titles ~91

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

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
namestring–Part of the position title.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_list_qualifications ~120

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

NameTypeReqDescription
employee_numberstring––
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
person_idstring–Person id(s), comma separated.
qualification_library_item_idstring––

No output schema declared.

No examples provided.

intellihr_list_reference_data ~139

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.

NameTypeReqDescription
kindstringyes–
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_list_skills ~112

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

NameTypeReqDescription
business_criticalboolean–true = only business-critical skills.
discipline_idstring–Only skills in this skill discipline (see list_reference_data kind skill_disciplines).
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_list_trainings ~149

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

NameTypeReqDescription
emailstring–The person's primary email.
employee_numberstring––
limitinteger–Results per page, 1-100 (default 25).
namestring–Training name.
newest_firstboolean–Sort by creation date, newest first.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
provider_namestring––
type_namestring––

No output schema declared.

No examples provided.

intellihr_list_users ~83

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

NameTypeReqDescription
limitinteger–Results per page, 1-100 (default 25).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.

No output schema declared.

No examples provided.

intellihr_update_person ~156

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}.

NameTypeReqDescription
date_of_birthstring–yyyy-mm-dd.
emergency_contactobject–Emergency contact details to set.
employee_numberstring––
first_namestring––
genderstring––
last_namestring––
middle_namestring––
person_idstringyes–
preferred_namestring––
titlestring–For example Mr, Ms, Dr.

No output schema declared.

No examples provided.

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.

remote · intellihr.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-intellihr 'https://intellihr.usefulapi.io/mcp'
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.