Traffit MCP by usefulapi
REMOTE · TRAFFIT.USEFULAPI.IO
Read candidates, jobs, stages and clients; add notes to candidates in Traffit.
Available components
Last scanned (12 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.
- 1 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ 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 66
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://traffit.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 traffit.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://traffit.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/traffit/ |
| http (plaintext) | http://traffit.usefulapi.io/mcp | Inconclusive | 302 | http://traffit.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 →
traffit_add_candidate_note Add a note to a candidate ~76
WRITE: add a text note to one candidate's activity history. Each call adds a new note, so do not repeat a call that succeeded. Scope: employee. POST /employees/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | The candidate id (numeric id). |
| content | string | yes | The note text. |
No output schema declared.
No examples provided.
traffit_get_candidate Get a candidate ~51
Get one candidate by id with contact data, status, files list and custom fields. Scope: employee. GET /employees/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | The candidate id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_candidate_activities Get candidate activities ~155
List the activity history of one candidate (notes, stage moves, mails). Scope: employee. GET /employees/{id}/activities.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | The candidate id (numeric id). |
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_get_candidate_files Get candidate files ~51
List the files (file names and upload dates) of one candidate. Scope: employee. GET /employees/{id}/files.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | The candidate id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_candidate_jobs Get candidate jobs ~53
List the jobs (recruitments) a candidate takes part in. Scope: employee. GET /employees/{id}/recruitments.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | The candidate id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_candidate_sources Get candidate sources ~47
List where one candidate came from (source records). Scope: source. GET /sources/employees/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | The candidate id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_candidate_tags Get candidate tags ~44
List the tags of one candidate. Scope: employee. GET /employees/{id}/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | string | yes | The candidate id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_client Get a client ~41
Get one client company by id. Scope: client. GET /clients/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | The client id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_contact Get a client contact ~48
Get one contact person by id. Scope: crm_person. GET /crm_persons/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | string | yes | The contact (crm_person) id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_job Get a job ~57
Get one job (recruitment) by id with client, responsible people, status and custom fields. Scope: recruitment. GET /recruitments/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_job_stage_counts Count candidates per stage ~52
Count the candidates in each stage of one job. Scope: recruitment. GET /recruitments/{id}/states/counter.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_user Get a user ~43
Get one Traffit user by id. Scope: user. GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The user id (numeric id). |
No output schema declared.
No examples provided.
traffit_get_workflow Get a workflow ~54
Get one recruitment workflow by id with its stages. Scope: dictionary. GET /workflows/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| workflow_id | string | yes | The workflow id (a job shows its workflow_id) (numeric id). |
No output schema declared.
No examples provided.
traffit_list_candidates List candidates ~149
List candidates in the ATS with paging, filters (e.g. created_at, name, lastname) and sort. Returns total_count and items. Scope: employee. GET /employees/.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_clients List clients ~133
List client companies (CRM) with paging, filters and sort. Scope: client. GET /clients/.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_contacts List client contacts ~135
List contact people (crm_persons) of client companies. Scope: crm_person. GET /crm_persons/.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_crm_activities List CRM activities ~140
List CRM activities (calls, meetings, notes on clients and contacts). Scope: crm_activity. GET /crm_activities/.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_job_candidates List candidates of a job ~149
List the candidates attached to one job. Scope: recruitment. GET /recruitments/{id}/employees.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| job_id | string | yes | The job id (numeric id). |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_job_states List job stages ~152
List the pipeline stages (states) of one job. Scope: recruitment. GET /recruitments/{id}/states.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| job_id | string | yes | The job id (numeric id). |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_jobs List jobs ~136
List jobs (recruitments) with paging, filters and sort. Scope: recruitment. GET /recruitments/.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_sources List sources ~129
List candidate sources (job boards, referrals). Scope: source. GET /sources.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_stage_candidates List candidates in a job stage ~185
List the candidates that are now in one stage of one job. Get stage ids from traffit_list_job_states. Scope: recruitment. GET /recruitments/{job}/states/{state}/employees.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| job_id | string | yes | The job id (numeric id). |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
| state_id | string | yes | The stage (state) id (numeric id). |
No output schema declared.
No examples provided.
traffit_list_talent_pools List talent pools ~133
List talent pools (named groups of candidates). Scope: talent. GET /talents.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
traffit_list_users List users ~135
List users of the Traffit account with their groups and permission groups. Scope: user. GET /users/.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | object | – | Filters joined by AND, keyed by field name, e.g. {"created_at":{"value":"2026-01-01","comparison":">="}}. Custom fields work when exposed in the API. |
| page | integer | – | Page number (default 1). |
| page_size | integer | – | Records per page (default 20, max 100). |
| sort | object | – | Sort order keyed by field name, e.g. {"created_at":"DESC"}. |
No output schema declared.
No examples provided.
How do I install the Traffit MCP by usefulapi server?
Traffit MCP by usefulapi is a hosted endpoint at https://traffit.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 · traffit.usefulapi.io
claude mcp add --transport http io-usefulapi-traffit 'https://traffit.usefulapi.io/mcp'
What is the Traffit MCP by usefulapi server?
Traffit MCP by usefulapi is listed in the public MCP registry as io.usefulapi/traffit. Read candidates, jobs, stages and clients; add notes to candidates in Traffit. This page covers its hosted endpoint (https://traffit.usefulapi.io/mcp).
Is the Traffit MCP by usefulapi server safe to use?
Traffit 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 Traffit MCP by usefulapi server expose?
Traffit MCP by usefulapi exposes 24 tools: traffit_list_candidates, traffit_get_candidate, traffit_get_candidate_tags, traffit_get_candidate_jobs, traffit_get_candidate_activities, and 19 more. Their descriptions and schemas cost roughly 2,348 tokens of context every time the server is loaded.
Does the Traffit MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Traffit 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 Traffit MCP by usefulapi server still maintained?
Traffit 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 Traffit MCP by usefulapi server?
VerifyMCP ran 4 checks on Traffit 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 Traffit 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.