Ext Ops Panel
Open dashboard
Comparison

Render vs io.github.FlayedOne/plesk-mcp

Render is an MCP server published by render-oss. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.FlayedOne/plesk-mcp is an MCP server published by FlayedOne. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceRenderio.github.FlayedOne/plesk-mcp
Docker MCP Catalog Listed
Version: sha256:96ee41e6433a
Forks (GitHub): 97
Pulls (Docker Hub): 15 881
Stars (Docker Hub): 1
Stars (GitHub): 179
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
Forks (GitHub): 1
Stars (GitHub): 6
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

Render vs io.github.FlayedOne/plesk-mcp
FactRenderio.github.FlayedOne/plesk-mcp
Marketplaces that list it11
Stars (GitHub) (differs)179 (better)6 (worse)
Pulls (Docker Hub) (differs)15 881No figure on Docker Hub
Forks (GitHub) (differs)97 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/render)On your machine (plesk-mcp)
Transportstdiostdio
Tools it declares (differs)24Not published
Environment variables it asks for (differs)1, secrets among them: 14, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/render-oss/render-mcp-servergithub.com/flayedone/plesk-mcp
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

Render

In its own words, on Docker MCP Catalog:

Interact with your Render resources via LLMs.

io.github.FlayedOne/plesk-mcp

In its own words, on Official MCP Registry:

Manage your Plesk hosting server using AI assistants.

How to run each

Render As a local MCP server: Docker image

Claude Code
claude mcp add --env "RENDER_API_KEY=<YOUR_RENDER_API_KEY>" --transport stdio render -- docker run -i --rm -e RENDER_API_KEY mcp/render

Requires: RENDER_API_KEY (secret)

io.github.FlayedOne/plesk-mcp As a local MCP server: PyPI package

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

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

Tools each declares

The marketplaces of io.github.FlayedOne/plesk-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

Only Render asks for

  • RENDER_API_KEY (secret)

Only io.github.FlayedOne/plesk-mcp asks for

  • PLESK_API_KEY
  • PLESK_HOST
  • PLESK_PASSWORD
  • PLESK_USERNAME

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

What it can do: Render · What it can do: io.github.FlayedOne/plesk-mcp · 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