Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Synchroteam MCP by usefulapi

REMOTE · SYNCHROTEAM.USEFULAPI.IO

Read Synchroteam jobs, customers, sites, equipment and parts; create, schedule and complete jobs.

62 Trust /100

Last scanned (2 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 17 Oct 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5087 tokens (~154/item across 33 items; 33 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 Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 64% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 34 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
Changelog

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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +3
    • 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.0.0 → 1.1.0 functional
  • 13 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Oct 26 57

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Probed https://synchroteam.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 synchroteam.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://synchroteam.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Bearer realm="OAuth", resource_metadata="https://synchroteam.usefulapi.io/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://synchroteam.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://synchroteam.usefulapi.io/mcp
Authorisation server https://synchroteam.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://synchroteam.usefulapi.io/mcp Redirected 302 https://usefulapi.io/synchroteam/
http (plaintext) http://synchroteam.usefulapi.io/mcp Inconclusive 302 http://synchroteam.usefulapi.io/mcp
MCP tools · 33 exposed · ~4,872 tokens

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 →

Tool Tokens
synchroteam_complete_job ~166

WRITE: mark a job as completed, optionally with the real start and end times (give actual_start and actual_end together: Synchroteam may refuse the call with only one of them). Completing may trigger the account's 'job completed' notifications (email/SMS/webhook to managers, technicians or the customer), as configured in Synchroteam. Identify the job by exactly one of id, my_id or num. POST /job/complete.

NameTypeReqDescription
actual_endstring–Real end, yyyy-mm-dd hh:mm:ss.
actual_startstring–Real start, yyyy-mm-dd hh:mm:ss.
idstring–Job id.
my_idstring–Job myId.
numinteger–Job number.

No output schema declared.

No examples provided.

synchroteam_create_customer ~184

WRITE: create a new customer (name and an address are required). If you pass myId and a customer with that myId already exists, nothing is created and an error is returned (use synchroteam_update_customer). POST /customer/send.

NameTypeReqDescription
addressstring–Full address on one line (e.g. '6605 Fisher Avenue, Falls Church, VA 22046, United States').
addressComplementstring–Complementary address line (unit, floor...).
contact_emailstring––
contact_faxstring––
contact_first_namestring––
contact_last_namestring––
contact_phonestring––
my_idstring–Your own reference for this customer.
namestringyesCustomer name.
vat_numberstring––

No output schema declared.

No examples provided.

synchroteam_create_equipment ~121

WRITE: create a new piece of equipment under a site or a customer (give exactly one of site or customer; both is refused). If myId already exists nothing is created and an error is returned. POST /equipment/send.

NameTypeReqDescription
customerobject–The customer (when there is no site): exactly one of id or myId.
my_idstring–Your own reference for this equipment.
namestringyesEquipment name.
siteobject–The site: exactly one of id or myId.

No output schema declared.

No examples provided.

synchroteam_create_job ~320

WRITE: create a new job for a customer (status created, not yet scheduled; use synchroteam_schedule_job to assign a technician and time). The customer is required (id, myId or exact name); site, equipment and job type are optional. If myId already exists nothing is created and an error is returned. Synchroteam may send the account's 'job created' notifications (email/SMS/webhook, possibly to the customer), as configured. POST /job/send.

NameTypeReqDescription
addressstring–Full address on one line (e.g. '6605 Fisher Avenue, Falls Church, VA 22046, United States').
addressComplementstring–Complementary address line (unit, floor...).
contact_emailstring––
contact_first_namestring––
contact_last_namestring––
contact_mobilestring––
contact_phonestring––
customerobjectyesThe customer: exactly one of id, myId or name.
descriptionstring–Job description.
equipmentobject–The equipment: exactly one of id or myId.
my_idstring–Your own reference for this job.
prioritystring–Default medium.
siteobject–The site: exactly one of id or myId.
skillsarray–Required skills.
typeobject–Job type: exactly one of id or name (synchroteam_list_job_types).

No output schema declared.

No examples provided.

synchroteam_create_site ~179

WRITE: create a new site (a location of a customer). Needs a name, an address and the customer (id or myId). If myId already exists nothing is created and an error is returned. POST /site/send.

NameTypeReqDescription
addressstring–Full address on one line (e.g. '6605 Fisher Avenue, Falls Church, VA 22046, United States').
addressComplementstring–Complementary address line (unit, floor...).
contact_emailstring––
contact_mobilestring––
contact_namestring––
contact_phonestring––
customerobjectyesThe customer: exactly one of id or myId.
my_idstring–Your own reference for this site.
namestringyesSite name.

No output schema declared.

No examples provided.

synchroteam_get_customer ~62

One customer by id, myId, exact name or e-mail, with address, contact, custom fields and tags. GET /customer/details.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_get_depot ~52

One stock depot by id, with the quantity of each part it holds. GET /depot/details.

NameTypeReqDescription
idstringyesDepot id (a GUID from synchroteam_list_depots).

No output schema declared.

No examples provided.

synchroteam_get_equipment ~58

One piece of equipment by id, myId or exact name, with its customer and site. GET /equipment/details.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_get_invoice ~51

One invoice by id, reference or number, with its lines. GET /invoice/details.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_get_job ~82

One job by num (the job number shown in the app), id or myId: status, customer/site/equipment, technician(s), schedule, actual times, time entries, parts used, report and custom fields. GET /job/details.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_get_job_photos ~62

Photo links of a job (url, file name, comment, report iteration). Image bytes are never returned. GET /job/photos.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_get_part ~47

One part or service by id or reference. GET /part/details.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_get_quotation ~52

One quotation by id, reference or number, with its lines. GET /quotation/details.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_get_site ~60

One site by id, myId or exact name: address, contact, customer, custom fields, tags. GET /site/details.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_get_user ~45

One user by login or id. GET /user/details.

NameTypeReqDescription
bystringyesWhich identifier `value` is.
valuestringyesThe identifier.

No output schema declared.

No examples provided.

synchroteam_list_activities ~197

List time entries and unavailabilities (travel, at work, clock, unavailable) of technicians. start_date and end_date go together and return anything overlapping that range. GET /activity/list.

NameTypeReqDescription
activity_type_categorystring––
activity_type_namestring–Exact activity type name.
end_datestring–Range end (requires start_date).
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
sortstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).
start_datestring–Range start (requires end_date).
team_idinteger––
user_idinteger––
user_loginstring––

No output schema declared.

No examples provided.

synchroteam_list_contracts ~191

List service contracts by name, customer, site, period or active flag. GET /contract/list.

NameTypeReqDescription
activeboolean–Active contracts (default true).
customer_idinteger––
customer_my_idstring––
endstring–Contracts on or before this date (yyyy-mm-dd).
namestring––
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
site_idinteger––
site_my_idstring––
sortstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).
startstring–Contracts on or after this date (yyyy-mm-dd).

No output schema declared.

No examples provided.

synchroteam_list_customers ~174

List or search customers (name wildcard, e-mail, active flag, change time). Returns name, address, contact, custom fields, tags. GET /customer/list.

NameTypeReqDescription
activeboolean–Active customers (default true); false lists deactivated ones.
changed_sincestring–Only customers modified after this UTC date-time.
emailstring–Exact contact e-mail.
namestring–Wildcard name search.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
sortstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).

No output schema declared.

No examples provided.

synchroteam_list_depots ~158

List stock depots (warehouses and technician vans). The part quantities of one depot come from synchroteam_get_depot. GET /depot/list.

NameTypeReqDescription
is_defaultboolean––
is_providerboolean–Only depots that are (true) or are not (false) providers.
namestring–Wildcard name search.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
sortstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).

No output schema declared.

No examples provided.

synchroteam_list_equipment ~184

List or search pieces of equipment (assets) by name, customer, site, active flag, change time. GET /equipment/list.

NameTypeReqDescription
activeboolean–Active equipment (default true).
changed_sincestring–Only equipment modified after this UTC date-time.
customer_idinteger––
customer_my_idstring––
namestring–Wildcard name search.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
site_idinteger––
site_my_idstring––
sortstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).

No output schema declared.

No examples provided.

synchroteam_list_invoices ~265

List invoices (read only): number, status, customer, job, lines, totals. Filter by status, customer, site, job or time. GET /invoice/list.

NameTypeReqDescription
changed_sincestring–Date-time as yyyy-mm-dd hh:mm:ss (a date alone means midnight). No timezone conversion is applied.
created_sincestring–Date-time as yyyy-mm-dd hh:mm:ss (a date alone means midnight). No timezone conversion is applied.
customer_idinteger––
customer_my_idstring––
job_idinteger––
job_my_idstring––
job_numinteger––
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
paid_sincestring–Date-time as yyyy-mm-dd hh:mm:ss (a date alone means midnight). No timezone conversion is applied.
site_idinteger––
site_my_idstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).
statusstring––

No output schema declared.

No examples provided.

synchroteam_list_job_types ~101

List job types (name, default duration, priority, skills, default report). Use their id or name when creating a job. GET /jobtype/list.

NameTypeReqDescription
namestring–Types whose name contains this.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).

No output schema declared.

No examples provided.

synchroteam_list_jobs ~397

List jobs (simplified: no report, parts or time entries) filtered by status, schedule window, technician, team, customer, site, equipment, job type or project. Use synchroteam_get_job for the full record. GET /job/list.

NameTypeReqDescription
changed_sincestring–Jobs modified on or after this date-time.
created_sincestring–Jobs created on or after this date-time.
customer_idinteger––
customer_my_idstring––
date_fromstring–Jobs planned, ongoing or completed on or after this date-time.
date_tostring–Jobs planned, ongoing or completed on or before this date-time.
equipment_idinteger––
equipment_my_idstring––
has_photosboolean–Only jobs that have (true) or lack (false) photos.
my_idstring–Exact job myId.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
project_idstring–Project id.
showstring–Default active.
site_idinteger––
site_my_idstring––
sortstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).
statusarray–One or more job statuses.
team_idinteger–Jobs of technicians in this team id.
type_idinteger–Job type id.
type_namestring–Job type name.
user_idinteger–Technician user id.
user_loginstring–Technician login.
validated_sincestring–Jobs validated on or after this date-time.

No output schema declared.

No examples provided.

synchroteam_list_part_requests ~189

List technicians' part requests (urgent, sent, completed, deleted flags). GET /partrequest/list.

NameTypeReqDescription
changed_sincestring–Date-time as yyyy-mm-dd hh:mm:ss (a date alone means midnight). No timezone conversion is applied.
created_sincestring–Date-time as yyyy-mm-dd hh:mm:ss (a date alone means midnight). No timezone conversion is applied.
is_completeboolean––
is_deletedboolean––
is_sentboolean––
is_urgentboolean––
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).

No output schema declared.

No examples provided.

synchroteam_list_parts ~190

List the parts and services catalog (reference, name, price, category, tax, tracked/serialized flags, type). GET /part/list.

NameTypeReqDescription
category_idinteger––
category_namestring––
changed_sincestring–Only parts modified after this UTC date-time.
is_serializableboolean––
is_trackedboolean–Only parts tracked (true) or not tracked (false) in inventory.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
sortstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).
statusstring––
typestring––

No output schema declared.

No examples provided.

synchroteam_list_projects ~165

List projects (groups of jobs) by customer, site, equipment or project type. GET /project/list.

NameTypeReqDescription
customer_idinteger––
customer_my_idstring––
equipment_idinteger––
equipment_my_idstring––
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
site_idinteger––
site_my_idstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).
type_idinteger––
type_namestring––

No output schema declared.

No examples provided.

synchroteam_list_quotations ~225

List quotations (read only): number, status, customer, job, lines, totals. GET /quotation/list.

NameTypeReqDescription
changed_sincestring–Date-time as yyyy-mm-dd hh:mm:ss (a date alone means midnight). No timezone conversion is applied.
created_sincestring–Date-time as yyyy-mm-dd hh:mm:ss (a date alone means midnight). No timezone conversion is applied.
customer_idinteger––
customer_my_idstring––
job_idinteger––
job_my_idstring––
job_numinteger––
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
site_idinteger––
site_my_idstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).
statusstring––

No output schema declared.

No examples provided.

synchroteam_list_sites ~179

List or search sites (a customer's locations): by name, customer, active flag, change time. GET /site/list.

NameTypeReqDescription
activeboolean–Active sites (default true).
changed_sincestring–Only sites modified after this UTC date-time.
customer_idinteger–Only sites of this customer id.
customer_my_idstring–Only sites of the customer with this myId.
namestring–Wildcard name search.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
sortstring––
sort_orderstring–Sort order (default ascending; invoices and quotations default to descending).

No output schema declared.

No examples provided.

synchroteam_list_teams ~89

List teams with member counts and tags. GET /team/list.

NameTypeReqDescription
namestring–Teams whose name contains this.
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
showstring––

No output schema declared.

No examples provided.

synchroteam_list_users ~141

List users: login, name, profile (technician, manager, administrator), teams, skills, last known location. Passwords are never returned. GET /user/list.

NameTypeReqDescription
pageinteger–Page number, from 1 (default 1). Pass the previous reply's next_page.
page_sizeinteger–Results per page, 1-100 (default 25).
showstring–Default active.
skilled_tradestring–Only users with this skill.
team_idinteger–Only users of this team id.
team_namestring–Only users of this team name.

No output schema declared.

No examples provided.

synchroteam_schedule_job ~192

WRITE: schedule a job for a technician between two times (also re-schedules a scheduled or paused job). Synchroteam may notify technicians and/or customers (email/SMS/webhook) as configured in the account's notification settings (SMS uses the account's paid credits). Identify the job by exactly one of id, my_id or num. POST /job/schedule.

NameTypeReqDescription
idstring–Job id.
my_idstring–Job myId.
numinteger–Job number.
other_technician_loginsarray–Logins of additional technicians.
scheduled_endstringyesEnd, yyyy-mm-dd hh:mm:ss (after the start).
scheduled_startstringyesStart, yyyy-mm-dd hh:mm:ss.
technicianobjectyesThe technician: exactly one of id or login (synchroteam_list_users).

No output schema declared.

No examples provided.

synchroteam_start_job ~118

WRITE: mark a job as started (status started, actual start now). If the job's technician already has another started job, Synchroteam pauses that one. Starting may trigger the account's 'job started' notifications (email/SMS/webhook to managers, technicians or the customer). Identify the job by exactly one of id, my_id or num. POST /job/start.

NameTypeReqDescription
idstring–Job id.
my_idstring–Job myId.
numinteger–Job number.

No output schema declared.

No examples provided.

synchroteam_update_customer ~176

WRITE: change fields of an existing customer by its numeric id. Only the fields you pass are changed; nothing is cleared. The customer id must exist (an unknown id fails). POST /customer/send.

NameTypeReqDescription
addressstring–Full address on one line (e.g. '6605 Fisher Avenue, Falls Church, VA 22046, United States').
addressComplementstring–Complementary address line (unit, floor...).
contact_emailstring––
contact_faxstring––
contact_first_namestring––
contact_last_namestring––
contact_phonestring––
idintegeryesCustomer id (synchroteam_list_customers).
namestring––
vat_numberstring––

No output schema declared.

No examples provided.

Install

How do I install the Synchroteam MCP by usefulapi server?

Synchroteam MCP by usefulapi is a hosted endpoint at https://synchroteam.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 · synchroteam.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-synchroteam 'https://synchroteam.usefulapi.io/mcp'
Common questions

What is the Synchroteam MCP by usefulapi server?

Synchroteam MCP by usefulapi is listed in the public MCP registry as io.usefulapi/synchroteam. Read Synchroteam jobs, customers, sites, equipment and parts; create, schedule and complete jobs. This page covers its hosted endpoint (https://synchroteam.usefulapi.io/mcp).

Is the Synchroteam MCP by usefulapi server safe to use?

Synchroteam MCP by usefulapi scores 62 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 Synchroteam MCP by usefulapi server expose?

Synchroteam MCP by usefulapi exposes 33 tools: synchroteam_list_customers, synchroteam_get_customer, synchroteam_list_sites, synchroteam_get_site, synchroteam_list_equipment, and 28 more. Their descriptions and schemas cost roughly 4,872 tokens of context every time the server is loaded.

Does the Synchroteam MCP by usefulapi server require authentication?

Yes. Synchroteam 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 Synchroteam MCP by usefulapi server still maintained?

Synchroteam MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.