CATS MCP by usefulapi
REMOTE · CATS-ATS.USEFULAPI.IO
Read CATS candidates, jobs and pipelines, and make explicitly confirmed recruiting changes.
Available components
Last scanned (1 hour 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.
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 −47
- 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 65
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://cats-ats.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 cats-ats.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | 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://cats-ats.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/cats-ats/ |
| http (plaintext) | http://cats-ats.usefulapi.io/mcp | Inconclusive | 302 | http://cats-ats.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 →
cats_add_candidate_activity Add an activity (note) to a candidate ~178
WRITE: Requires confirm:true. log an activity (a call, meeting, note...) on a candidate's record. It only records the entry in CATS: no email/SMS-send request is made, even for type 'email' or 'text_message'. Creates a new entry each time (not idempotent). POST /candidates/{id}/activities.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | CATS candidate id. |
| confirm | boolean | yes | Confirm this change to the CATS account. |
| date | string | – | When it happened (ISO 8601); default now. |
| notes | string | yes | The note text. |
| regarding_job_id | integer | – | The job order this activity is about; omit for a general activity. |
| type | string | yes | Activity type; use 'other' for a plain note. |
No output schema declared.
No examples provided.
cats_change_pipeline_status Move a candidate to another pipeline status ~188
WRITE: Requires confirm:true. change the status of a pipeline (move a candidate to another stage of a job's workflow, e.g. Interviewing, Offered, Rejected). Get the pipeline id from cats_list_candidate_pipelines and the status id from cats_list_workflow_statuses. Requires confirm:true. Requests that status triggers (which can e-mail people or change records) be suppressed: every trigger attached to the target status is sent with fire=false. CATS remains responsible for enforcing its trigger semantics; independently configured webhooks may still run. The change is recorded in the pipeline's status history. POST /pipelines/{id}/status.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | yes | Confirm this change to the CATS account. |
| pipeline_id | integer | yes | CATS pipeline id. |
| status_id | integer | yes | The status to move to; must belong to the pipeline's workflow. |
No output schema declared.
No examples provided.
cats_create_candidate Create a candidate ~273
WRITE: Requires confirm:true. create one candidate record (personal data) with name, optional contact details and notes. Refuses when CATS finds a duplicate (check_duplicate=true, the default). Creates a new record each time (not idempotent); no email-send request is made to the candidate and no login is created. POST /candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| check_duplicate | boolean | – | Refuse to create when a duplicate exists (default true). |
| city | string | – | – |
| confirm | boolean | yes | Confirm this change to the CATS account. |
| country_code | string | – | ISO 3166 two-letter country code. |
| current_employer | string | – | – |
| string | – | Primary e-mail address (stored only, never mailed). | |
| first_name | string | yes | – |
| key_skills | string | – | – |
| last_name | string | yes | – |
| notes | string | – | – |
| owner_id | integer | – | CATS user id of the record owner. |
| phone | string | – | Phone number with country code. |
| phone_type | string | – | Phone type (default mobile). |
| postal_code | string | – | – |
| source | string | – | Where the candidate came from. |
| state | string | – | – |
| title | string | – | Current job title. |
No output schema declared.
No examples provided.
cats_create_task Create a task ~182
WRITE: Requires confirm:true. create a task in CATS, optionally about a candidate, contact, company or job and assigned to a user. Creates a new task each time (not idempotent); CATS may notify the assignee. POST /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| about_id | integer | – | Id of that record. |
| about_type | string | – | Kind of record the task is about; omit for a general task. Needs about_id. |
| assigned_to_id | integer | – | CATS user id of the assignee (see cats_list_users). |
| confirm | boolean | yes | Confirm this change to the CATS account. |
| date_due | string | – | Due date (ISO 8601); omit for ASAP. |
| description | string | yes | What has to be done. |
| priority | integer | – | 1 (lowest) to 5. |
No output schema declared.
No examples provided.
cats_filter_candidates Filter candidates ~188
Filter candidates by fields (read-only, although it is a POST): first_name, last_name, title, emails.primary, address.city/state/postal_code, country_code, current_employer, key_skills, notes, dates (date_created, date_modified), owner_id, is_hot... Each condition is {field, filter, value}; filters: exactly, contains, between {gte,lte}, greater_than, less_than, is_empty, geo_distance. Paged. POST /candidates/search.
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | array | yes | One or more conditions. |
| match | string | – | How several conditions combine: all = AND (default), any = OR. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_filter_pipelines Filter pipelines ~137
Filter pipelines by id, candidate_id, job_id, status_id, rating, date_created or date_modified (read-only, although it is a POST). Each condition is {field, filter, value}. Paged. POST /pipelines/search.
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | array | yes | One or more conditions. |
| match | string | – | How several conditions combine: all = AND (default), any = OR. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_get_candidate Get candidate ~36
One candidate by id (personal data). GET /candidates/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | CATS candidate id. |
No output schema declared.
No examples provided.
cats_get_company Get company ~32
One company by id. GET /companies/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | integer | yes | CATS company id. |
No output schema declared.
No examples provided.
cats_get_contact Get contact ~36
One client contact by id (personal data). GET /contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | CATS contact id. |
No output schema declared.
No examples provided.
cats_get_job Get job ~37
One job order by id, with its description. GET /jobs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | CATS job id. |
No output schema declared.
No examples provided.
cats_get_pipeline Get pipeline ~40
One pipeline (a candidate on a job) by id. GET /pipelines/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_id | integer | yes | CATS pipeline id. |
No output schema declared.
No examples provided.
cats_get_pipeline_status_history Get pipeline status history ~92
The status changes of a pipeline over time (status, who, when). GET /pipelines/{id}/statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
| pipeline_id | integer | yes | CATS pipeline id. |
No output schema declared.
No examples provided.
cats_get_site Get CATS site ~40
The CATS site (account) this API key belongs to: id, mode (recruiter or employer) and subdomain. GET /site.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
cats_get_task Get task ~32
One task by id. GET /tasks/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | CATS task id. |
No output schema declared.
No examples provided.
cats_list_activities List activities ~84
The site-wide activity log (calls, emails logged, meetings, notes) with the record each is about, paged. GET /activities.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_candidate_activities List a candidate's activities ~96
The activity log of a candidate (calls, meetings, notes, pipeline changes), paged. GET /candidates/{id}/activities.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | CATS candidate id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_candidate_attachments List a candidate's attachments (metadata) ~104
File names, sizes and whether each file is a resume, for a candidate's attachments. Metadata only: file contents are never downloaded. GET /candidates/{id}/attachments.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | CATS candidate id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_candidate_pipelines List a candidate's pipelines ~97
The jobs a candidate is in the pipeline for, with rating, workflow and current status id. GET /candidates/{id}/pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | CATS candidate id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_candidate_tasks List a candidate's tasks ~82
Tasks attached to a candidate. GET /candidates/{id}/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_id | integer | yes | CATS candidate id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_candidates List candidates ~102
List candidates (personal data: name, emails, address, employer, skills, notes), one page at a time, max 100 per page. Use cats_search_candidates or cats_filter_candidates to find specific people. GET /candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_companies List companies ~74
List client companies (name, address, website, owner), paged. GET /companies.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_contacts List contacts ~76
List client contacts (personal data: name, title, emails, company), paged. GET /contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_job_pipelines List a job's pipeline ~101
The candidates in the pipeline of a job: pipeline id, candidate id, rating and current status id. Paged. GET /jobs/{id}/pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | integer | yes | CATS job id. |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_job_statuses List job statuses ~77
The statuses a job order can have (Active, OnHold, Closed...). GET /jobs/statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_jobs List jobs ~80
List job orders with title, location, company, recruiter, status and workflow ids, dates. Paged. GET /jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_pipelines List pipelines ~83
List candidate-to-job pipelines (candidate id, job id, rating, workflow id, status id), paged. GET /pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_tasks List tasks ~86
List tasks (description, priority 1-5, due date, assignee, completion, the record it is about), paged. GET /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_users List users ~87
List the CATS users (recruiters) with id, name, title and access level. Use the ids as owner or assignee. GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_list_workflow_statuses List workflow statuses ~114
The statuses of one pipeline workflow (id, title, prerequisites, triggers). Use the ids with cats_change_pipeline_status. GET /pipelines/workflows/{id}/statuses.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
| workflow_id | integer | yes | Workflow id, from cats_list_workflows or a pipeline's workflow_id. |
No output schema declared.
No examples provided.
cats_list_workflows List pipeline workflows ~79
The pipeline workflows (sets of statuses such as Contacted, Interviewing, Offered). GET /pipelines/workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
cats_search_candidates Search candidates ~90
Free-text search over candidates (name, email, skills, resume text...), paged. GET /candidates/search?query=.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
| query | string | yes | Search text. |
No output schema declared.
No examples provided.
cats_search_companies Search companies ~81
Free-text search over companies, paged. GET /companies/search?query=.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
| query | string | yes | Search text. |
No output schema declared.
No examples provided.
cats_search_contacts Search contacts ~81
Free-text search over client contacts, paged. GET /contacts/search?query=.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
| query | string | yes | Search text. |
No output schema declared.
No examples provided.
cats_search_jobs Search jobs ~81
Free-text search over job orders, paged. GET /jobs/search?query=.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| per_page | integer | – | Results per page, 1-100 (default 25). |
| query | string | yes | Search text. |
No output schema declared.
No examples provided.
How do I install the CATS MCP by usefulapi server?
CATS MCP by usefulapi is a hosted endpoint at https://cats-ats.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 · cats-ats.usefulapi.io
claude mcp add --transport http io-usefulapi-cats-ats 'https://cats-ats.usefulapi.io/mcp'
What is the CATS MCP by usefulapi server?
CATS MCP by usefulapi is listed in the public MCP registry as io.usefulapi/cats-ats. Read CATS candidates, jobs and pipelines, and make explicitly confirmed recruiting changes. This page covers its hosted endpoint (https://cats-ats.usefulapi.io/mcp).
Is the CATS MCP by usefulapi server safe to use?
CATS 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 CATS MCP by usefulapi server expose?
CATS MCP by usefulapi exposes 34 tools: cats_get_site, cats_list_users, cats_list_candidates, cats_get_candidate, cats_search_candidates, and 29 more. Their descriptions and schemas cost roughly 3,246 tokens of context every time the server is loaded.
Does the CATS MCP by usefulapi server require authentication?
Its publisher declares no required credentials for CATS 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 CATS MCP by usefulapi server still maintained?
CATS 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.