Home / MCP registry index / io.github.themewireco/synchronity
Synchronity
io.github.themewireco/synchronity in the official MCP registry.
Endpoint https://api.synchronity.app/mcp. Source: github.com/themewireco/synchronity.
The registry describes it as: Shop connected e-commerce stores: search, compare, cart, and checkout with buyer approval.
We read its 26 tools on 2026-10-22. 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.
Tools it advertises
list_sites search_products get_product get_product_reviews request_back_in_stock compare_products create_cart add_to_cart quick_checkout remove_from_cart set_cart_quantity apply_coupon get_cart get_active_cart set_shipping_address select_shipping_option execute_checkout get_order list_orders request_delegation submit_delegation_otp check_delegation get_payment_methods initiate_payment submit_payment_otp get_payment_status
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-themewireco-synchronity)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.