Ext Ops Panel
Open dashboard
Comparison

Render vs Perceptdot Vercel

Render is an MCP server published by render-oss. Marketplaces we read that list it: 1 (Docker MCP Catalog). Perceptdot Vercel is an MCP server published by perceptdot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceRenderPerceptdot Vercel
Docker MCP Catalog Listed
Version: sha256:96ee41e6433a
Forks (GitHub): 96
Pulls (Docker Hub): 15 856
Stars (Docker Hub): 1
Stars (GitHub): 179
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.6
No figure published
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 Perceptdot Vercel
FactRenderPerceptdot Vercel
Marketplaces that list it11
Stars (GitHub) (differs)179No figure on GitHub
Pulls (Docker Hub) (differs)15 856No figure on Docker Hub
Forks (GitHub) (differs)96No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/render)On your machine (@perceptdot/vercel)
Transportstdiostdio
Tools it declares (differs)24Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/render-oss/render-mcp-serverNot stated
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.

Perceptdot Vercel

In its own words, on Official MCP Registry:

AI agent vision for Vercel deployments — with ROI measurement. perceptdot.com

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)

Perceptdot Vercel As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio vercel -- npx -y @perceptdot/vercel

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

Tools each declares

The marketplaces of Perceptdot Vercel publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Perceptdot Vercel publish no settings it asks for, so we do not compare settings.

What it can do: Render · What it can do: Perceptdot Vercel · 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