shiply

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as now.shiply/shiply and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 28 Jul 2026. Not supplied by the maker.

• publish_site

  Publish files to the web → live URL at <slug>.shiply.now. UPDATING: never create a new site for changes — re-call with claimToken (anonymous sites) or slug (sites you own with a Bearer key) and the SA

• site_status

  Check any shiply slug or custom hostname: TLS certificate (issuer, days left) + HTTPS probe. ready=true means live.

• verify_site

  Edge-check a shiply slug or custom hostname and return a structured readiness report: status (LIVE/PENDING), SSL details (valid, issuer, daysLeft), HTTP probe, and a presigned thumbnail URL when avail

• list_sites

  List the sites owned by this API key. Optional clientId filters to one client.

• get_site

  Site settings + version history for one of my sites.

• delete_site

  PERMANENTLY delete a site and all stored files. Irreversible — confirm with the user first.

• rollback_site

  Re-point a site to any finalized version (rollback or roll-forward). Get version ids from get_site. Serving updates immediately.

• list_versions

  List a site's finalized deploys newest-first (id, createdAt, isLive, fileCount, bytes), capped at 20. Pair with rollback_site: pick a version id from here and re-point the site to it.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.