SyncSo vs Ny Omig Exclusions
SyncSo is an MCP server published by syncso.com. Marketplaces we read that list it: 1 (Official MCP Registry). Ny Omig Exclusions is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  SyncSo |  Ny Omig Exclusions |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | SyncSo | Ny Omig Exclusions |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | Remote server (rtdb.syncso.com/partner/mcp) | Remote server (gateway.pipeworx.io/ny-omig-exclusions/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/syncso-inc/syncso | github.com/pipeworx-io/mcp-ny-omig-exclusions |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 405 | Status out of date: last check 3 days ago returned HTTP 200 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
SyncSo
Live New York events, shows, classes, tours, markets, music, theater, comedy, art and nightlife
Ny Omig Exclusions
New York State OMIG Medicaid provider exclusion screening — fleet #2788.
How to run each
SyncSo As a remote MCP server
claude mcp add --transport http syncso https://rtdb.syncso.com/partner/mcpNy Omig Exclusions As a remote MCP server
claude mcp add --transport http ny-omig-exclusions https://gateway.pipeworx.io/ny-omig-exclusions/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of SyncSo nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of SyncSo publish no settings it asks for, so we do not compare settings.
What it can do: SyncSo · What it can do: Ny Omig Exclusions · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.