Ext Ops Panel
Open dashboard
Comparison

io.github.CloudCorpRecords/deployport vs io.github.nometria/deploy

io.github.CloudCorpRecords/deployport is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.nometria/deploy is an MCP server published by nometria. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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.CloudCorpRecords/deployportio.github.nometria/deploy
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.0
Downloads/month (npm): 285
Downloads/week (npm): 116
Forks (GitHub): 0
Stars (GitHub): 3
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.CloudCorpRecords/deployport vs io.github.nometria/deploy
Factio.github.CloudCorpRecords/deployportio.github.nometria/deploy
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@reneturcios/deployport)On your machine (@nometria-ai/claude-code)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/cloudcorprecords/deployportgithub.com/nometria/claude-code-plugin
Changes in the last 7 days00
First seen (differs)2026-11-022026-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

io.github.CloudCorpRecords/deployport

In its own words, on Official MCP Registry:

Vercel projects, deployments, domains and env vars as MCP tools.

io.github.nometria/deploy

In its own words, on Official MCP Registry:

Deploy any app to any cloud. 20 tools for deployments, previews, and management.

How to run each

io.github.CloudCorpRecords/deployport As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio deployport -- npx -y @reneturcios/deployport mcp

io.github.nometria/deploy As a local MCP server: npm package

Claude Code
claude mcp add --env "NOMETRIA_API_KEY=<YOUR_NOMETRIA_API_KEY>" --transport stdio deploy -- npx -y @nometria-ai/claude-code

Requires: NOMETRIA_API_KEY (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

The marketplaces of io.github.CloudCorpRecords/deployport publish no settings it asks for, so we do not compare settings.

What it can do: io.github.CloudCorpRecords/deployport · What it can do: io.github.nometria/deploy · 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