MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Code & DevOps

Synchroteam MCP by usefulapi

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

Checks passed
13 / 22

1 failed · 8 not measured

Median response
56 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
33

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 56 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name synchroteam-mcp.

  • Pass
    Lists tools

    tools/list returned 33 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 56 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 56 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    167 of 253 parameters have a description (66%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:33:56.52008Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Synchroteam MCP by usefulapi

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http synchroteam-mcp-by-usefulapi https://synchroteam.usefulapi.io/mcp

Capabilities

Tools 33

synchroteam_complete_job

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.

Discovered
synchroteam_create_customer

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.

Discovered
synchroteam_create_equipment

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.

Discovered
synchroteam_create_job

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.

Discovered
synchroteam_create_site

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.

Discovered
synchroteam_get_customer

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

Discovered
synchroteam_get_depot

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

Discovered
synchroteam_get_equipment

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

Discovered
synchroteam_get_invoice

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

Discovered
synchroteam_get_job

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.

Discovered
synchroteam_get_job_photos

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

Discovered
synchroteam_get_part

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

Discovered
synchroteam_get_quotation

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

Discovered
synchroteam_get_site

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

Discovered
synchroteam_get_user

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

Discovered
synchroteam_list_activities

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.

Discovered
synchroteam_list_contracts

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

Discovered
synchroteam_list_customers

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

Discovered
synchroteam_list_depots

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

Discovered
synchroteam_list_equipment

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

Discovered
synchroteam_list_invoices

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

Discovered
synchroteam_list_job_types

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

Discovered
synchroteam_list_jobs

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.

Discovered
synchroteam_list_part_requests

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

Discovered
synchroteam_list_parts

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

Discovered
synchroteam_list_projects

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

Discovered
synchroteam_list_quotations

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

Discovered
synchroteam_list_sites

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

Discovered
synchroteam_list_teams

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

Discovered
synchroteam_list_users

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

Discovered
synchroteam_schedule_job

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.

Discovered
synchroteam_start_job

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.

Discovered
synchroteam_update_customer

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.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected56 ms33