Connecteam MCP by usefulapi
REMOTE · CONNECTEAM.USEFULAPI.IO
Read Connecteam users, shifts, time clock, jobs, time off, tasks and forms; create shifts and tasks.
Available components
Last scanned (6 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Project Management
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3286 tokens (~172/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.4.0 → 1.5.0 functional
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 60
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 18 Oct 2026 · Probed https://connecteam.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 connecteam.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://connecteam.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://connecteam.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://connecteam.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://connecteam.usefulapi.io/mcp |
| Authorisation server | https://connecteam.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://connecteam.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/connecteam/ |
| http (plaintext) | http://connecteam.usefulapi.io/mcp | Inconclusive | 302 | http://connecteam.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 →
connecteam_create_shift Create shift ~415
WRITE: create ONE shift in a scheduler (one assignee or one open spot: the V1 endpoint does not create group or multi-spot shifts). By default it is created as an unpublished draft (employees see nothing). With is_published=true it is published, and Connecteam notifies the assigned users unless notify_users=false. Give a title or a job_id (Connecteam requires one). For an open shift set is_open_shift=true and leave assigned_user_ids empty. POST /scheduler/v1/schedulers/{schedulerId}/shifts.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_user_ids | array | – | The user id to assign (at most one: the V1 endpoint rejects more); empty for an open shift. |
| color | string | – | Shift color from Connecteam's palette; defaults to the job's color (or #4B7AC5). |
| end_time | – | yes | Shift end: Unix seconds or ISO 8601 date-time with zone. |
| is_open_shift | boolean | – | Create an open shift with one spot that an employee can claim (default false). |
| is_published | boolean | – | Publish the shift now (default false = draft). |
| job_id | string | – | Job id (connecteam_list_jobs) to attach the shift to. |
| note | string | – | A plain-text note shown on the shift. |
| notify_users | boolean | – | For a published shift: notify the assigned users (Connecteam default true). |
| require_admin_approval | boolean | – | Claiming needs admin approval (open shifts only). |
| scheduler_id | integer | yes | Scheduler id (connecteam_list_schedulers). |
| start_time | – | yes | Shift start: Unix seconds or ISO 8601 date-time with zone. |
| task_titles | array | – | Shift tasks (checklist items) by title. |
| timezone | string | – | IANA time zone, e.g. America/New_York (default: the account's time zone). |
| title | string | – | Shift title (required unless job_id is given). |
No output schema declared.
No examples provided.
connecteam_create_task Create task ~219
WRITE: create one quick task on a task board for the given users. status 'draft' keeps it hidden; 'published' sends it to the assignees' apps. Several user ids make one group task. POST /tasks/v1/taskboards/{taskBoardId}/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Task description (plain text). |
| due_date | – | – | Due: Unix seconds or ISO 8601 date-time with zone. |
| label_ids | array | – | Label ids (connecteam_list_task_labels). |
| start_time | – | – | Start: Unix seconds or ISO 8601 date-time with zone. |
| status | string | yes | 'draft' (not visible to employees) or 'published' (sent to the assignees). |
| sub_tasks | array | – | Sub-task titles. |
| task_board_id | string | yes | Task board id (connecteam_list_task_boards). |
| title | string | yes | Task title. |
| user_ids | array | yes | Assignee user ids (several = one group task). |
No output schema declared.
No examples provided.
connecteam_get_account Get account ~30
The Connecteam company this API key belongs to: company name and company id. GET /me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connecteam_get_job Get job ~51
One job by id, with its sub-jobs, assignments and location. GET /jobs/v1/jobs/{jobId}.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job id (from connecteam_list_jobs). |
No output schema declared.
No examples provided.
connecteam_get_shift Get shift ~74
One shift of a scheduler by its id, with assignments, statuses, breaks, notes and tasks. GET /scheduler/v1/schedulers/{schedulerId}/shifts/{shiftId}.
| Name | Type | Req | Description |
|---|---|---|---|
| scheduler_id | integer | yes | Scheduler id. |
| shift_id | string | yes | Shift id (from connecteam_list_shifts). |
No output schema declared.
No examples provided.
connecteam_get_timesheet_totals Get timesheet totals ~297
Payroll-ready timesheet totals of a time clock for a date range (at most 45 days, Connecteam's limit): per user and day, total/work/paid-break/unpaid-break hours (decimal), approved/submitted/locked flags and pay items by pay rule (with pay rates when defined). Filter by users, groups, jobs or approval state. GET /time-clock/v1/time-clocks/{timeClockId}/timesheet.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Last date (yyyy-mm-dd), up to 23:59:59; at most 45 days after start_date. |
| group_ids | array | – | Only users in these smart group ids. |
| include_plan_vs_actual | boolean | – | Add scheduled-vs-actual details per day (default false). |
| is_approved | boolean | – | true = approved days only, false = unapproved only. |
| is_locked | boolean | – | true = locked only, false = unlocked only. |
| is_submitted | boolean | – | true = submitted only, false = unsubmitted only. |
| job_ids | array | – | Only these (parent or regular) job ids. |
| start_date | string | yes | First date (yyyy-mm-dd), from 00:00:00. |
| time_clock_id | integer | yes | Time clock id (connecteam_list_time_clocks). |
| user_ids | array | – | Only these user ids. |
No output schema declared.
No examples provided.
connecteam_list_form_submissions List form submissions ~175
List the submissions of one form: who submitted and when, the answers and the manager fields (status, owner, notes). Filter by submitting users and time window. GET /forms/v1/forms/{formId}/form-submissions.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | integer | yes | Form id (connecteam_list_forms). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Index of the first result (default 0); pass the previous reply's next_offset. |
| submitted_from | – | – | Submitted at or after: Unix seconds or ISO 8601 date-time with zone. |
| submitted_to | – | – | Submitted at or before: Unix seconds or ISO 8601 date-time with zone. |
| user_ids | array | – | Only submissions by these user ids. |
No output schema declared.
No examples provided.
connecteam_list_forms List forms ~126
List forms (checklists, inspections, reports) with their questions. Filter by name or creation date. GET /forms/v1/forms.
| Name | Type | Req | Description |
|---|---|---|---|
| created_from | string | – | Created on or after (yyyy-mm-dd). |
| created_to | string | – | Created on or before (yyyy-mm-dd). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| name | string | – | Name contains (case-insensitive). |
| offset | integer | – | Index of the first result (default 0); pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
connecteam_list_jobs List jobs ~218
List jobs (the work items shifts and time are tracked against): id, title, code, color, description, GPS/geofence, assigned users/groups, parent job and sub-jobs, and the schedulers/time clocks (instance ids) they belong to. GET /jobs/v1/jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Include deleted jobs (Connecteam default: true). |
| instance_ids | array | – | Only jobs of these scheduler or time clock ids. |
| job_codes | array | – | Only jobs with these codes. |
| job_ids | array | – | Only these job ids (a parent id also returns its sub-jobs). |
| job_names | array | – | Only jobs with these titles. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Index of the first result (default 0); pass the previous reply's next_offset. |
| order | string | – | Sort order (only with a sort key). |
| sort | string | – | Sort key. |
No output schema declared.
No examples provided.
connecteam_list_schedulers List schedulers ~54
List the job schedulers (schedules) in the account with their id, name, time zone and archived state. The scheduler id is needed to list or create shifts. GET /scheduler/v1/schedulers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connecteam_list_shifts List shifts ~314
List shifts of one scheduler in a time window (one row per assigned user, as Connecteam's V1 endpoint returns them): title, start/end (Unix seconds), time zone, assigned user ids, open-shift spots, job, location, published state, statuses, breaks, notes and shift tasks. Filter by assigned users, job, open or published. GET /scheduler/v1/schedulers/{schedulerId}/shifts.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_user_ids | array | – | Only shifts assigned to these user ids. |
| end_time | – | yes | Window end: Unix seconds or ISO 8601 date-time with zone. |
| is_open_shift | boolean | – | true = only open shifts, false = only assigned shifts. |
| is_published | boolean | – | true = only published shifts, false = only drafts. |
| job_ids | array | – | Only shifts of these job ids. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Index of the first result (default 0); pass the previous reply's next_offset. |
| order | string | – | Sort order (only with a sort key). |
| scheduler_id | integer | yes | Scheduler id (connecteam_list_schedulers). |
| shift_ids | array | – | Only these shift ids. |
| sort | string | – | Sort key. |
| start_time | – | yes | Window start: Unix seconds or ISO 8601 date-time with zone. |
| title | string | – | Only shifts with this title. |
No output schema declared.
No examples provided.
connecteam_list_task_boards List task boards ~46
List the quick-task boards in the account (id, name, archived). The board id is needed to list or create tasks. GET /tasks/v1/taskboards.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connecteam_list_task_labels List task labels ~117
List the labels of a task board (id, name, color), for filtering tasks or labelling a new one. GET /tasks/v1/taskboards/{taskBoardId}/labels.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Index of the first result (default 0); pass the previous reply's next_offset. |
| task_board_id | string | yes | Task board id. |
| title | string | – | Only the label with this name. |
No output schema declared.
No examples provided.
connecteam_list_tasks List tasks ~192
List tasks on a task board: title, assigned user ids, status (draft/published/completed), start and due time (Unix seconds), labels, sub-tasks and description. Filter by status, users, labels or task ids. GET /tasks/v1/taskboards/{taskBoardId}/tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| label_ids | array | – | Only tasks carrying these label ids. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Index of the first result (default 0); pass the previous reply's next_offset. |
| status | string | – | Status filter (default all). |
| task_board_id | string | yes | Task board id (connecteam_list_task_boards). |
| task_ids | array | – | Only these task ids. |
| user_ids | array | – | Only tasks assigned to these user ids (group tasks are included). |
No output schema declared.
No examples provided.
connecteam_list_time_activities List time activities ~191
Clock-in/clock-out records of a time clock for a date range (at most 31 days per call), grouped by user: worked shifts (start/end, job, sub-job, notes, auto clock-out), manual breaks and time off. Filter by users, jobs or activity type. GET /time-clock/v1/time-clocks/{timeClockId}/time-activities.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_types | array | – | Only these activity types. |
| end_date | string | yes | Last date (yyyy-mm-dd), at most 31 days after start_date. |
| job_ids | array | – | Only shifts of these job ids. |
| start_date | string | yes | First date (yyyy-mm-dd). |
| time_clock_id | integer | yes | Time clock id (connecteam_list_time_clocks). |
| user_ids | array | – | Only these user ids (users still assigned to the time clock). |
No output schema declared.
No examples provided.
connecteam_list_time_clocks List time clocks ~49
List the time clocks in the account (id, name, archived). The time clock id is needed for time activities and timesheets. GET /time-clock/v1/time-clocks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connecteam_list_time_off_policy_types List time-off policy types ~58
List time-off policy types (e.g. Vacation, Sick) and their policies with unit (hours/days) and accrual type. Needs the HR & Skills hub. GET /time-off/v1/policy-types.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
connecteam_list_time_off_requests List time-off requests ~202
List time-off requests overlapping a date range (at most 365 days): user, policy type, dates/times, all-day flag, status (approved/pending/denied), notes, approving manager and, for approved requests, the amount deducted. Connecteam returns only approved requests unless statuses is given. Needs the HR & Skills hub. GET /time-off/v1/requests.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | yes | Range end (yyyy-mm-dd), inclusive; at most 365 days after start_date. |
| limit | integer | – | Results per page, 1-100 (default 25). |
| offset | integer | – | Index of the first result (default 0); pass the previous reply's next_offset. |
| start_date | string | yes | Range start (yyyy-mm-dd), inclusive. |
| statuses | array | – | Statuses to include (default: approved only). |
| user_ids | array | – | Only these user ids. |
No output schema declared.
No examples provided.
connecteam_list_users List users ~248
List employees (users): name, email, phone, user type (user/manager/owner), archived state, smart groups, custom fields and last login. Use it to map the user ids in shifts, time activities, timesheets, time off and tasks to names. Kiosk codes and device ids are never returned. GET /users/v1/users.
| Name | Type | Req | Description |
|---|---|---|---|
| emails | array | – | Exact email addresses. |
| full_names | array | – | Exact full names ('First Last', case-insensitive). |
| limit | integer | – | Results per page, 1-100 (default 25). |
| modified_since | – | – | Only users changed after this time (Unix seconds or ISO 8601 date-time with zone). |
| offset | integer | – | Index of the first result (default 0); pass the previous reply's next_offset. |
| order | string | – | Sort order (only with a sort key). |
| phone_numbers | array | – | Phone numbers in +<country code><number> format. |
| sort | string | – | Sort key. |
| status | string | – | User status filter (Connecteam default: active). |
| user_ids | array | – | Only these user ids. |
No output schema declared.
No examples provided.
How do I install the Connecteam MCP by usefulapi server?
Connecteam MCP by usefulapi is a hosted endpoint at https://connecteam.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 · connecteam.usefulapi.io
claude mcp add --transport http io-usefulapi-connecteam 'https://connecteam.usefulapi.io/mcp'
What is the Connecteam MCP by usefulapi server?
Connecteam MCP by usefulapi is listed in the public MCP registry as io.usefulapi/connecteam. Read Connecteam users, shifts, time clock, jobs, time off, tasks and forms; create shifts and tasks. This page covers its hosted endpoint (https://connecteam.usefulapi.io/mcp).
Is the Connecteam MCP by usefulapi server safe to use?
Connecteam MCP by usefulapi scores 65 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 Connecteam MCP by usefulapi server expose?
Connecteam MCP by usefulapi exposes 19 tools: connecteam_get_account, connecteam_list_users, connecteam_list_schedulers, connecteam_list_shifts, connecteam_get_shift, and 14 more. Their descriptions and schemas cost roughly 3,076 tokens of context every time the server is loaded.
Does the Connecteam MCP by usefulapi server require authentication?
Yes. Connecteam MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Connecteam MCP by usefulapi server still maintained?
Connecteam MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.