sornkan-publish
Registry code: 7da6bcd13ddb7cf7
Publish a school or teacher website for $1 USDC/month on Base.
from a public catalogue that lists it, not from the operator
- endpoint
- https://publish.sornkan.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is sornkan-publish live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is sornkan-publish free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does sornkan-publish have?
- 10 tools: connect_custom_hostname, edit, upload_url, scan, inspect, renew, preview_status, render_page, ….
- Is sornkan-publish safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.6%· all time 99.6%
last good check
of 10 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- publish a school website
- preview an uploaded site
- renew website hosting
- connect a custom hostname
- render a public url in a browser
- takes → gives
- documents, web pages → text, data
- tools
- 3 reads3 changes data4 moves money
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 2 doors on this origin, so the chain figures are the operator's. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-01
no flags
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
claim moves money 1 USDC paid never probed
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 [email protected] and do not retry payment.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "uploadId" ], "properties": { "slug": { "type": "string", "description": "Lowercase site name to claim; live URL is {slug}.worldsite.workers.dev (ask the human first)" }, "email": { "type": "string", "description": "Receipt email for card/PromptPay payers (optional)" }, "uploadId": { "type": "string", "description": "UUID from inspect — the part after /preview/, never the full preview URL" }, "editToken": { "type": "string", "description": "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." } } }arguments 25 linespublish_website changes data open 8h ago
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 [email protected] and do not retry payment. Never put the zip in chat.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesconnect_custom_hostname moves money unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug", "hostname" ], "properties": { "slug": { "type": "string", "description": "Live site slug to attach the hostname to" }, "hostname": { "type": "string", "description": "Your own domain to point at the site (e.g. www.example.com); CNAME it to sites.sornkan.com" }, "editToken": { "type": "string", "description": "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." } } }arguments 22 linesedit moves money unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "uploadId", "slug" ], "properties": { "slug": { "type": "string", "description": "Live site slug to redeploy" }, "tokens": { "type": "number", "description": "Approximate token size of the change (optional, informational — edits are flat $0.50)" }, "uploadId": { "type": "string", "description": "UUID of the new zip to deploy (call upload_url first)" }, "editToken": { "type": "string", "description": "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." } } }arguments 26 linesupload_url changes data unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesscan reads unknown 5h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "uploadId" ], "properties": { "uploadId": { "type": "string", "description": "UUID of the uploaded zip to check, from upload_url" } } }arguments 13 linesinspect changes data unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "uploadId" ], "properties": { "uploadId": { "type": "string", "description": "UUID of the uploaded zip to deploy as a preview, from upload_url" } } }arguments 13 linesrenew moves money unknown never probed
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: [email protected]. 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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Live site slug to renew — the {slug} in {slug}.worldsite.workers.dev" }, "editToken": { "type": "string", "description": "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." } } }arguments 17 linespreview_status reads unknown 8h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "uploadId" ], "properties": { "uploadId": { "type": "string", "description": "Preview UUID to check — the part after /preview/ if you only have a preview URL" } } }arguments 13 linesrender_page reads unknown 8h ago
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).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "Public https URL to render" }, "fullPage": { "type": "boolean", "description": "Capture entire scrollable page (same $0.005)" } } }arguments 17 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id7da6bcd13ddb7cf7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7da6bcd13ddb7cf7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7da6bcd13ddb7cf7?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- sornkan.com sornkan