# Namely MCP by usefulapi (remote · namely.usefulapi.io)

Read Namely employee profiles, groups, teams, jobs and reports; update profiles, post to the feed.

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

## Components

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

## Channel facts

- Endpoint: `https://namely.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.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**: 85/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).
  - Tool/resource definitions use about 1638 tokens (~96/item across 17 items; 17 tools + 0 resources), lean.
  - 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 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 Namely MCP by usefulapi server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-namely": {
      "type": "http",
      "url": "https://namely.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 63, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.2.0 → 1.2.3

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

First indexed and scored.

## MCP tools (17)

### `namely_get_me` (~42 tokens)

Get my profile

Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.

### `namely_list_profiles` (~265 tokens)

List employee profiles

List employee profiles (active, pending and inactive unless filtered) with paging, sorting and filters. Returns {profiles, meta:{count}, linked}. Use format=short for a smaller record (ids, names, email, status, job title); the full record includes every custom field the token may see (compensation, addresses and other sensitive HR data). An empty page means the end. Namely API: GET /profiles (limit 100 requests per minute).

Input parameters:

- `email` (string): Exact company email.
- `first_name` (string): Exact first name.
- `format` (string): short = truncated profile objects (default); full = every field.
- `job_title` (string): Exact job title (the `title` of a job title).
- `last_name` (string): Exact last name.
- `page` (integer): Page number, starting at 1.
- `per_page` (integer): Profiles per page (default 30, max 50).
- `personal_email` (string): Exact personal email.
- `reports_to` (string): Profile id of a manager: only that person's direct reports.
- `sort` (string): Sort order; a leading - reverses it.
- `user_status` (string): Only profiles with this status.

### `namely_get_profile` (~79 tokens)

Get employee profile

Get one employee's full profile by id: personal and job data, manager, groups, teams and the custom fields the token may see (can include compensation and other sensitive HR data). Namely API: GET /profiles/{id}.

Input parameters:

- `id` (string, required): Namely profile id (the `id` of a profile from namely_list_profiles).

### `namely_list_profile_fields` (~50 tokens)

List profile fields

List the fields of the employee profile as configured at this company (standard and custom), with their labels, sections and the valid format of each value. Namely API: GET /profiles/fields.

### `namely_list_groups` (~39 tokens)

List groups

List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.

### `namely_get_group` (~49 tokens)

Get group

Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.

Input parameters:

- `id` (string, required): Group id (from namely_list_groups).

### `namely_list_group_types` (~35 tokens)

List group types

List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.

### `namely_list_teams` (~26 tokens)

List teams

List all teams with their team categories. Namely API: GET /teams.

### `namely_get_team` (~50 tokens)

Get team

Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.

Input parameters:

- `id` (string, required): Team id (from namely_list_teams).

### `namely_list_job_titles` (~31 tokens)

List job titles

List all job titles; each belongs to one job tier. Namely API: GET /job_titles.

### `namely_list_job_tiers` (~33 tokens)

List job tiers

List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.

### `namely_list_events` (~138 tokens)

List feed events

List events of the company home feed (announcements, birthdays, work anniversaries, new arrivals), newest first by default, with limit and after (an event id) for paging. Namely API: GET /events.

Input parameters:

- `after` (string): Event id after which to start (for the next page).
- `limit` (integer): Number of events to return (max 30).
- `order` (string): Order by time; default desc.
- `profile_id` (string): Only events associated with this profile id.
- `type` (string): Event type, e.g. birthday, announcement, recent_arrival, anniversary.

### `namely_list_event_comments` (~46 tokens)

List event comments

List the comments on a feed event. Namely API: GET /events/{event-id}/comments.

Input parameters:

- `event_id` (string, required): Event id (from namely_list_events).

### `namely_get_report` (~79 tokens)

Get report

Run a saved Namely report by id and return its columns and rows (live data; each row is a list in column order). Find the id in the URL of the report in Namely. Reports can contain sensitive HR data such as salary history. Namely API: GET /reports/{id}.

Input parameters:

- `id` (string, required): Report id.

### `namely_update_profile` (~198 tokens)

Update employee profile

Change standard fields of an employee profile (name, emails, start date, status, manager, job title). WRITES live HR data. Send only the fields to change. Setting user_status to pending needs a personal_email. Namely API: PUT /profiles/{id}.

Input parameters:

- `email` (string): Company email.
- `first_name` (string): First name.
- `id` (string, required): Namely profile id (the `id` of a profile from namely_list_profiles).
- `job_title` (object): New job title: an object with the id or the exact title of an existing job title.
- `last_name` (string): Last name.
- `personal_email` (string): Personal email (required when user_status is pending).
- `reports_to` (string): Profile id of the new manager.
- `start_date` (string): Start date, YYYY-MM-DD.
- `user_status` (string): active or pending.

### `namely_create_announcement` (~139 tokens)

Post announcement

Post an announcement to the company home feed, visible to every employee. Markdown; to mention a person write [Full Name](/people/<profile_id>). With is_appreciation, mentioned people are appreciated. email_all=true ALSO EMAILS every active employee at their company address (needs the permission) and cannot be undone: set it only when the user explicitly asks. Namely API: POST /events.

Input parameters:

- `content` (string, required): Announcement text in markdown.
- `email_all` (boolean): If true, also emails all active employees. Default false.
- `is_appreciation` (boolean): If true, mentioned profiles are appreciated.

### `namely_create_event_comment` (~87 tokens)

Comment on event

Add a comment to a feed event, posted as the token's user and visible to employees who see the event. Markdown; mention a person with [Full Name](/people/<profile_id>). Namely API: POST /events/{id}/comments.

Input parameters:

- `content` (string, required): Comment text in markdown.
- `event_id` (string, required): Event id (from namely_list_events).

## Diagnostics

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

## Score history

- 2026-10-25: 63
- 2026-10-24: 63

## Common questions

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

Namely MCP by usefulapi is listed in the public MCP registry as io.usefulapi/namely. Read Namely employee profiles, groups, teams, jobs and reports; update profiles, post to the feed. This page covers its hosted endpoint (https://namely.usefulapi.io/mcp).

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

Namely MCP by usefulapi scores 63 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 Namely MCP by usefulapi server expose?

Namely MCP by usefulapi exposes 17 tools: namely_get_me, namely_list_profiles, namely_get_profile, namely_list_profile_fields, namely_list_groups, and 12 more. Their descriptions and schemas cost roughly 1,386 tokens of context every time the server is loaded.

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

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

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