Home / MCP registry index / io.usefulapi/synchroteam

Synchroteam MCP by usefulapi

io.usefulapi/synchroteam in the official MCP registry. Endpoint https://synchroteam.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read Synchroteam jobs, customers, sites, equipment and parts; create, schedule and complete jobs.

We read its 33 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "synchroteam": {
      "url": "https://synchroteam.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"synchroteam","type":"http","url":"https://synchroteam.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

synchroteam_list_customers synchroteam_get_customer synchroteam_list_sites synchroteam_get_site synchroteam_list_equipment synchroteam_get_equipment synchroteam_list_jobs synchroteam_get_job synchroteam_get_job_photos synchroteam_list_job_types synchroteam_list_users synchroteam_get_user synchroteam_list_teams synchroteam_list_parts synchroteam_get_part synchroteam_list_depots synchroteam_get_depot synchroteam_list_part_requests synchroteam_list_invoices synchroteam_get_invoice synchroteam_list_quotations synchroteam_get_quotation synchroteam_list_contracts synchroteam_list_projects synchroteam_list_activities synchroteam_create_customer synchroteam_update_customer synchroteam_create_site synchroteam_create_equipment synchroteam_create_job synchroteam_schedule_job synchroteam_start_job synchroteam_complete_job

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): 02b3588098e0b7e5. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-synchroteam/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-synchroteam)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.