SORNKan Publish
REMOTE · PUBLISH.SORNKAN.COM
Host a static website from a zip: $1 USDC/month via x402 on Base, or card/PromptPay link.
Available components
Last scanned (8 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
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 → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1834 tokens (~183/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_website" implies "publish" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 21 Oct 26 +11
- Authorization: unverified → partial ▲ security
- Tool “claim” rewrote its description, which is the text the model reads security
- Tool “publish_website” rewrote its description, which is the text the model reads security
- Schema quality: 157 → 183 ▼ functional
- Destructive annotations: 0% → 50% ▲ functional
- Tool coverage: 33% → 100% ▲ functional
- Schema quality: good → excellent functional
- “claim” reworded the description of “email” cosmetic
- “claim” reworded the description of “slug” cosmetic
- “claim” reworded the description of “uploadId” cosmetic
- “connect_custom_hostname” reworded the description of “hostname” cosmetic
- “connect_custom_hostname” reworded the description of “slug” cosmetic
- “edit” reworded the description of “slug” cosmetic
- “edit” reworded the description of “tokens” cosmetic
- “edit” reworded the description of “uploadId” cosmetic
- “inspect” reworded the description of “uploadId” cosmetic
- “preview_status” reworded the description of “uploadId” cosmetic
- “renew” reworded the description of “slug” cosmetic
- “scan” reworded the description of “uploadId” cosmetic
- 16 Oct 26 0
- Tool “connect_custom_hostname” rewrote its description, which is the text the model reads security
- Tool “edit” rewrote its description, which is the text the model reads security
- Tool “renew” rewrote its description, which is the text the model reads security
- Schema quality: 134 → 157 ▼ functional
- Tool coverage: 13% → 33% ▲ functional
- “claim” added an optional parameter “editToken” cosmetic
- “connect_custom_hostname” added an optional parameter “editToken” cosmetic
- “edit” added an optional parameter “editToken” cosmetic
- “renew” added an optional parameter “editToken” cosmetic
- “edit” dropped the optional parameter “ownerWallet” cosmetic
- 28 Sept 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
- 25 Sept 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
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 28 Aug 26 0
- Tool “render_page” rewrote its description, which is the text the model reads security
- “render_page” reworded the description of “fullPage” cosmetic
- 27 Aug 26 0
- Tool coverage: 0% → 13% ▲ functional
- New tool “render_page” functional
- 26 Aug 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
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 5 Nov 2026 · Probed https://publish.sornkan.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sornkan.com | CN=WE1,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c40a0814761717b0e59c08366f3b959 |
| SANs: sornkan.com, publish.sornkan.com, *.publish.sornkan.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of publish.sornkan.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sornkan.com. | present | 2371 | 13 | Verified |
| publish.sornkan.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://publish.sornkan.com/mcp | Verified | 200 | |
| http (plaintext) | http://publish.sornkan.com/mcp | HTTPS enforced | 301 | https://publish.sornkan.com/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
claim ~347
Claim (activate) an inspected preview as a live site at {slug}.worldsite.workers.dev. This is the paid go-live step ($1 USDC first 30 days); publish_website only returns the plan and never goes live by itself. Call preview_status first — if claimable is false, do not pay. Ask which slug they want before paying. Live URL is {slug}.worldsite.workers.dev — not {slug}.workers.dev. Pretty names: CNAME their domain after claim. uploadId MUST be the UUID from inspect (not previewUrl). If you only have https://publish.sornkan.com/preview/<uuid>, pass that UUID. If you have no wallet, get payment_url from the 402 response and show it to the human — they pay by card or Thai PromptPay in THB (no crypto needed); after they pay, poll preview_status/retry until live. If the last claim returned PRICE_COMPUTE_FAILED, retry this tool — no USDC was taken. If a signed payment failed settlement, tell the human contact@sornkan.com and do not retry payment.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | – | Edit token of a site paid by card/PromptPay (shown once at claim and emailed to the payer). Required to edit/renew/connect a domain on such a site. |
| string | – | Receipt email for card/PromptPay payers (optional) | |
| slug | string | – | Lowercase site name to claim; live URL is {slug}.worldsite.workers.dev (ask the human first) |
| uploadId | string | yes | UUID from inspect — the part after /preview/, never the full preview URL |
No output schema declared.
No examples provided.
connect_custom_hostname ~258
Connect an existing hostname via CNAME to sites.sornkan.com (no registrar). One-time $1 USDC, same claiming wallet (or editToken for a card-paid site), while lease is live. If the bind is refused after a card payment, the payment stays as a credit: retry with HTTP POST https://publish.sornkan.com/custom-hostname {slug, hostname} plus header X-Edit-Token — no new payment. If the hostname is already on Cloudflare, keep the CNAME proxied. Not a monthly fee. If you have no wallet, get payment_url from the 402 response and show it to the human — they pay by card or Thai PromptPay in THB (no crypto needed); after they pay, poll preview_status/retry until live.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | – | Edit token of a site paid by card/PromptPay (shown once at claim and emailed to the payer). Required to edit/renew/connect a domain on such a site. |
| hostname | string | yes | Your own domain to point at the site (e.g. www.example.com); CNAME it to sites.sornkan.com |
| slug | string | yes | Live site slug to attach the hostname to |
No output schema declared.
No examples provided.
edit ~240
Check the zip for unsafe files, then redeploy the live Worker. Flat $0.50 per edit on every rail (x402 wallet or card/PromptPay payment_url). Does not extend lease days. Ownership: a site claimed with a wallet must be edited by paying from that same wallet; a site paid by card/PromptPay needs its editToken (shown once at claim and emailed to the payer). If you have no wallet, get payment_url from the 402 response and show it to the human — they pay by card or Thai PromptPay in THB (no crypto needed); after they pay, poll preview_status/retry until live.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | – | Edit token of a site paid by card/PromptPay (shown once at claim and emailed to the payer). Required to edit/renew/connect a domain on such a site. |
| slug | string | yes | Live site slug to redeploy |
| tokens | number | – | Approximate token size of the change (optional, informational — edits are flat $0.50) |
| uploadId | string | yes | UUID of the new zip to deploy (call upload_url first) |
No output schema declared.
No examples provided.
inspect ~216
Deploys a throwaway preview Worker at preview-*.worldsite.workers.dev (not publish.sornkan.com) after scanning the zip. This is the DEPLOY step — it counts against the free preview quota (first 3/day, then $0.10). The 4th+ can be paid two ways: sign the x402 retry with USDC on Base, or show the 402’s payment_url to the human (card / Thai PromptPay, same $0.10). Use scan (free, nothing deployed) while iterating on the zip; call inspect only when the human wants to see a preview. Do NOT inspect again just to read remaining time — use preview_status. If claimable is false, upload_url again; do not pay for that old id. Successful claim resets the free preview quota. After the human approves, ask which slug they want, then claim with the UUID and slug.
| Name | Type | Req | Description |
|---|---|---|---|
| uploadId | string | yes | UUID of the uploaded zip to deploy as a preview, from upload_url |
No output schema declared.
No examples provided.
preview_status ~115
Read remaining preview time. uploadId is the UUID (a preview URL is OK). Does not scan, does not reset the clock, never 402. If claimable is false, the preview was deleted — call upload_url, PUT a new zip, inspect, then claim. Do not inspect or claim the old id. Do not pay. Use this instead of inspect when you only need the clock.
| Name | Type | Req | Description |
|---|---|---|---|
| uploadId | string | yes | Preview UUID to check — the part after /preview/ if you only have a preview URL |
No output schema declared.
No examples provided.
publish_website ~207
START HERE: get the step-by-step website publishing plan. This tool only returns instructions — it never uploads, deploys, or goes live by itself; follow the plan with upload_url → scan → inspect → claim. ALWAYS ask the human first: go live for $1 USDC first 30 days? content legal? Then: upload_url → PUT putUrl (else give dropUrl) → inspect → show previewUrl → preview_status to read remaining time (never inspect again just for the clock) → ask which slug they want → claim with the UUID from inspect plus slug, never the preview URL. Live URL is {slug}.worldsite.workers.dev — not {slug}.workers.dev. Pretty names: CNAME their domain after claim. If claim returned PRICE_COMPUTE_FAILED, retry claim — no USDC was taken. Only if a signed payment failed settlement, tell the human contact@sornkan.com and do not retry payment. Never put the zip in chat.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
render_page ~101
Render any public URL in a real browser (Chromium). Returns markdown text, a screenshot URL, and a human-checkable evidence page URL. $0.005 per call. No signup, no API key. x402 wallet required. Pass fullPage:true for the entire scrollable page (same price).
| Name | Type | Req | Description |
|---|---|---|---|
| fullPage | boolean | – | Capture entire scrollable page (same $0.005) |
| url | string | yes | Public https URL to render |
No output schema declared.
No examples provided.
renew ~204
Renew hosting +30 days for $1 USDC. Same claiming wallet (or editToken for a card-paid site). Allowed only while the site is live and remaining < 90 days (stacked cap 90). After expiry renew is unavailable — claim again as a new site; last day without renew means the site is deleted and the slug is free. Support: contact@sornkan.com. If you have no wallet, get payment_url from the 402 response and show it to the human — they pay by card or Thai PromptPay in THB (no crypto needed); after they pay, poll preview_status/retry until live.
| Name | Type | Req | Description |
|---|---|---|---|
| editToken | string | – | Edit token of a site paid by card/PromptPay (shown once at claim and emailed to the payer). Required to edit/renew/connect a domain on such a site. |
| slug | string | yes | Live site slug to renew — the {slug} in {slug}.worldsite.workers.dev |
No output schema declared.
No examples provided.
scan ~102
Check an uploaded zip for unsafe files WITHOUT deploying anything. Free, never 402, burns no preview quota — use this while iterating on the zip (scan → fix → upload_url again → scan). When the content is clean and the human wants to SEE it, call inspect to deploy a throwaway preview Worker. Verdict here is advisory: inspect re-checks before deploying.
| Name | Type | Req | Description |
|---|---|---|---|
| uploadId | string | yes | UUID of the uploaded zip to check, from upload_url |
No output schema declared.
No examples provided.
upload_url ~44
If you have the zip, PUT putUrl yourself (max 3MB). Do not put zip in chat. Only send dropUrl to the human if you have no file.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SORNKan Publish MCP server?
SORNKan Publish is a hosted endpoint at https://publish.sornkan.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · publish.sornkan.com
claude mcp add --transport http com-sornkan-publish-website 'https://publish.sornkan.com/mcp'
What is the SORNKan Publish MCP server?
SORNKan Publish is an MCP server listed in the public MCP registry as com.sornkan/publish-website. Host a static website from a zip: $1 USDC/month via x402 on Base, or card/PromptPay link. This page covers its hosted endpoint (https://publish.sornkan.com/mcp).
Is the SORNKan Publish MCP server safe to use?
SORNKan Publish scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SORNKan Publish MCP server expose?
SORNKan Publish exposes 10 tools: publish_website, upload_url, scan, inspect, preview_status, and 5 more. Their descriptions and schemas cost roughly 1,834 tokens of context every time the server is loaded.
Does the SORNKan Publish MCP server require authentication?
No. We connected to SORNKan Publish without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SORNKan Publish MCP server still maintained?
SORNKan Publish is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.