now.shiply/shiply

REMOTE · SHIPLY.NOW · SCANNED AUG 3

Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price.

Available components

+8 this week 82 82 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security94

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Tool/resource definitions use about 9168 tokens (~78/item across 117 items; 114 tools + 3 resources), lean.Pass
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
99% of tool parameters carry a description.Partial
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · shiply.now

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http now-shiply-shiply https://shiply.now/mcp

# ~/.codex/config.toml

[mcp_servers.now-shiply-shiply]
url = "https://shiply.now/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "now-shiply-shiply": {
      "type": "remote",
      "url": "https://shiply.now/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add now-shiply-shiply --url https://shiply.now/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  now-shiply-shiply:
    url: "https://shiply.now/mcp"

// mcp.json

{
  "mcpServers": {
    "now-shiply-shiply": {
      "type": "http",
      "url": "https://shiply.now/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 74

First indexed and scored.

Show 6 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://shiply.now/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=shiply.now	CN=WE1,O=Google Trust Services,C=US	11 Jun 2026	9 Sept 2026	ECDSA 256	ECDSA-SHA256	c2577c70f60d0a4113fa4d399ec10b5a
SANs: shiply.now, *.shiply.now
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC insecure

Validation of shiply.now. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
now.	present	53572	8	Verified
shiply.now.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result	Enforced and verified
Enforced	On tool calls
HTTP status	200

WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://shiply.now/.well-known/oauth-protected-resource"

Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://shiply.now/.well-known/oauth-protected-resource"

Header	Value
strict-transport-security	max-age=63072000; includeSubDomains; preload
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	strict-origin-when-cross-origin
permissions-policy	camera=(), microphone=(), geolocation=(), payment=(), usb=()

Protected resource metadata

Document	https://shiply.now/.well-known/oauth-protected-resource
Retrieved	Yes
Resource	https://shiply.now/mcp
Authorisation server	https://shiply.now

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://shiply.now/mcp	Verified	200
http (plaintext)	http://shiply.now/mcp	HTTPS enforced	301	https://shiply.now/mcp

MCP tools — 114 exposed · ~9,102 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

set_profile Set up a public profile ~190

Create or update the user's public PORTFOLIO page at shiply.now/@<handle> (handle 3-30 chars a-z0-9-) — a landing page listing the user's sites. This is NOT a site's address: to give one site a vanity URL like <handle>.shiply.now, use set_handle instead. enable shows the profile; autoAdd auto-lists new sites. Use after publishing to give the user a shareable portfolio.

Input Output Examples

Name	Type	Req	Description
autoAdd	boolean	—	auto-list newly published sites on the profile
enable	boolean	—	show (true) or hide (false) the public profile
handle	string	—	public portfolio handle, 3-30 chars a-z 0-9 -; portfolio lives at shiply.now/@<handle> (a page listing your sites — not a site URL; for a site vanity URL use set_handle)

Name	Type	Req	Description
result	—	yes	—

No examples provided.

set_secret Set a Worker secret on a site ~101

Set a CF Worker secret on a site's deployed function. Value is encrypted-at-rest and accessible as env.<NAME> inside the worker. Use for Stripe keys, Resend API keys, etc.

Input Output Examples

Name	Type	Req	Description
name	string	yes	secret name, UPPER_SNAKE_CASE; available as env.<NAME>
slug	string	yes	site slug whose function gets the secret
value	string	yes	secret value (encrypted at rest), ≤8 KiB

Name	Type	Req	Description
result	—	yes	—

No examples provided.

set_site_access Set site access control ~142

Protect an owned site (paid plans). mode 'public' (anyone), 'password' (supply password), or 'restricted' (supply allowedEmails and/or allowedDomains — only those can request a login code). Changing any setting signs out existing visitors.

Input Output Examples

Name	Type	Req	Description
allowedDomains	array	—	allowlisted email domains when mode='restricted'
allowedEmails	array	—	allowlisted emails when mode='restricted'
mode	string	yes	public = anyone; password = supply password; restricted = supply allowedEmails/allowedDomains
password	string	—	required when mode='password'
slug	string	yes	owned site slug to protect

Name	Type	Req	Description
result	—	yes	—

No examples provided.

set_variable Save an encrypted variable ~127

Upsert a key/value in the user's encrypted variable store (UPPER_SNAKE name, ≤8 KiB value). Use for API keys the user's sites/agents need, e.g. SUPABASE_URL. NOTE: saving alone does NOT expose it to any site Worker's env — attach it to a specific site with attach_variable (takes effect on that site's next function deploy).

Input Output Examples

Name	Type	Req	Description
name	string	yes	variable name, UPPER_SNAKE_CASE, e.g. SUPABASE_URL
value	string	yes	value to store (encrypted, ≤8 KiB)

Name	Type	Req	Description
result	—	yes	—

No examples provided.

site_status SSL + readiness check ~52

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

Input Output Examples

Name	Type	Req	Description
target	string	yes	slug (my-site) or hostname (www.example.com)

Name	Type	Req	Description
result	—	yes	—

No examples provided.

summarize_thread AI-summarize an inbox thread ~45

One-paragraph summary of the thread, oriented to the most actionable signal (interest, complaint, question, unsubscribe).

Input Output Examples

Name	Type	Req	Description
threadId	string	yes	thread id from list_inbox

Name	Type	Req	Description
result	—	yes	—

No examples provided.

sync_dns Sync DNS records ~63

For a connected custom domain, (re)write the CNAME records for all its subdomains automatically and report what changed. For unconnected domains, returns the records to add manually.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	registered custom domain to sync, e.g. example.com

Name	Type	Req	Description
result	—	yes	—

No examples provided.

unarchive_thread Unarchive a thread ~58

Restore an archived thread (clears archivedAt). It reappears in the default inbox list. Pair with list_inbox filter=archived to find archived threadIds first.

Input Output Examples

Name	Type	Req	Description
threadId	string	yes	archived thread id to restore

Name	Type	Req	Description
result	—	yes	—

No examples provided.

update_brief Patch the project brief ~87

Overwrite the project's working brief (jsonb). Hard-capped at 500 KB. Use to revise the AI-generated brief by hand; the original AI output is preserved separately in briefAiOriginal so you can always compare. Does not change status.

Input Output Examples

Name	Type	Req	Description
brief	object	yes	the full replacement brief object (jsonb, ≤500 KB)
id	string	yes	project id

Name	Type	Req	Description
result	—	yes	—

No examples provided.

update_listing Update one of my listings ~160

Patch a listing by siteSlug — change price, pitch, terms, jurisdiction, or status (draft|live|paused). Sold listings cannot be edited. Status transitions enforced server-side. Use to pause sales or drop the price.

Input Output Examples

Name	Type	Req	Description
jurisdiction	string	—	governing jurisdiction, e.g. 'California, USA'
pitch	—	—	new sales pitch (null to clear)
priceCents	integer	—	new whole-dollar price in cents, 100–999900
siteSlug	string	yes	slug of the listed site to patch
status	string	—	new listing status
termsCustom	—	—	new custom terms text (null to clear)
termsMode	string	—	'standard' template or 'custom' terms

Name	Type	Req	Description
result	—	yes	—

No examples provided.

verify_claim Verify a Shiply claim pairing code ~113

Confirm a pairing code shown in the user's browser at https://shiply.now/claim/<slug>?pair=1. Use ONLY in the agent session that originally published the site — it reads the claimToken from .shiply.json in the current working directory and proves to Shiply that this agent session is authorised to claim the site. After verification the user is auto-redirected to /welcome and the site binds to their account.

Input Output Examples

Name	Type	Req	Description
code	string	yes	the SHIPLY-XXXXXXXX code in the user's browser

Name	Type	Req	Description
result	—	yes	—

No examples provided.

verify_sending_domain Re-check DNS for a sending domain ~72

Trigger Resend to re-check the domain's DNS records, persist the new status. Call after adding the DNS records returned by add_sending_domain. Status flips to 'verified' once SPF + DKIM + MX all check out.

Input Output Examples

Name	Type	Req	Description
id	string	yes	sending domain id from list_sending_domains

Name	Type	Req	Description
result	—	yes	—

No examples provided.

verify_site Verify a live deploy ~81

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 available. Use this after publishing to confirm the site is reachable.

Input Output Examples

Name	Type	Req	Description
target	string	yes	slug (my-site) or hostname (www.example.com)

Name	Type	Req	Description
result	—	yes	—

No examples provided.

whoami Account overview ~51

Who am I? Returns the signed-in account: email, @handle, plan + limits, counts of sites/domains/drives, and connected DNS providers. Call this first to orient before managing sites or domains.

Input Output Examples

Input schema present but exposes no named parameters.

Name	Type	Req	Description
result	—	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	74
27 Jul	74
28 Jul	75
29 Jul	76
30 Jul	75
31 Jul	81
1 Aug	81
2 Aug	81
3 Aug	82