Ext Ops Panel
Open dashboard
Comparison

Sequential Thinking (Reference) vs VerifiMind PEAS - RefleXion Trinity

Sequential Thinking (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). VerifiMind PEAS - RefleXion Trinity is an MCP server published by creator35lwb-web. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceSequential Thinking (Reference)VerifiMind PEAS - RefleXion Trinity
Docker MCP Catalog Listed
Version: sha256:cd3174b2ecf3
Forks (GitHub): 11 790
Pulls (Docker Hub): 422 092
Stars (Docker Hub): 30
Stars (GitHub): 91 268
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.41.0
Forks (GitHub): 1
Stars (GitHub): 2
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

Sequential Thinking (Reference) vs VerifiMind PEAS - RefleXion Trinity
FactSequential Thinking (Reference)VerifiMind PEAS - RefleXion Trinity
Marketplaces that list it11
Stars (GitHub) (differs)91 268 (better)2 (worse)
Pulls (Docker Hub) (differs)422 092No figure on Docker Hub
Forks (GitHub) (differs)11 790 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sequentialthinking)Remote server (verifimind.ysenseai.org/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/creator35lwb-web/verifimind-peas
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 17 h ago

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

Sequential Thinking (Reference)

In its own words, on Docker MCP Catalog:

Dynamic and reflective problem-solving through thought sequences.

VerifiMind PEAS - RefleXion Trinity

In its own words, on Official MCP Registry:

X-Z-CS AI validation with auditable reasoning. 8 active tools; 5 in maintenance. v0.5.64

How to run each

Sequential Thinking (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio sequentialthinking -- docker run -i --rm mcp/sequentialthinking

VerifiMind PEAS - RefleXion Trinity As a remote MCP server

Claude Code
claude mcp add --transport http verifimind-genesis https://verifimind.ysenseai.org/mcp/

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

Only VerifiMind PEAS - RefleXion Trinity has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of VerifiMind PEAS - RefleXion Trinity publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Sequential Thinking (Reference) · What it can do: VerifiMind PEAS - RefleXion Trinity · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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