# Traffit MCP by usefulapi (remote · traffit.usefulapi.io)

Read candidates, jobs, stages and clients; add notes to candidates in Traffit.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `traffit.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-traffit/traffit.md), [page](https://verifymcp.io/servers/io-usefulapi-traffit/traffit)

## Channel facts

- Endpoint: `https://traffit.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-traffit 'https://traffit.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-traffit": {
      "url": "https://traffit.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-traffit": {
      "type": "http",
      "url": "https://traffit.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-traffit]
url = "https://traffit.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-traffit": {
      "type": "remote",
      "url": "https://traffit.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-traffit --url 'https://traffit.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-traffit:
    url: "https://traffit.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-traffit": {
      "Transport": "http",
      "Url": "https://traffit.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-traffit -t streamable-http -u 'https://traffit.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-traffit": {
      "type": "http",
      "url": "https://traffit.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-01 (score 18, −48)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-31 (score 66)

First indexed and scored.

## MCP tools (24)

### `traffit_list_candidates` (~149 tokens)

List candidates

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/.

Input parameters:

- `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"}.

### `traffit_get_candidate` (~51 tokens)

Get a candidate

Get one candidate by id with contact data, status, files list and custom fields. Scope: employee. GET /employees/{id}.

Input parameters:

- `candidate_id` (string, required): The candidate id (numeric id).

### `traffit_get_candidate_tags` (~44 tokens)

Get candidate tags

List the tags of one candidate. Scope: employee. GET /employees/{id}/tags.

Input parameters:

- `candidate_id` (string, required): The candidate id (numeric id).

### `traffit_get_candidate_jobs` (~53 tokens)

Get candidate jobs

List the jobs (recruitments) a candidate takes part in. Scope: employee. GET /employees/{id}/recruitments.

Input parameters:

- `candidate_id` (string, required): The candidate id (numeric id).

### `traffit_get_candidate_activities` (~155 tokens)

Get candidate activities

List the activity history of one candidate (notes, stage moves, mails). Scope: employee. GET /employees/{id}/activities.

Input parameters:

- `candidate_id` (string, required): 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"}.

### `traffit_get_candidate_files` (~51 tokens)

Get candidate files

List the files (file names and upload dates) of one candidate. Scope: employee. GET /employees/{id}/files.

Input parameters:

- `candidate_id` (string, required): The candidate id (numeric id).

### `traffit_get_candidate_sources` (~47 tokens)

Get candidate sources

List where one candidate came from (source records). Scope: source. GET /sources/employees/{id}.

Input parameters:

- `candidate_id` (string, required): The candidate id (numeric id).

### `traffit_list_jobs` (~136 tokens)

List jobs

List jobs (recruitments) with paging, filters and sort. Scope: recruitment. GET /recruitments/.

Input parameters:

- `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"}.

### `traffit_get_job` (~57 tokens)

Get a job

Get one job (recruitment) by id with client, responsible people, status and custom fields. Scope: recruitment. GET /recruitments/{id}.

Input parameters:

- `job_id` (string, required): The job id (numeric id).

### `traffit_list_job_candidates` (~149 tokens)

List candidates of a job

List the candidates attached to one job. Scope: recruitment. GET /recruitments/{id}/employees.

Input parameters:

- `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, required): 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"}.

### `traffit_list_job_states` (~152 tokens)

List job stages

List the pipeline stages (states) of one job. Scope: recruitment. GET /recruitments/{id}/states.

Input parameters:

- `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, required): 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"}.

### `traffit_get_job_stage_counts` (~52 tokens)

Count candidates per stage

Count the candidates in each stage of one job. Scope: recruitment. GET /recruitments/{id}/states/counter.

Input parameters:

- `job_id` (string, required): The job id (numeric id).

### `traffit_list_stage_candidates` (~185 tokens)

List candidates in a job stage

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.

Input parameters:

- `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, required): 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, required): The stage (state) id (numeric id).

### `traffit_list_clients` (~133 tokens)

List clients

List client companies (CRM) with paging, filters and sort. Scope: client. GET /clients/.

Input parameters:

- `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"}.

### `traffit_get_client` (~41 tokens)

Get a client

Get one client company by id. Scope: client. GET /clients/{id}.

Input parameters:

- `client_id` (string, required): The client id (numeric id).

### `traffit_list_contacts` (~135 tokens)

List client contacts

List contact people (crm_persons) of client companies. Scope: crm_person. GET /crm_persons/.

Input parameters:

- `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"}.

### `traffit_get_contact` (~48 tokens)

Get a client contact

Get one contact person by id. Scope: crm_person. GET /crm_persons/{id}.

Input parameters:

- `contact_id` (string, required): The contact (crm_person) id (numeric id).

### `traffit_list_crm_activities` (~140 tokens)

List CRM activities

List CRM activities (calls, meetings, notes on clients and contacts). Scope: crm_activity. GET /crm_activities/.

Input parameters:

- `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"}.

### `traffit_list_users` (~135 tokens)

List users

List users of the Traffit account with their groups and permission groups. Scope: user. GET /users/.

Input parameters:

- `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"}.

### `traffit_get_user` (~43 tokens)

Get a user

Get one Traffit user by id. Scope: user. GET /users/{id}.

Input parameters:

- `user_id` (string, required): The user id (numeric id).

### `traffit_list_talent_pools` (~133 tokens)

List talent pools

List talent pools (named groups of candidates). Scope: talent. GET /talents.

Input parameters:

- `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"}.

### `traffit_list_sources` (~129 tokens)

List sources

List candidate sources (job boards, referrals). Scope: source. GET /sources.

Input parameters:

- `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"}.

### `traffit_get_workflow` (~54 tokens)

Get a workflow

Get one recruitment workflow by id with its stages. Scope: dictionary. GET /workflows/{id}.

Input parameters:

- `workflow_id` (string, required): The workflow id (a job shows its workflow_id) (numeric id).

### `traffit_add_candidate_note` (~76 tokens)

Add a note to a candidate

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.

Input parameters:

- `candidate_id` (string, required): The candidate id (numeric id).
- `content` (string, required): The note text.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-traffit/traffit#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 18
- 2026-10-31: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://traffit.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/traffit/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-traffit/traffit.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-traffit/traffit/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-traffit/traffit.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-traffit/traffit