# SmartHR MCP by usefulapi (remote · smarthr.usefulapi.io)

MCP server for SmartHR — employees, departments, dependents and employee invitations.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Endpoint: `https://smarthr.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.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-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - 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.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

### How do I install the SmartHR MCP by usefulapi server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-smarthr": {
      "type": "http",
      "url": "https://smarthr.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-11-02 (score 18, −47)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 65, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-31 (score 64)

First indexed and scored.

## MCP tools (23)

### `smarthr_list_employees` (~459 tokens)

List employees (従業員) of the SmartHR tenant, with filters: free-text name/department/position search, status (employed, absent, retired), employee number, employment type, department, position, hire and resignation date ranges. Returns a compact record per employee; use `fields` for more. Sensitive data (bank accounts, insurance numbers, residence cards, salary, ID images) is never returned.

Input parameters:

- `department_id` (string): Department id(s), comma separated (from smarthr_list_departments).
- `emp_code` (string): Exact employee number.
- `emp_status` (string): Only employees with this status.
- `employment_type_id` (string): Employment type id(s), comma separated (from smarthr_list_employment_types).
- `entered_at_from` (string): Hired on or after this day (yyyy-mm-dd).
- `entered_at_to` (string): Hired on or before this day (yyyy-mm-dd).
- `fields` (array): Which employee fields to return (default: names, status, email, departments, positions, grade, job category, dates). Add address, tel_number, birth_at, custom_fields, contract_* and so on when needed…
- `id` (string): Employee id(s), comma separated.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).
- `position_id` (string): Position id(s), comma separated (from smarthr_list_positions).
- `q` (string): Free-text search over name, business name, department name and position name.
- `resigned_at_from` (string): Resigned on or after this day (yyyy-mm-dd).
- `resigned_at_to` (string): Resigned on or before this day (yyyy-mm-dd).
- `sort` (string): Sort order: property names, several separated by commas, a leading "-" means descending, e.g. "-updated_at".
- `user_id` (string): User id(s), comma separated.

### `smarthr_get_employee` (~137 tokens)

Get one employee (従業員) by id. Returns a compact record; use `fields` for more (address, phone, birth date, custom fields, contract dates). Sensitive data is never returned.

Input parameters:

- `fields` (array): Which employee fields to return (default: names, status, email, departments, positions, grade, job category, dates). Add address, tel_number, birth_at, custom_fields, contract_* and so on when needed…
- `id` (string, required): Employee id (from smarthr_list_employees).

### `smarthr_list_dependents` (~112 tokens)

List the dependents (家族情報) registered for one employee: name, relation, birth date, living arrangement and support status. Pension numbers, income and documents are not returned.

Input parameters:

- `employee_id` (string, required): Employee id (from smarthr_list_employees).
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_maternity_childcare_leaves` (~117 tokens)

List the maternity and childcare leave records (産休育休) of one employee: expected birth, leave start/end and scheduled return dates. Bank, insurance and memo data are not returned.

Input parameters:

- `employee_id` (string, required): Employee id (from smarthr_list_employees).
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_departments` (~114 tokens)

List departments (部署) with their hierarchy (parent, children), code and company.

Input parameters:

- `code` (string): Exact department code.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).
- `sort` (string): Sort order: property names, several separated by commas, a leading "-" means descending, e.g. "-updated_at".

### `smarthr_get_department` (~43 tokens)

Get one department (部署) by id, with its parent and children.

Input parameters:

- `id` (string, required): Department id (from smarthr_list_departments).

### `smarthr_list_positions` (~101 tokens)

List positions / job titles (役職) with their rank and code.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).
- `sort` (string): Sort order: property names, several separated by commas, a leading "-" means descending, e.g. "-updated_at".

### `smarthr_list_employment_types` (~90 tokens)

List employment types (雇用形態), e.g. full-timer, part-timer, contract worker, with their ids for filtering and writes.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_grades` (~67 tokens)

List grades (等級) with their rank.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_job_categories` (~64 tokens)

List job categories (職種).

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_companies` (~78 tokens)

List the companies (会社) of the tenant: name, code, corporate number, address, phone.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_business_establishments` (~95 tokens)

List business establishments (事業所): name, social insurance and labor insurance registration data, company.

Input parameters:

- `embed` (string): Embed the related object instead of only its id.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_employee_custom_fields` (~118 tokens)

List the definitions of the tenant's custom employee fields (カスタム従業員項目): name, type and, for dropdowns, the choices. Use them to read the values in custom_fields.

Input parameters:

- `embed` (string): Embed the custom field group instead of only its id.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_dependent_relations` (~89 tokens)

List the relation types for dependents (続柄: spouse, child, parent...) with their ids, needed by smarthr_create_dependent.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_users` (~148 tokens)

List SmartHR users (login accounts): email, administrator flag, role, linked employee, and the invitation status (created, opened, accepted, answered). Use it to find the administrator id for smarthr_invite_employee.

Input parameters:

- `embed` (string): Embed the related object instead of only its id.
- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).
- `sort` (string): Sort order: property names, several separated by commas, a leading "-" means descending, e.g. "-updated_at".

### `smarthr_list_employee_input_forms` (~80 tokens)

List the employee information collection forms (従業員情報収集フォーム) that an invitation can use.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_list_webhooks` (~90 tokens)

List the configured webhooks (target URL, which employee and dependent events notify). Read-only; secret tokens and the query string of the target URL are never shown.

Input parameters:

- `page` (integer): Page number, 1-based (default 1). Use next_page from the previous reply.
- `per_page` (integer): Results per page, 1-100 (default 50).

### `smarthr_create_employee` (~454 tokens)

WRITE: Register a new employee (従業員) in SmartHR. Nothing is sent to the employee; to invite them to fill in their own data use smarthr_invite_employee afterwards. Only the fields you give are set. The tenant plan may cap the number of employees (error plan_limit_exceeded). Returns the created employee as a compact record.

Input parameters:

- `address` (object): Address; the city is required by SmartHR.
- `birth_at` (string): Date of birth, yyyy-mm-dd.
- `biz_establishment_id` (string): Business establishment id (from smarthr_list_business_establishments).
- `business_first_name` (string): Business name: given name.
- `business_last_name` (string): Business name: family name.
- `department_ids` (array): Department ids (from smarthr_list_departments); replaces the current departments.
- `email` (string): Work or contact email address.
- `emp_code` (string): Employee number (社員番号).
- `emp_status` (string): Employment status: employed, absent (on leave) or retired.
- `employment_type_id` (string): Employment type id (from smarthr_list_employment_types).
- `entered_at` (string): Hire date, yyyy-mm-dd.
- `first_name` (string, required): Given name (required).
- `first_name_yomi` (string): Given name in katakana.
- `gender` (string): Legal gender (戸籍上の性別): male or female.
- `grade` (string): Grade name (等級).
- `job_category` (string): Job category name (職種).
- `last_name` (string, required): Family name (required).
- `last_name_yomi` (string): Family name in katakana.
- `occupation` (string): Job description (業務内容).
- `positions` (array): Position (job title) NAMES, e.g. ["部長"]; a name that does not exist yet may be created by SmartHR.
- `resigned_at` (string): Resignation date, yyyy-mm-dd.
- `resigned_reason` (string): Reason for leaving.
- `tel_number` (string): Phone number.

### `smarthr_update_employee` (~490 tokens)

WRITE: Change fields of one existing employee (partial update: only the fields you give change; others stay). Typical uses: set the status to absent or retired with the resignation date, correct a name, email or phone, move the employee to other departments (department_ids replaces the current list), change positions. SmartHR does not allow clearing a name that is already filled in. Returns the updated employee as a compact record.

Input parameters:

- `address` (object): Address; the city is required by SmartHR.
- `birth_at` (string): Date of birth, yyyy-mm-dd.
- `biz_establishment_id` (string): Business establishment id (from smarthr_list_business_establishments).
- `business_first_name` (string): Business name: given name.
- `business_last_name` (string): Business name: family name.
- `department_ids` (array): Department ids (from smarthr_list_departments); replaces the current departments.
- `email` (string): Work or contact email address.
- `emp_code` (string): Employee number (社員番号).
- `emp_status` (string): Employment status: employed, absent (on leave) or retired.
- `employment_type_id` (string): Employment type id (from smarthr_list_employment_types).
- `entered_at` (string): Hire date, yyyy-mm-dd.
- `first_name` (string): Given name (戸籍上の名).
- `first_name_yomi` (string): Given name in katakana.
- `gender` (string): Legal gender (戸籍上の性別): male or female.
- `grade` (string): Grade name (等級).
- `id` (string, required): Employee id (from smarthr_list_employees).
- `job_category` (string): Job category name (職種).
- `last_name` (string): Family name (戸籍上の姓).
- `last_name_yomi` (string): Family name in katakana.
- `occupation` (string): Job description (業務内容).
- `positions` (array): Position (job title) NAMES, e.g. ["部長"]; a name that does not exist yet may be created by SmartHR.
- `resigned_at` (string): Resignation date, yyyy-mm-dd.
- `resigned_reason` (string): Reason for leaving.
- `tel_number` (string): Phone number.

### `smarthr_create_department` (~117 tokens)

WRITE: Create a department (部署). Give the parent department id to nest it. Returns the created department.

Input parameters:

- `code` (string): Department code.
- `company_id` (string): Company id (from smarthr_list_companies); needed when the tenant has several companies.
- `name` (string, required): Department name (no slash).
- `parent_id` (string): Parent department id (from smarthr_list_departments); omit for a top-level department.
- `position` (integer): Display order among siblings.

### `smarthr_update_department` (~104 tokens)

WRITE: Rename or move one department (partial update: only the fields you give change). Returns the updated department.

Input parameters:

- `code` (string): New code.
- `id` (string, required): Department id (from smarthr_list_departments).
- `name` (string): New name (no slash). Omit to keep the current name.
- `parent_id` (string): New parent department id.
- `position` (integer): New display order among siblings.

### `smarthr_create_dependent` (~296 tokens)

WRITE: Register a dependent (家族情報) for an employee. Needs the relation id from smarthr_list_dependent_relations. Returns the created dependent without pension number, income or documents.

Input parameters:

- `address` (object): Address; the city is required by SmartHR.
- `birth_at` (string, required): Date of birth, yyyy-mm-dd.
- `employee_id` (string, required): Employee id (from smarthr_list_employees).
- `first_name` (string, required): Given name.
- `first_name_yomi` (string): Given name in katakana.
- `gender` (string, required): Gender: male or female.
- `is_spouse` (boolean): True for a spouse.
- `job` (string): Occupation.
- `last_name` (string, required): Family name.
- `last_name_yomi` (string): Family name in katakana.
- `live_together_type` (string, required): Living with the employee or separately.
- `relation_id` (string, required): Relation id (from smarthr_list_dependent_relations).
- `social_insurance_support_type` (string, required): Social-insurance dependent status (required: SmartHR would otherwise default it to supported). Use unknown when not decided.
- `tax_law_support_type` (string, required): Tax-law dependent status (required: SmartHR would otherwise default it to supported). Use unknown when not decided.
- `tel_number` (string): Phone number.

### `smarthr_invite_employee` (~174 tokens)

WRITE, SENDS AN EMAIL: Invite an employee to SmartHR. SmartHR emails the address stored on the employee (the employee must have one) an invitation to create their login and, with an input form, to fill in their own data. Asking again re-sends it (and updates the invited address if it changed). An employee who already accepted cannot be invited again. Confirm with the user before calling.

Input parameters:

- `crew_input_form_id` (string): Employee information collection form id (from smarthr_list_employee_input_forms); its mail format is used.
- `id` (string, required): Employee id (from smarthr_list_employees); the employee needs an email address.
- `inviter_user_id` (string, required): User id of the inviting administrator (from smarthr_list_users, an administrator).

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 65
- 2026-10-31: 64

## Common questions

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

SmartHR MCP by usefulapi is listed in the public MCP registry as io.usefulapi/smarthr. MCP server for SmartHR, employees, departments, dependents and employee invitations. This page covers its hosted endpoint (https://smarthr.usefulapi.io/mcp).

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

SmartHR 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 SmartHR MCP by usefulapi server expose?

SmartHR MCP by usefulapi exposes 23 tools: smarthr_list_employees, smarthr_get_employee, smarthr_list_dependents, smarthr_list_maternity_childcare_leaves, smarthr_list_departments, and 18 more. Their descriptions and schemas cost roughly 3,637 tokens of context every time the server is loaded.

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

Its publisher declares no required credentials for SmartHR 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 SmartHR MCP by usefulapi server still maintained?

SmartHR 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 SmartHR MCP by usefulapi server?

VerifyMCP ran 4 checks on SmartHR 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 SmartHR 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.

## Links

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