Taleez MCP by usefulapi
REMOTE · TALEEZ.USEFULAPI.IO
Read Taleez recruiting data; create or update candidates and add them to pools or jobs.
Available components
Last scanned (6 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.07 → 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 +4
- Authorization: partial → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- MCP protocol: fail → pass ▲ functional
- New prompt “add_candidates_to_a_pool” functional
- New prompt “inspect_a_talent_pool” functional
- New prompt “look_up_a_candidate_s_applications” functional
- New prompt “review_current_job_postings” functional
- New prompt “update_a_candidate_s_profile” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.2.0 → 1.4.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- Server version: 1.0.1 → 1.1.0 functional
- 30 Oct 26 62
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 5 Nov 2026 · Probed https://taleez.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 taleez.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://taleez.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/taleez/ |
| http (plaintext) | http://taleez.usefulapi.io/mcp | Inconclusive | 302 | http://taleez.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 →
taleez_add_candidates_to_job Add candidates to a job ~121
WRITE: associate existing candidates to a job so they appear in its recruitment pipeline (the vendor's 'add candidates to a job'; this is an association made by the recruiter, not a candidate application, and this call sends no message). Pass location_id for a job with several locations. POST /0/jobs/{id}/candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_ids | array | yes | Candidate ids to associate. |
| job_id | integer | yes | Taleez job id. |
| location_id | integer | – | Location id, only for a job with several locations. |
No output schema declared.
No examples provided.
taleez_add_candidates_to_pool Add candidates to a pool ~79
WRITE: add existing candidates to a talent pool (see taleez_list_pools). Adding a candidate already in the pool is harmless. No message is sent. POST /0/pools/{id}/candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_ids | array | yes | Candidate ids to add. |
| pool_id | integer | yes | Taleez pool id. |
No output schema declared.
No examples provided.
taleez_create_candidate Create candidate ~267
WRITE: add a new candidate to the Taleez database (first and last name required; the e-mail, if given, must be unique in the company). Creates a record only: the candidate is not attached to a job and no e-mail is sent by this call. Not idempotent: calling twice with no mail creates two candidates. POST /0/candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| first_name | string | yes | – |
| lang | string | – | Candidate language (must be activated in the account). Default FR. |
| last_name | string | yes | – |
| location | object | – | Place of residence; city, country, lat and lng are all required. |
| string | – | E-mail address, unique in the company. | |
| phone | string | – | Phone, e.g. 0611223344 or +33611223344 (Taleez ignores an invalid number). |
| recruiter_id | integer | – | Credit this recruiter as the one who added the candidate (see taleez_list_recruiters). |
| social_links | object | – | Social profile links. |
| source | string | – | Where the candidate comes from (Taleez default: 'API Taleez'). |
| unit_id | integer | – | Unit of the candidate (only for companies that segment candidates by unit). |
No output schema declared.
No examples provided.
taleez_get_candidate Get candidate ~56
One candidate by id: name, mail, phone, language, location, social links, unit, CV link and custom properties. GET /0/candidates/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | Taleez candidate id. |
No output schema declared.
No examples provided.
taleez_get_candidate_applications Get candidate applications ~80
Where a candidate stands: every application or association (type SPONTANEOUS, APPLICATION_TO_A_JOB, ASSOCIATED_TO_A_JOB...) with the job id, current pipeline step, rejected/hired dates and the step history. GET /0/candidates/{id}/applications.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | Taleez candidate id. |
No output schema declared.
No examples provided.
taleez_get_candidate_documents Get candidate documents ~57
The documents attached to a candidate (CV, cover letter...): id, name, date, size and file URL. GET /0/candidates/{id}/documents.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | Taleez candidate id. |
No output schema declared.
No examples provided.
taleez_get_candidate_events Get candidate events ~60
The events (interviews, calls, meetings) scheduled with a candidate: subject, start/end, location, meeting URL, attendees. GET /0/candidates/{id}/events.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | Taleez candidate id. |
No output schema declared.
No examples provided.
taleez_get_candidate_pools Get candidate pools ~54
The talent pools a candidate belongs to (pool id, name, date added, referrer). GET /0/candidates/{id}/pools.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | Taleez candidate id. |
No output schema declared.
No examples provided.
taleez_get_candidate_properties Get candidate properties ~53
The custom property values of a candidate (property id, name key, type, value or choices). GET /0/candidates/{id}/properties.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | Taleez candidate id. |
No output schema declared.
No examples provided.
taleez_get_job Get job ~59
One job posting by id with its full details: descriptions, contract, location, recruiter, unit, tags, custom properties, public and application URLs. GET /0/jobs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Taleez job id. |
No output schema declared.
No examples provided.
taleez_get_job_filters Count jobs by filter ~55
The total number of jobs and the job counts per status, contract, city, tag and company label (only values with at least one job). A quick overview of the hiring activity. GET /0/jobs/filters.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
taleez_get_job_questions Get job application questions ~52
The questions candidates answer when applying to a job (id, label, type, required, choices). GET /0/jobs/{id}/questions.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Taleez job id. |
No output schema declared.
No examples provided.
taleez_get_job_statuses Get job status history ~57
The status history of a job: each change (date timestamp, status DRAFT/PUBLISHED/SUSPENDED/DONE). GET /0/jobs/{id}/statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Taleez job id. |
No output schema declared.
No examples provided.
taleez_get_job_steps Get job pipeline steps ~57
The recruitment pipeline steps of a job in order (id, name, order). Use them to read where each candidate stands. GET /0/jobs/{id}/steps.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | Taleez job id. |
No output schema declared.
No examples provided.
taleez_list_candidate_properties List candidate properties ~111
The custom candidate properties defined in the account (id, name, type, choices, disabled). Use the ids with taleez_set_candidate_properties. GET /0/candidate-properties.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
| with_disabled | boolean | – | Include properties disabled in the account settings. Default false. |
No output schema declared.
No examples provided.
taleez_list_candidates List candidates ~153
List the candidates in the company (id, name, mail, phone, language, location, social links, unit, creation date). Filter by exact e-mail address to find one person. Custom properties only with with_props. Candidates contain personal data: use it only for the user's own recruiting. GET /0/candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| array | – | Only candidates with one of these e-mail addresses. | |
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
| with_props | boolean | – | Include all custom candidate properties. Default false. |
No output schema declared.
No examples provided.
taleez_list_events List events ~117
List the company's calendar events (interviews, meetings): subject, start/end timestamps, location, meeting URL, job id, attendees. GET /0/events.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
| sort_by | string | – | Sort field. |
| sort_direction | string | – | Sort direction (default asc) when sort_by is set. |
No output schema declared.
No examples provided.
taleez_list_job_properties List job properties ~80
The custom job properties defined in the account (id, name, type, choices). GET /0/job-properties.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
taleez_list_jobs List jobs ~316
List the job postings of the company (id, label, status DRAFT/PUBLISHED/DONE/SUSPENDED, contract, location, recruiter, unit, tags, visibility, public URL). Filter by status, contract, unit, city, tag, company label or visibility; sort by creation or publication date. Job and profile descriptions are only included with with_details. GET /0/jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| city | array | – | Only jobs in these cities. |
| company_label | array | – | Only jobs with this exact company label. |
| contract | array | – | Only jobs with one of these contract types. |
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
| sort_by | string | – | Sort field. |
| sort_direction | string | – | Sort direction (default asc) when sort_by is set. |
| status | array | – | Only jobs in one of these statuses. |
| tag | array | – | Only jobs with these tags. |
| unit_id | array | – | Only jobs of these units (see taleez_list_units). |
| visibility | array | – | Only jobs with these visibilities (restricted jobs need a visibility token, which these tools do not send). |
| with_details | boolean | – | Include the job, profile and company descriptions (long HTML text). Default false. |
| with_props | boolean | – | Include the custom job properties. Default false. |
No output schema declared.
No examples provided.
taleez_list_pool_candidates List pool candidates ~117
The candidates in one talent pool. Custom properties only with with_props. GET /0/pools/{id}/candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
| pool_id | integer | yes | Taleez pool id (see taleez_list_pools). |
| with_props | boolean | – | Include all custom candidate properties. Default false. |
No output schema declared.
No examples provided.
taleez_list_pools List talent pools ~79
List the talent pools of the company (id, name, dates, recruiter). GET /0/pools.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
taleez_list_recruiters List recruiters ~91
List the recruiters (users) of the company. Use the ids to read who owns a job or to credit a new candidate. GET /0/recruiters.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
taleez_list_units List units ~83
List the units (entities, subsidiaries, sites) of the company. Use the ids to filter jobs. GET /0/units.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 0 (default 0). Pass the previous reply's next_page. |
| page_size | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
taleez_set_candidate_properties Set candidate properties ~106
WRITE: set custom property values on a candidate. For a property without choices pass value (DATE as yyyy-MM-dd); for a property with choices pass choices (choice ids, see taleez_list_candidate_properties). An empty choices list removes all selected choices unless append_choices is true. Overwrites the previous values of the listed properties. POST /0/candidates/{id}/properties.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | Taleez candidate id. |
| properties | array | yes | – |
No output schema declared.
No examples provided.
taleez_update_candidate Update candidate ~221
WRITE: change a candidate's name, e-mail, phone, social links or location. The current record is read first and unchanged name, mail and phone are sent back, so only what you pass changes (Taleez' update endpoint otherwise needs first and last name). Social links and location, when given, REPLACE the existing ones (an empty social_links object removes them all). Overwrites data; no message is sent. POST /0/candidates/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | Taleez candidate id. |
| first_name | string | – | – |
| last_name | string | – | – |
| location | object | – | Replaces the location; city, country, lat and lng are all required. |
| string | – | New e-mail address, unique in the company. | |
| phone | string | – | Phone, e.g. 0611223344 or +33611223344 (Taleez ignores an invalid number). |
| social_links | object | – | Replaces all social links; an empty object removes them. |
No output schema declared.
No examples provided.
How do I install the Taleez MCP by usefulapi server?
Taleez MCP by usefulapi is a hosted endpoint at https://taleez.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 · taleez.usefulapi.io
claude mcp add --transport http io-usefulapi-taleez 'https://taleez.usefulapi.io/mcp'
What is the Taleez MCP by usefulapi server?
Taleez MCP by usefulapi is listed in the public MCP registry as io.usefulapi/taleez. Read Taleez recruiting data; create or update candidates and add them to pools or jobs. This page covers its hosted endpoint (https://taleez.usefulapi.io/mcp).
Is the Taleez MCP by usefulapi server safe to use?
Taleez 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 Taleez MCP by usefulapi server expose?
Taleez MCP by usefulapi exposes 25 tools: taleez_list_jobs, taleez_get_job, taleez_get_job_steps, taleez_get_job_statuses, taleez_get_job_questions, and 20 more. Their descriptions and schemas cost roughly 2,581 tokens of context every time the server is loaded.
Does the Taleez MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Taleez 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 Taleez MCP by usefulapi server still maintained?
Taleez MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 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 Taleez MCP by usefulapi server?
VerifyMCP ran 4 checks on Taleez 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 Taleez 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.