Namely MCP by usefulapi

io.usefulapi/namelyusefulapi.iostreamable-httpv1.0.0Scanned 1 hour ago

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

17 tools: 3 can delete or cancel things, 1 change things and 13 only read.

Reads private data · 1
Reads text others write · 2
Can send data out · 1
1 finding

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

17 tools

Deletes or cancels 3Removes, cancels or revokes something.Claude Code: deny

namely_create_announcementPost an announcement to the company home feed, visible to every employee.No findings
Why it is in this group
- The name "namely_create_announcement" says "create": a word for a change.
- The description says "cannot be undone".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- title: Post announcement
- destructiveHint: true
namely_create_event_commentAdd a comment to a feed event, posted as the token's user and visible to employees who see the event.Can send data outNo findings
Why it is in this group
- The name "namely_create_event_comment" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "namely_create_event_comment" says "create" and "comment": it writes something other people read.
Description, as the server wrote it
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.
Annotations the server declares
- title: Comment on event
- destructiveHint: true
namely_update_profileChange standard fields of an employee profile (name, emails, start date, status, manager, job title).No findings
Why it is in this group
- The name "namely_update_profile" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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}.
Annotations the server declares
- title: Update employee profile
- destructiveHint: true
- idempotentHint: true

Changes things 1Creates or changes something that can be changed back.Claude Code: ask

namely_get_reportRun a saved Namely report by id and return its columns and rows (live data; each row is a list in column order).1 finding
Why it is in this group
- The name "namely_get_report" says "get": a word for reading.
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "namely_get_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true}; The name "namely_get_report" says "get": a word for reading.
  What this check looks for
Description, as the server wrote it
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}.
Annotations the server declares
- title: Get report
- readOnlyHint: true

Only reads 13Looks things up and changes nothing.Show 13 read-only tools

namely_get_groupGet one group by id, with the profiles (members) linked to it.No findings
Why it is in this group
- The name "namely_get_group" says "get": a word for reading.
Description, as the server wrote it
Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.
Annotations the server declares
- title: Get group
- readOnlyHint: true
namely_get_meGet the profile of the user the connected token belongs to (name, email, job title, manager, access role).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "namely_get_me" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "get" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it
Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.
Annotations the server declares
- title: Get my profile
- readOnlyHint: true
namely_get_profileGet 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).No findings
Why it is in this group
- The name "namely_get_profile" says "get": a word for reading.
Description, as the server wrote it
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}.
Annotations the server declares
- title: Get employee profile
- readOnlyHint: true
namely_get_teamGet one team by id, with the profiles (members) linked to it.No findings
Why it is in this group
- The name "namely_get_team" says "get": a word for reading.
Description, as the server wrote it
Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.
Annotations the server declares
- title: Get team
- readOnlyHint: true
namely_list_event_commentsList the comments on a feed event.Reads text others writeNo findings
Why it is in this group
- The name "namely_list_event_comments" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "namely_list_event_comments" says "list" and "comment": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "comment": it reads comments, which other people can write.
Description, as the server wrote it
List the comments on a feed event. Namely API: GET /events/{event-id}/comments.
Annotations the server declares
- title: List event comments
- readOnlyHint: true
namely_list_eventsList 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.No findings
Why it is in this group
- The name "namely_list_events" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List feed events
- readOnlyHint: true
namely_list_group_typesList the group types (the containers of groups, such as Department or Office).No findings
Why it is in this group
- The name "namely_list_group_types" says "list": a word for reading.
Description, as the server wrote it
List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.
Annotations the server declares
- title: List group types
- readOnlyHint: true
namely_list_groupsList all groups (departments, office locations and other company groups).No findings
Why it is in this group
- The name "namely_list_groups" says "list": a word for reading.
Description, as the server wrote it
List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.
Annotations the server declares
- title: List groups
- readOnlyHint: true
namely_list_job_tiersList all job tiers (the levels that group job titles).No findings
Why it is in this group
- The name "namely_list_job_tiers" says "list": a word for reading.
Description, as the server wrote it
List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.
Annotations the server declares
- title: List job tiers
- readOnlyHint: true
namely_list_job_titlesList all job titles; each belongs to one job tier.No findings
Why it is in this group
- The name "namely_list_job_titles" says "list": a word for reading.
Description, as the server wrote it
List all job titles; each belongs to one job tier. Namely API: GET /job_titles.
Annotations the server declares
- title: List job titles
- readOnlyHint: true
namely_list_profile_fieldsList 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.No findings
Why it is in this group
- The name "namely_list_profile_fields" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: List profile fields
- readOnlyHint: true
namely_list_profilesList employee profiles (active, pending and inactive unless filtered) with paging, sorting and filters.No findings
Why it is in this group
- The name "namely_list_profiles" says "list": a word for reading.
Description, as the server wrote it
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).
Annotations the server declares
- title: List employee profiles
- readOnlyHint: true
namely_list_teamsList all teams with their team categories.No findings
Why it is in this group
- The name "namely_list_teams" says "list": a word for reading.
Description, as the server wrote it
List all teams with their team categories. Namely API: GET /teams.
Annotations the server declares
- title: List teams
- readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1: Reads files, mail, messages, databases, secrets, calendars or repositories.; namely_get_me
Reads text others write2: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; namely_get_me
namely_list_event_comments
Can send data out1: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.; namely_create_event_comment

deny to break every path

{
  "permissions": {
    "deny": [
      "mcp__namely__namely_create_event_comment"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 warn

Warnnamely_get_report
The server marks "namely_get_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true}; The name "namely_get_report" says "get": a word for reading.
What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http namely https://namely.usefulapi.io/mcp

claude mcp add --transport http namely https://namely.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__namely__namely_get_me",
      "mcp__namely__namely_list_profiles",
      "mcp__namely__namely_get_profile",
      "mcp__namely__namely_list_profile_fields",
      "mcp__namely__namely_list_groups",
      "mcp__namely__namely_get_group",
      "mcp__namely__namely_list_group_types",
      "mcp__namely__namely_list_teams",
      "mcp__namely__namely_get_team",
      "mcp__namely__namely_list_job_titles",
      "mcp__namely__namely_list_job_tiers",
      "mcp__namely__namely_list_events",
      "mcp__namely__namely_list_event_comments"
    ],
    "ask": [
      "mcp__namely__namely_get_report"
    ],
    "deny": [
      "mcp__namely__namely_update_profile",
      "mcp__namely__namely_create_announcement",
      "mcp__namely__namely_create_event_comment"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as namely. Review it before you use it.

Capability tags behind 3 rules

mcp__namely__namely_get_me private-data, untrusted-input
mcp__namely__namely_list_event_comments untrusted-input
mcp__namely__namely_create_event_comment outbound

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/io.usefulapi/namely/verify?hash=8d863f4bef451c4c8c1fce1846caf505e7e290333390c710bb23f09aa92b4a3d" | jq -e '.changed == false'

Pinned hash 8d863f4bef45, from Oct 24, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/namely/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/io.usefulapi/namely.svg)](https://anlyon.dev/servers/io.usefulapi/namely)

Source: MCP Registry · repository. Synced Oct 24, 2026, 11:18 UTC.