instant-site vs Dplooy
instant-site is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.
instant-site is a plugin bundle for AI coding tools published by Yi Hao. No marketplace we read lists it any more. Dplooy is an MCP server published by dplooy.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace haoyiyin/instant-site | Removed on 2026-10-23 Version: 0.1.1 Forks (GitHub): 2 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.15.0 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
| Fact | instant-siteno longer listed · | Dplooy |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.dplooy.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/haoyiyin/instant-site | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 42 h ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of instant-site
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
yetty ai.yetty/yetty
Build, edit and run real hosted websites from your AI - content, SEO, menus, store, rollback.
-
Build, publish, and grow SEO-ready websites just by chatting with your AI assistant.
-
Deploy static sites to ShipStatic from Claude Code. Upload files and directories, manage deployments with instant rollbacks, configure custom domains with DNS verification - all…
-
Deploys static sites to a live HTTPS URL via the Cybrix hosting service. Automatically detects Next.js export, Astro, Vite, Hugo, Eleventy, and plain HTML. Returns a live URL on…
-
sitectrl ai.sitectrl/sitectrl
Your AI builds real hosted websites: describe it, get a live site with SSL, forms, analytics. Free.
-
Instant Business Website Builder & Next.js Generator
The easiest way to build, preview, and launch a live business website in 60 seconds ($0 setup).
What each says it does
instant-site
Build, deploy, update, and SEO-optimize static foreign trade independent sites using HTML/CSS/JS, DESIGN.md templates, Cloudflare Pages (Wrangler), and scheduled agent operations
Dplooy
Publish a complete website to a live URL from your AI assistant: forms, bookings, content, chatbot
How to run each
instant-site
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Dplooy As a remote MCP server
claude mcp add --transport http hosting https://api.dplooy.com/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Dplooy 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: instant-site · What it can do: Dplooy · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.