Skip to content

Recruitee MCP by usefulapi

io.usefulapi/recruiteeusefulapi.iostreamable-httpv1.42.5Scanned

Search Recruitee candidates, jobs, pipelines and interviews, and add notes, tags and tasks.

22 tools: 7 can delete or cancel things and 15 only read.

Tools: 7 delete, 0 irreversible, 0 write, 15 read.
  • Reads private data · 4
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

7 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 Radar 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 →

What the Recruitee MCP by usefulapi can do

The Recruitee MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 22 tools. It can delete or cancel things (7 tools: recruitee_create_candidate, recruitee_update_candidate, recruitee_add_candidate_note, recruitee_add_candidate_tags and 3 more). 15 tools only read.

4 tools read private data (recruitee_get_current_user, recruitee_get_candidate, recruitee_list_candidate_notes and 1 more); 3 tools bring in text other people can write (recruitee_get_current_user, recruitee_get_candidate and recruitee_list_candidate_notes).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.42.5.

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.

22 tools

Deletes or cancels 7Claude Code: deny
  • recruitee_add_candidate_noteWRITE: add a note to a candidate's profile, visible to the team.No findings

    Why it is in this group

    • The name "recruitee_add_candidate_note" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: add a note to a candidate's profile, visible to the team. Recruitee: POST /c/{company_id}/candidates/{candidate_id}/notes.

    Annotations the server declares

    • title: Add a note to a candidate
    • destructiveHint: true
  • recruitee_add_candidate_tagsWRITE: add one or more tags to a candidate (existing tags are reused by name; new names create new tags).No findings

    Why it is in this group

    • The name "recruitee_add_candidate_tags" says "add": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: add one or more tags to a candidate (existing tags are reused by name; new names create new tags). Recruitee: POST /c/{company_id}/candidates/{candidate_id}/tags.

    Annotations the server declares

    • title: Tag a candidate
    • destructiveHint: true
  • recruitee_assign_candidate_to_offerWRITE: put an existing candidate on a job (or talent pool) — creates a placement in the pipeline's first stage.No findings

    Why it is in this group

    • The name "recruitee_assign_candidate_to_offer" says "assign": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: put an existing candidate on a job (or talent pool) — creates a placement in the pipeline's first stage. Pass exactly one of offer_id or talent_pool_id. Recruitee: POST /c/{company_id}/placements.

    Annotations the server declares

    • title: Add a candidate to a job
    • destructiveHint: true
  • recruitee_create_candidateWRITE: add a candidate manually (as if a recruiter added them in the app — no auto-confirmation email is sent), optionally assigning them straight to one or more jobs in the job's …No findings

    Why it is in this group

    • The name "recruitee_create_candidate" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: add a candidate manually (as if a recruiter added them in the app — no auto-confirmation email is sent), optionally assigning them straight to one or more jobs in the job's default stage. Recruitee: POST /c/{company_id}/candidates.

    Annotations the server declares

    • title: Create a candidate
    • destructiveHint: true
  • recruitee_create_taskWRITE: create a recruiting task, optionally about a candidate, assigned to team members (admin ids from recruitee_list_team_members), with an optional due date.No findings

    Why it is in this group

    • The name "recruitee_create_task" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: create a recruiting task, optionally about a candidate, assigned to team members (admin ids from recruitee_list_team_members), with an optional due date. Recruitee: POST /c/{company_id}/tasks.

    Annotations the server declares

    • title: Create a task
    • destructiveHint: true
  • recruitee_move_candidate_stageWRITE: move a candidate to another stage of a job's pipeline.No findings

    Why it is in this group

    • The name "recruitee_move_candidate_stage" says "move": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: move a candidate to another stage of a job's pipeline. Takes the PLACEMENT id (from recruitee_get_candidate → placements[].id, one per job) and the destination stage id (from recruitee_get_pipeline_template). Moving to a 'hired' stage also requires work_location_id. Stage automations configured in Recruitee may run. Undo by moving back. Recruitee: PATCH /c/{company_id}/placements/{id}/change_stage.

    Annotations the server declares

    • title: Move a candidate to another stage
    • destructiveHint: true
  • recruitee_update_candidateWRITE: update a candidate's name or contact details.No findings

    Why it is in this group

    • The name "recruitee_update_candidate" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: update a candidate's name or contact details. Only the fields you pass change; list fields (emails, phones, links) REPLACE the existing list, so pass the full list you want. Recruitee: PATCH /c/{company_id}/candidates/{id}.

    Annotations the server declares

    • title: Update a candidate
    • destructiveHint: true
Only reads 15Show 15 read-only tools
  • recruitee_get_candidateFetch one candidate's full profile: contact details, sources, tags, cover letter, CV URL, custom fields, ratings, and `placements` — one per job they are on, each with its placemen…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "recruitee_get_candidate" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "contact": it reads contacts.
    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Fetch one candidate's full profile: contact details, sources, tags, cover letter, CV URL, custom fields, ratings, and `placements` — one per job they are on, each with its placement id and current stage. The placement id is what recruitee_move_candidate_stage needs. Recruitee: GET /c/{company_id}/candidates/{id}.

    Annotations the server declares

    • title: Get one candidate
    • readOnlyHint: true
  • recruitee_get_current_userFetch the Recruitee user the API token belongs to — name, email, role, role abilities and company id.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "recruitee_get_current_user" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "fetch" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Fetch the Recruitee user the API token belongs to — name, email, role, role abilities and company id. A cheap way to confirm the token and company id are right. Recruitee: GET /c/{company_id}/admin.

    Annotations the server declares

    • title: Get the current user
    • readOnlyHint: true
  • recruitee_get_offerFetch one job or talent pool by id with its full details: description, requirements, location, salary, employment type, candidate counters and pipeline_template_id.No findings

    Why it is in this group

    • The name "recruitee_get_offer" says "get": a word for reading.
    Description, as the server wrote it
    Fetch one job or talent pool by id with its full details: description, requirements, location, salary, employment type, candidate counters and pipeline_template_id. Recruitee: GET /c/{company_id}/offers/{id}.

    Annotations the server declares

    • title: Get one job
    • readOnlyHint: true
  • recruitee_get_pipeline_templateFetch a pipeline template with its ordered stages (id, name, group, category).No findings

    Why it is in this group

    • The name "recruitee_get_pipeline_template" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a pipeline template with its ordered stages (id, name, group, category). A job's `pipeline_template_id` (from recruitee_list_offers / recruitee_get_offer) names its pipeline; the stage ids here are what recruitee_move_candidate_stage takes. Recruitee: GET /c/{company_id}/pipeline_templates/{id}.

    Annotations the server declares

    • title: Get a hiring pipeline
    • readOnlyHint: true
  • recruitee_list_candidate_notesList the notes on a candidate's profile, with replies, author admin_id and visibility.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "recruitee_list_candidate_notes" says "list": a word for reading.

    What it can reach

    • private-dataThe name "recruitee_list_candidate_notes" says "list" and "note": it reads notes.
    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    • untrusted-inputThe description's first sentence says "list" and "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    List the notes on a candidate's profile, with replies, author admin_id and visibility. Recruitee: GET /c/{company_id}/candidates/{candidate_id}/notes.

    Annotations the server declares

    • title: List a candidate's notes
    • readOnlyHint: true
  • recruitee_list_candidatesList candidates, newest first, optionally narrowed to one job, a name/job search, qualified or disqualified only, specific ids, or those created after a date.No findings

    Why it is in this group

    • The name "recruitee_list_candidates" says "list": a word for reading.
    Description, as the server wrote it
    List candidates, newest first, optionally narrowed to one job, a name/job search, qualified or disqualified only, specific ids, or those created after a date. Paginate with limit + offset (next offset = offset + limit). Recruitee: GET /c/{company_id}/candidates.

    Annotations the server declares

    • title: List candidates
    • readOnlyHint: true
  • recruitee_list_departmentsList the company's departments with their ids and job counts.No findings

    Why it is in this group

    • The name "recruitee_list_departments" says "list": a word for reading.
    Description, as the server wrote it
    List the company's departments with their ids and job counts. Recruitee: GET /c/{company_id}/departments.

    Annotations the server declares

    • title: List departments
    • readOnlyHint: true
  • recruitee_list_disqualify_reasonsList the company's configured disqualification reasons (id, name, position).No findings

    Why it is in this group

    • The name "recruitee_list_disqualify_reasons" says "list": a word for reading.
    Description, as the server wrote it
    List the company's configured disqualification reasons (id, name, position). Useful for reading why candidates were disqualified. Recruitee: GET /c/{company_id}/disqualify_reasons.

    Annotations the server declares

    • title: List disqualify reasons
    • readOnlyHint: true
  • recruitee_list_evaluationsList interview results — evaluations (rating + note) and questionnaire scorecards — optionally for one candidate or by selected reviewers.Reads private dataNo findings

    Why it is in this group

    • The name "recruitee_list_evaluations" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    List interview results — evaluations (rating + note) and questionnaire scorecards — optionally for one candidate or by selected reviewers. Recruitee: GET /c/{company_id}/interview/results.

    Annotations the server declares

    • title: List evaluations
    • readOnlyHint: true
  • recruitee_list_interview_eventsList scheduled interview events (candidate_id, offer_id, stage_id, start time, duration, location, attendees).No findings

    Why it is in this group

    • The name "recruitee_list_interview_events" says "list": a word for reading.
    Description, as the server wrote it
    List scheduled interview events (candidate_id, offer_id, stage_id, start time, duration, location, attendees). Defaults to upcoming events for the whole company; narrow by candidate, date range or interviewer. Recruitee: GET /c/{company_id}/interview/events.

    Annotations the server declares

    • title: List interviews
    • readOnlyHint: true
  • recruitee_list_offersList the company's jobs (Recruitee calls them offers) with id, title, status, slug, department_id, recruiter_id, hiring_manager_id and pipeline_template_id.No findings

    Why it is in this group

    • The name "recruitee_list_offers" says "list": a word for reading.
    Description, as the server wrote it
    List the company's jobs (Recruitee calls them offers) with id, title, status, slug, department_id, recruiter_id, hiring_manager_id and pipeline_template_id. Filter by status, department, location, recruiter, hiring manager, tag and more; add heavy fields with `include` (e.g. counters for candidate counts, description, salary, location_ids). Paginated with limit + page (default 1000 per page); `meta.total_count` gives the total. Recruitee: GET /c/{company_id}/offers.

    Annotations the server declares

    • title: List jobs
    • readOnlyHint: true
  • recruitee_list_tagsList the company's candidate tags with ids and usage counts.No findings

    Why it is in this group

    • The name "recruitee_list_tags" says "list": a word for reading.
    Description, as the server wrote it
    List the company's candidate tags with ids and usage counts. Tag ids are used in recruitee_search_candidates filters. Recruitee: GET /c/{company_id}/tags.

    Annotations the server declares

    • title: List candidate tags
    • readOnlyHint: true
  • recruitee_list_tasksList recruiting tasks (title, description, due date, completed, candidate_id).No findings

    Why it is in this group

    • The name "recruitee_list_tasks" says "list": a word for reading.
    Description, as the server wrote it
    List recruiting tasks (title, description, due date, completed, candidate_id). With candidate_id, lists that candidate's tasks (Recruitee: GET /c/{company_id}/candidates/{candidate_id}/tasks — only `status` applies). Otherwise lists company tasks with scope, assignee, sorting and paging (Recruitee: GET /c/{company_id}/tasks).

    Annotations the server declares

    • title: List tasks
    • readOnlyHint: true
  • recruitee_list_team_membersList the company's team members (memberships): admin_id, role, whether they are a recruiter or hiring manager, and the jobs they can access.No findings

    Why it is in this group

    • The name "recruitee_list_team_members" says "list": a word for reading.
    Description, as the server wrote it
    List the company's team members (memberships): admin_id, role, whether they are a recruiter or hiring manager, and the jobs they can access. Use admin_id values for task assignees and filters. User names/emails are in the `references` array. Recruitee: GET /c/{company_id}/memberships.

    Annotations the server declares

    • title: List team members
    • readOnlyHint: true
  • recruitee_search_candidatesSearch the company's candidates with Recruitee's candidate search (the same engine as the app's filters).No findings

    Why it is in this group

    • The name "recruitee_search_candidates" says "search": a word for reading.
    Description, as the server wrote it
    Search the company's candidates with Recruitee's candidate search (the same engine as the app's filters). `query` is a free-text search across name, emails, phones, tags, sources, job assignments, current stage, cover letter and CV content. `filters` accepts Recruitee filter objects verbatim, e.g. {"field":"created_at","gte":1548975600} (Unix seconds), {"field":"has_cv","eq":true}, {"filter":"tags","id":{"in":[12]}}, {"filter":"stages","name":{"in":["Phone interview"]}}. Returns `hits` (with each candidate's placements: job + current stage) and `total`. Recruitee: GET /c/{company_id}/search/new/candidates.

    Annotations the server declares

    • title: Search candidates
    • 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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

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

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

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:38 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://recruitee.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://recruitee.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://recruitee.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://recruitee.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

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

claude mcp add --transport http recruitee https://recruitee.usefulapi.io/mcp
claude mcp add --transport http recruitee https://recruitee.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__recruitee__recruitee_get_current_user",
      "mcp__recruitee__recruitee_list_team_members",
      "mcp__recruitee__recruitee_search_candidates",
      "mcp__recruitee__recruitee_list_candidates",
      "mcp__recruitee__recruitee_get_candidate",
      "mcp__recruitee__recruitee_list_candidate_notes",
      "mcp__recruitee__recruitee_list_offers",
      "mcp__recruitee__recruitee_get_offer",
      "mcp__recruitee__recruitee_get_pipeline_template",
      "mcp__recruitee__recruitee_list_departments",
      "mcp__recruitee__recruitee_list_tags",
      "mcp__recruitee__recruitee_list_disqualify_reasons",
      "mcp__recruitee__recruitee_list_tasks",
      "mcp__recruitee__recruitee_list_interview_events",
      "mcp__recruitee__recruitee_list_evaluations"
    ],
    "ask": [],
    "deny": [
      "mcp__recruitee__recruitee_create_candidate",
      "mcp__recruitee__recruitee_update_candidate",
      "mcp__recruitee__recruitee_add_candidate_note",
      "mcp__recruitee__recruitee_add_candidate_tags",
      "mcp__recruitee__recruitee_assign_candidate_to_offer",
      "mcp__recruitee__recruitee_move_candidate_stage",
      "mcp__recruitee__recruitee_create_task"
    ]
  }
}

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 recruitee. Review it before you use it.

Capability tags behind 4 rules
  • mcp__recruitee__recruitee_get_current_user private-data, untrusted-input
  • mcp__recruitee__recruitee_get_candidate private-data, untrusted-input
  • mcp__recruitee__recruitee_list_candidate_notes private-data, untrusted-input
  • mcp__recruitee__recruitee_list_evaluations private-data

Pin

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://radar.anlyon.com/api/v1/servers/io.usefulapi/recruitee/verify?hash=6b983d19d9ff771e5e05e01471e0c71bc969fb42ca7c9dadade9635e3b0a6f0c" | jq -e '.changed == false'

Pinned hash 6b983d19d9ff, from Oct 25, 2026, 23:19 UTC.

Watch

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

https://radar.anlyon.com/servers/io.usefulapi/recruitee/changes.xml

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

Badge

Anlyon Radar badge for io.usefulapi/recruitee
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/recruitee.svg)](https://radar.anlyon.com/servers/io.usefulapi/recruitee)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Recruitee MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Recruitee MCP by usefulapi safe?

No scan can promise that. What its definitions show: 22 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Recruitee MCP by usefulapi delete data?

Yes. 7 tools can delete, cancel or revoke something: recruitee_create_candidate, recruitee_update_candidate, recruitee_add_candidate_note, recruitee_add_candidate_tags, recruitee_assign_candidate_to_offer, recruitee_move_candidate_stage and 1 more.

Can the Recruitee MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Recruitee MCP by usefulapi have?

22 tools: 7 destructive, 15 read. recruitee_create_candidate, recruitee_update_candidate, recruitee_add_candidate_note, recruitee_add_candidate_tags, recruitee_assign_candidate_to_offer, recruitee_move_candidate_stage, recruitee_create_task, recruitee_get_current_user and 14 more.

Does the Recruitee MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Recruitee MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Recruitee MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.