Ext Ops Panel
Open dashboard
Comparison

Enoch vs ssh-mcp-pro

Enoch is an MCP server published by alias8818. 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-23. 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
MarketplaceEnochssh-mcp-pro
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (PyPI): 68
Downloads/week (PyPI): 22
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

Enoch vs ssh-mcp-pro
FactEnochssh-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)On your machine (enoch-mcp)On your machine (ssh-mcp-pro)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 14, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/alias8818/enoch-mcpgithub.com/oaslananka/ssh-mcp-pro
Changes in the last 7 days00
First seen2026-10-112026-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

Enoch

In its own words, on Official MCP Registry:

Operate an Enoch control plane through MCP tools

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

Enoch As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ENOCH_API_TOKEN=<YOUR_ENOCH_API_TOKEN>" --transport stdio enoch -- uvx enoch-mcp

Requires: ENOCH_API_TOKEN (secret)

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.

Tools each declares

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

Settings each asks for

Only Enoch asks for

  • ENOCH_API_TOKEN (secret)
  • ENOCH_API_URL

Only ssh-mcp-pro asks for

  • SSH_MCP_HTTP_ALLOWED_ORIGINS
  • SSH_MCP_HTTP_BEARER_TOKEN_FILE (secret)
  • SSH_MCP_HTTP_PUBLIC_URL
  • SSH_MCP_HTTP_TRUST_PROXY

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Enoch · 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