Build & Ship vs io.github.CloudCorpRecords/sitehost-port
Build & Ship is an MCP server published by buildandship.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.CloudCorpRecords/sitehost-port is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
| Marketplace |  Build & Ship |  io.github.CloudCorpRecords/sitehost-port |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 No figure published Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | Build & Ship | io.github.CloudCorpRecords/sitehost-port |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.buildandship.ai/mcp) | On your machine (@reneturcios/sitehost-port) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/cloudcorprecords/sitehost-port |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-11-02 |
| Endpoint at the last check (differs) | Status out of date: last check 32 h ago returned HTTP 401 | no 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
Build & Ship
Prompt your Build & Ship agent to create web pages and publish them to your CDN, Git or API.
io.github.CloudCorpRecords/sitehost-port
Netlify sites, deploys and builds as MCP tools.
How to run each
Build & Ship As a remote MCP server
claude mcp add --transport http agent https://api.buildandship.ai/mcpio.github.CloudCorpRecords/sitehost-port As a local MCP server: npm package
claude mcp add --transport stdio sitehost-port -- npx -y @reneturcios/sitehost-port mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Build & Ship 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Build & Ship · What it can do: io.github.CloudCorpRecords/sitehost-port · 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.