io.github.statwonk/decern vs xaffinity MCP
io.github.statwonk/decern is an MCP server published by statwonk. Marketplaces we read that list it: 1 (Official MCP Registry). xaffinity MCP is an MCP server published by yaniv-golan. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Downloads/month (PyPI): 102 Downloads/week (PyPI): 34 Not marked · First seen |
Listed Version: 1.22.0 Forks (GitHub): 1 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 | io.github.statwonk/decern | xaffinity MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (decern-mcp) | On your machine (https://github.com/yaniv-golan/affinity-sdk/releases/download/mcp-v1.22.0/xaffinity-mcp-1.22.0.mcpb) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/statwonk/decern | github.com/yaniv-golan/affinity-sdk |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
io.github.statwonk/decern
MCP server for Decern CRM — contacts, deals, pipelines, tasks, and approvals.
xaffinity MCP
MCP server for Affinity CRM - entity search, relationship intelligence, and workflow management
How to run each
io.github.statwonk/decern As a local MCP server: PyPI package
claude mcp add --env "DECERN_API_KEY=<YOUR_DECERN_API_KEY>" --transport stdio decern -- uvx decern-mcp
Requires: DECERN_API_KEY (secret)
xaffinity MCP
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: AFFINITY_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only io.github.statwonk/decern asks for
DECERN_API_KEY (secret)
Only xaffinity MCP asks for
AFFINITY_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.statwonk/decern · What it can do: xaffinity MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.