Should my agent depend on the MCP server io.github.themewireco/synchronity?

Verdict: allow — mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Synchronity

io.github.themewireco/synchronity

Shop connected e-commerce stores: search, compare, cart, and checkout with buyer approval.

— the operator's own registry description reported

Publisher io.github.themewireco · first seen 2026-08-12 · endpoint https://api.synchronity.app/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.249 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency266 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools26

vs populationmid

capabilities2

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_8b379b21037f076425fe5c35 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

add_to_cart apply_coupon check_delegation compare_products create_cart execute_checkout get_active_cart get_cart get_order get_payment_methods get_payment_status get_product get_product_reviews initiate_payment list_orders list_sites quick_checkout remove_from_cart request_back_in_stock request_delegation search_products select_shipping_option set_cart_quantity set_shipping_address submit_delegation_otp submit_payment_otp

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	26/26	✓
has a description	26/26	✓
description is substantive	26/26	✓
parameters are typed	26/26	✓
parameters are described	26/26	✓

26 of 26 tools graded · 26 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.2.0

server version synchronity-mcp

Capabilities: resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:15Z	ok_tools	200	266	2025-06-18
2026-08-12T05:35:27Z	ok_tools	200	252	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.themewireco/synchronity.svg)](https://robinsaige.com/s/io.github.themewireco/synchronity)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview