Ext Ops Panel
Open dashboard
Comparison

io.github.michal-lefler/secure-flows vs ssh-mcp-pro

io.github.michal-lefler/secure-flows is an MCP server published by michal-lefler. Marketplaces we read that list it: 1 (Official MCP Registry). ssh-mcp-pro is an MCP server published by oaslananka. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceio.github.michal-lefler/secure-flowsssh-mcp-pro
Official MCP Registry Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.2.3
Downloads/month (npm): 666
Downloads/week (npm): 474
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

io.github.michal-lefler/secure-flows vs ssh-mcp-pro
Factio.github.michal-lefler/secure-flowsssh-mcp-pro
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.secure-flows.com/mcp)On your machine (ssh-mcp-pro)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/michal-lefler/secure-flowsgithub.com/oaslananka/ssh-mcp-pro
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

io.github.michal-lefler/secure-flows

In its own words, on Official MCP Registry:

MCP server for secureFlows (secure-flows.com). Alias of io.github.michal-lefler/secureflows-mcp.

ssh-mcp-pro

In its own words, on Official MCP Registry:

Secure MCP SSH automation server with policy controls, resources, prompts, stdio, and HTTP.

How to run each

io.github.michal-lefler/secure-flows

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

ssh-mcp-pro As a local MCP server: npm package

Claude Code
claude mcp add --env "SSH_MCP_HTTP_BEARER_TOKEN_FILE=<YOUR_SSH_MCP_HTTP_BEARER_TOKEN_FILE>" --transport stdio ssh-mcp-pro -- npx -y ssh-mcp-pro

Requires: SSH_MCP_HTTP_BEARER_TOKEN_FILE (secret)

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

Only io.github.michal-lefler/secure-flows 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

The marketplaces of io.github.michal-lefler/secure-flows publish no settings it asks for, so we do not compare settings.

What it can do: io.github.michal-lefler/secure-flows · What it can do: ssh-mcp-pro · 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