Ext Ops Panel
Open dashboard
Comparison

ai.packmind/mcp-server vs io.github.aktonay/snapdec

ai.packmind/mcp-server is an MCP server published by packmind.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.aktonay/snapdec is an MCP server published by aktonay. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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

Where each is published
Marketplaceai.packmind/mcp-serverio.github.aktonay/snapdec
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 22
Stars (GitHub): 319
Not marked · First seen
Listed
Version: 0.6.0
Downloads/month (PyPI): 636
Downloads/week (PyPI): 115
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

ai.packmind/mcp-server vs io.github.aktonay/snapdec
Factai.packmind/mcp-serverio.github.aktonay/snapdec
Marketplaces that list it11
Stars (GitHub) (differs)319No figure on GitHub
Forks (GitHub) (differs)22No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app.packmind.ai/mcp)On your machine (snapdec)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/packmindhub/packmindNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agono remote endpoint we check

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

ai.packmind/mcp-server

In its own words, on Official MCP Registry:

Packmind captures, scales, and enforces your organization's technical decisions.

io.github.aktonay/snapdec

In its own words, on Official MCP Registry:

Snap decisions for coding agents: local or hosted classify/check/score/rank via MCP.

How to run each

ai.packmind/mcp-server As a remote MCP server

Claude Code
claude mcp add --transport http ai-packmind-mcp-server https://app.packmind.ai/mcp

io.github.aktonay/snapdec As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio snapdec -- uvx snapdec

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ai.packmind/mcp-server has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: ai.packmind/mcp-server · What it can do: io.github.aktonay/snapdec · 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.

Where the data comes from: how the catalog is built