# SORNKan Worldsite (remote · publish.sornkan.com)

Publish a school or teacher website for $1 USDC/month on Base.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `publish.sornkan.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-sornkan-publish-website/publish.md), [page](https://verifymcp.io/servers/com-sornkan-publish-website/publish)

## Channel facts

- Endpoint: `https://publish.sornkan.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1343 tokens (~134/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_website" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SORNKan Worldsite MCP server?

SORNKan Worldsite 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.

### Claude

```bash
claude mcp add --transport http com-sornkan-publish-website 'https://publish.sornkan.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-sornkan-publish-website": {
      "url": "https://publish.sornkan.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-sornkan-publish-website": {
      "type": "http",
      "url": "https://publish.sornkan.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-sornkan-publish-website]
url = "https://publish.sornkan.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-sornkan-publish-website": {
      "type": "remote",
      "url": "https://publish.sornkan.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-sornkan-publish-website --url 'https://publish.sornkan.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-sornkan-publish-website:
    url: "https://publish.sornkan.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-sornkan-publish-website": {
      "Transport": "http",
      "Url": "https://publish.sornkan.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-sornkan-publish-website -t streamable-http -u 'https://publish.sornkan.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-sornkan-publish-website": {
      "type": "http",
      "url": "https://publish.sornkan.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 74, +1)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 73, +1)

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

### 2026-09-15 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (10)

### `publish_website` (~167 tokens)

Publish a website. 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.

### `upload_url` (~44 tokens)

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.

### `scan` (~91 tokens)

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.

Input parameters:

- `uploadId` (string, required)

### `inspect` (~202 tokens)

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.

Input parameters:

- `uploadId` (string, required)

### `preview_status` (~97 tokens)

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.

Input parameters:

- `uploadId` (string, required)

### `claim` (~217 tokens)

Go live. $1 USDC first 30 days. 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.

Input parameters:

- `email` (string)
- `slug` (string)
- `uploadId` (string, required)

### `renew` (~135 tokens)

Renew hosting +30 days for $1 USDC. Same claiming wallet only. 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.

Input parameters:

- `slug` (string, required)

### `connect_custom_hostname` (~126 tokens)

Connect an existing hostname via CNAME to sites.sornkan.com (no registrar). One-time $1 USDC, same claiming wallet, while lease is live. 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.

Input parameters:

- `hostname` (string, required)
- `slug` (string, required)

### `edit` (~163 tokens)

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) unless a complimentary edit remains. Same claiming wallet. Does not extend lease days. 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. Wallet-less owners: pass ownerWallet (the address that claimed this slug) so the 402 carries a Stripe payment_url.

Input parameters:

- `ownerWallet` (string)
- `slug` (string, required)
- `tokens` (number)
- `uploadId` (string, required)

### `render_page` (~101 tokens)

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).

Input parameters:

- `fullPage` (boolean): Capture entire scrollable page (same $0.005)
- `url` (string, required): Public https URL to render

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-sornkan-publish-website/publish#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 71
- 2026-09-13: 71
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 65
- 2026-09-01: 65
- 2026-08-31: 65
- 2026-08-30: 64
- 2026-08-29: 64
- 2026-08-28: 63
- 2026-08-27: 63
- 2026-08-26: 62
- 2026-08-25: 61
- 2026-08-24: 62
- 2026-08-23: 61
- 2026-08-22: 60

## Common questions

### What is the SORNKan Worldsite MCP server?

SORNKan Worldsite is an MCP server listed in the public MCP registry as com.sornkan/publish-website. Publish a school or teacher website for $1 USDC/month on Base. This page covers its hosted endpoint (https://publish.sornkan.com/mcp).

### Is the SORNKan Worldsite MCP server safe to use?

SORNKan Worldsite scores 74 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 Worldsite MCP server expose?

SORNKan Worldsite exposes 10 tools: publish_website, upload_url, scan, inspect, preview_status, and 5 more. Their descriptions and schemas cost roughly 1,343 tokens of context every time the server is loaded.

### Does the SORNKan Worldsite MCP server require authentication?

No. We connected to SORNKan Worldsite without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SORNKan Worldsite MCP server still maintained?

SORNKan Worldsite is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://publish.sornkan.com/mcp
- Repository: https://github.com/sornkan/sornkan
- Website: https://publish.sornkan.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-sornkan-publish-website/publish.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-sornkan-publish-website/publish.json
- HTML version of this page: https://verifymcp.io/servers/com-sornkan-publish-website/publish