Namely MCP by usefulapi
REMOTE · NAMELY.USEFULAPI.IO
Read Namely employee profiles, groups, teams, jobs and reports; update profiles, post to the feed.
Available components
Last scanned (5 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 25 Oct 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability85
- 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
- Tool/resource definitions use about 1638 tokens (~96/item across 17 items; 17 tools + 0 resources), lean.Pass
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
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 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 63
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 25 Oct 2026 · Probed https://namely.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 namely.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://namely.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://namely.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://namely.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://namely.usefulapi.io/mcp |
| Authorisation server | https://namely.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://namely.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/namely/ |
| http (plaintext) | http://namely.usefulapi.io/mcp | Inconclusive | 302 | http://namely.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 →
namely_create_announcement Post announcement ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | 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. |
No output schema declared.
No examples provided.
namely_create_event_comment Comment on event ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Comment text in markdown. |
| event_id | string | yes | Event id (from namely_list_events). |
No output schema declared.
No examples provided.
namely_get_group Get group ~49
Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Group id (from namely_list_groups). |
No output schema declared.
No examples provided.
namely_get_me Get my profile ~42
Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
namely_get_profile Get employee profile ~79
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Namely profile id (the `id` of a profile from namely_list_profiles). |
No output schema declared.
No examples provided.
namely_get_report Get report ~79
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Report id. |
No output schema declared.
No examples provided.
namely_get_team Get team ~50
Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Team id (from namely_list_teams). |
No output schema declared.
No examples provided.
namely_list_event_comments List event comments ~46
List the comments on a feed event. Namely API: GET /events/{event-id}/comments.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event id (from namely_list_events). |
No output schema declared.
No examples provided.
namely_list_events List feed events ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
namely_list_group_types List group types ~35
List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
namely_list_groups List groups ~39
List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
namely_list_job_tiers List job tiers ~33
List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
namely_list_job_titles List job titles ~31
List all job titles; each belongs to one job tier. Namely API: GET /job_titles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
namely_list_profile_fields List profile fields ~50
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
namely_list_profiles List employee profiles ~265
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
namely_list_teams List teams ~26
List all teams with their team categories. Namely API: GET /teams.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
namely_update_profile Update employee profile ~198
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Company email. | |
| first_name | string | – | First name. |
| id | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · namely.usefulapi.io
claude mcp add --transport http io-usefulapi-namely 'https://namely.usefulapi.io/mcp'
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.