Recruitee MCP by usefulapi
REMOTE · RECRUITEE.USEFULAPI.IO
Search Recruitee candidates, jobs, pipelines and interviews, and add notes, tags and tasks.
Available components
Last scanned (22 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.93 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_a_candidate_and_put_them_on_a_job” functional
- New prompt “add_a_note_or_tags_or_create_a_task” functional
- New prompt “find_candidates_for_a_job_or_by_keyword” functional
- New prompt “move_a_candidate_to_another_pipeline_stage” functional
- New prompt “read_notes_and_evaluations_of_a_candidate” functional
- New prompt “see_interviews_coming_up” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 +1
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 +1
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://recruitee.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 | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| 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 recruitee.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recruitee.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/recruitee/ |
| http (plaintext) | http://recruitee.usefulapi.io/mcp | Inconclusive | 302 | http://recruitee.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 →
recruitee_add_candidate_note Add a note to a candidate ~69
WRITE: add a note to a candidate's profile, visible to the team. Recruitee: POST /c/{company_id}/candidates/{candidate_id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The note text. |
| candidate_id | integer | yes | The candidate id. |
No output schema declared.
No examples provided.
recruitee_add_candidate_tags Tag a candidate ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | The candidate id. |
| tags | array | yes | Tag names to add, e.g. ["Python developer"]. |
No output schema declared.
No examples provided.
recruitee_assign_candidate_to_offer Add a candidate to a job ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | The candidate id. |
| offer_id | integer | – | The job id. |
| talent_pool_id | integer | – | The talent pool id. |
No output schema declared.
No examples provided.
recruitee_create_candidate Create a candidate ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cover_letter | string | – | Cover letter text. |
| emails | array | – | Email addresses. |
| links | array | – | Other links (portfolio, website). |
| name | string | yes | Candidate's full name (required). |
| offer_ids | array | – | Jobs/talent pools to assign the candidate to (default stage). |
| phones | array | – | Phone numbers. |
| remote_cv_url | string | – | Public URL of the CV file for Recruitee to fetch. |
| social_links | array | – | Social profile URLs (e.g. LinkedIn). |
| sources | array | – | Source tags, e.g. ["Referral"]. |
No output schema declared.
No examples provided.
recruitee_create_task Create a task ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_ids | array | – | Assignees (admin ids). |
| candidate_id | integer | – | Candidate the task is about. |
| description | string | – | Task details. |
| due_date | string | – | Due date/time (ISO 8601). Requires timezone. |
| timezone | string | – | Timezone of the due date, e.g. Europe/Amsterdam. |
| title | string | yes | Task title (required). |
No output schema declared.
No examples provided.
recruitee_get_candidate Get one candidate ~98
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | The candidate id. |
No output schema declared.
No examples provided.
recruitee_get_current_user Get the current user ~64
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recruitee_get_offer Get one job ~72
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| offer_id | integer | yes | The job (offer) id. |
No output schema declared.
No examples provided.
recruitee_get_pipeline_template Get a hiring pipeline ~100
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_template_id | integer | yes | The pipeline template id. |
No output schema declared.
No examples provided.
recruitee_list_candidate_notes List a candidate's notes ~61
List the notes on a candidate's profile, with replies, author admin_id and visibility. Recruitee: GET /c/{company_id}/candidates/{candidate_id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | The candidate id. |
No output schema declared.
No examples provided.
recruitee_list_candidates List candidates ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| created_after | string | – | Only candidates created after this date (ISO 8601). |
| disqualified | boolean | – | true = only disqualified candidates. |
| ids | array | – | Only these candidate ids. |
| limit | integer | – | Candidates per page (default 100, max 1000). |
| offer_id | integer | – | Only candidates on this job/talent pool. |
| offset | integer | – | Number of candidates to skip. |
| qualified | boolean | – | true = only qualified candidates. |
| query | string | – | Search by candidate name or job. |
| sort | string | – | Sort order (default by_date). |
No output schema declared.
No examples provided.
recruitee_list_departments List departments ~38
List the company's departments with their ids and job counts. Recruitee: GET /c/{company_id}/departments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recruitee_list_disqualify_reasons List disqualify reasons ~56
List the company's configured disqualification reasons (id, name, position). Useful for reading why candidates were disqualified. Recruitee: GET /c/{company_id}/disqualify_reasons.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recruitee_list_evaluations List evaluations ~135
List interview results — evaluations (rating + note) and questionnaire scorecards — optionally for one candidate or by selected reviewers. Recruitee: GET /c/{company_id}/interview/results.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_ids | array | – | Only results by these admin ids. |
| candidate_id | integer | – | Only this candidate's evaluations. |
| kind | string | – | Result kind (default all). |
| limit | integer | – | Results per page (default unlimited). |
| page | integer | – | Page number; only used together with limit. |
| scope | string | – | Only mine, or all (default all). |
No output schema declared.
No examples provided.
recruitee_list_interview_events List interviews ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_ids | array | – | Only events assigned to these admin ids. |
| candidate_id | integer | – | Only this candidate's interviews. |
| end_date | string | – | Range end, YYYY-MM-DD. |
| limit | integer | – | Events per page (default unlimited). |
| page | integer | – | Page number; only used together with limit. |
| scope | string | – | Only mine, or all (default all). |
| start_date | string | – | Range start, YYYY-MM-DD. |
| status | string | – | Which events (default upcoming). |
| timezone | string | – | Timezone for the date range, e.g. Europe/Amsterdam. |
No output schema declared.
No examples provided.
recruitee_list_offers List jobs ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Only these job categories, e.g. information_technology. |
| department_ids | array | – | Only jobs in these departments. |
| employment_types | array | – | Only these employment types, e.g. fulltime. |
| hiring_manager_ids | array | – | Only jobs with these hiring managers (admin ids). |
| include | array | – | Extra field groups to return. |
| lang_codes | array | – | Only jobs in these languages, e.g. en. |
| limit | integer | – | Jobs per page (default 1000). |
| location_ids | array | – | Only jobs at these locations. |
| offer_ids | array | – | Only these job ids. |
| page | integer | – | Page number, starting at 1. |
| priorities | array | – | Only jobs with these priorities. |
| recruiter_ids | array | – | Only jobs with these recruiters (admin ids). |
| statuses | array | – | Only jobs in these statuses. |
| tag_ids | array | – | Only jobs with these job tags. |
No output schema declared.
No examples provided.
recruitee_list_tags List candidate tags ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Search tags by name. |
| sort_by | string | – | Sort field. |
| sort_order | string | – | Sort direction (default asc). |
No output schema declared.
No examples provided.
recruitee_list_tasks List tasks ~205
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).
| Name | Type | Req | Description |
|---|---|---|---|
| admin_ids | array | – | Only tasks assigned to these admin ids (company list only). |
| candidate_id | integer | – | Only this candidate's tasks. |
| limit | integer | – | Tasks per page (company list only). |
| page | integer | – | Page number, starting at 1. |
| scope | string | – | Whose tasks (company list only). |
| sort_by | string | – | Sort field (company list only). |
| sort_order | string | – | Sort direction (company list only). |
| status | string | – | Completed or open tasks only. |
No output schema declared.
No examples provided.
recruitee_list_team_members List team members ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page. |
| page | integer | – | Page number, starting at 1. |
| query | string | – | Search by name or email. |
| role_id | integer | – | Only members with this role id. |
| sort_by | string | – | Sort field (default name). |
| sort_order | string | – | Sort direction (default asc). |
No output schema declared.
No examples provided.
recruitee_move_candidate_stage Move a candidate to another stage ~168
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.
| Name | Type | Req | Description |
|---|---|---|---|
| placement_id | integer | yes | The placement id (candidate-on-job), not the candidate id. |
| stage_id | integer | yes | Destination stage id. |
| work_location_id | integer | – | Location id — required by Recruitee when the destination is a hired stage. |
No output schema declared.
No examples provided.
recruitee_search_candidates Search candidates ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | array | – | Additional Recruitee search filter objects, sent as filters_json. |
| limit | integer | – | Candidates per page (default 60). |
| page | integer | – | Page number, starting at 1. |
| query | string | – | Free-text search (adds a {"field":"all","query":...} filter). |
| sort_by | string | – | Sort key with _asc or _desc suffix, e.g. created_at_desc (default), relevance_desc, candidate_name_asc, candidate_rating_desc, candidate_stage_name_asc. |
No output schema declared.
No examples provided.
recruitee_update_candidate Update a candidate ~155
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | The candidate id. |
| cover_letter | string | – | Cover letter text. |
| emails | array | – | Full replacement list of email addresses. |
| links | array | – | Full replacement list of other links. |
| name | string | – | New full name. |
| phones | array | – | Full replacement list of phone numbers. |
| social_links | array | – | Full replacement list of social profile URLs. |
No output schema declared.
No examples provided.
How do I install the Recruitee MCP by usefulapi server?
Recruitee MCP by usefulapi is a hosted endpoint at https://recruitee.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 · recruitee.usefulapi.io
claude mcp add --transport http io-usefulapi-recruitee 'https://recruitee.usefulapi.io/mcp'
What is the Recruitee MCP by usefulapi server?
Recruitee MCP by usefulapi is listed in the public MCP registry as io.usefulapi/recruitee. Search Recruitee candidates, jobs, pipelines and interviews, and add notes, tags and tasks. This page covers its hosted endpoint (https://recruitee.usefulapi.io/mcp).
Is the Recruitee MCP by usefulapi server safe to use?
Recruitee 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 Recruitee MCP by usefulapi server expose?
Recruitee MCP by usefulapi exposes 22 tools: recruitee_get_current_user, recruitee_list_team_members, recruitee_search_candidates, recruitee_list_candidates, recruitee_get_candidate, and 17 more. Their descriptions and schemas cost roughly 3,004 tokens of context every time the server is loaded.
Does the Recruitee MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Recruitee 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 Recruitee MCP by usefulapi server still maintained?
Recruitee MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 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 Recruitee MCP by usefulapi server?
VerifyMCP ran 4 checks on Recruitee 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 Recruitee 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.