Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GYOTAK Fish Market

REMOTE · LINE-HARNESS.GYOTAK.WORKERS.DEV · SCANNED SEP 28

Sashimi-grade flash-frozen fish from Thailand. Catalog, ordering, and on-chain traceability.

+4 this week 71 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3780 tokens (~140/item across 27 items; 24 tools + 3 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 Management80
  • Stability observed for 24 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
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
  • Supports UI / widget rendering.Pass
Install

How do I install the GYOTAK Fish Market MCP server?

GYOTAK Fish Market is a hosted endpoint at https://line-harness.gyotak.workers.dev/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 · line-harness.gyotak.workers.dev

# add to Claude Code
claude mcp add --transport http com-thaifishsashimicatalog-fish-market 'https://line-harness.gyotak.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-thaifishsashimicatalog-fish-market": {
      "url": "https://line-harness.gyotak.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-thaifishsashimicatalog-fish-market": {
      "type": "http",
      "url": "https://line-harness.gyotak.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-thaifishsashimicatalog-fish-market]
url = "https://line-harness.gyotak.workers.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thaifishsashimicatalog-fish-market": {
      "type": "remote",
      "url": "https://line-harness.gyotak.workers.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-thaifishsashimicatalog-fish-market --url 'https://line-harness.gyotak.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-thaifishsashimicatalog-fish-market:
    url: "https://line-harness.gyotak.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-thaifishsashimicatalog-fish-market": {
      "Transport": "http",
      "Url": "https://line-harness.gyotak.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-thaifishsashimicatalog-fish-market -t streamable-http -u 'https://line-harness.gyotak.workers.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "com-thaifishsashimicatalog-fish-market": {
      "type": "http",
      "url": "https://line-harness.gyotak.workers.dev/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.

  • 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
  • 27 Sept 26 +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.

  • 26 Sept 26 +1
    • Tool “check_payment_status” rewrote its description, which is the text the model reads security
    • Tool “confirm_payment” rewrote its description, which is the text the model reads security
    • Tool “create_payment” rewrote its description, which is the text the model reads security
    • Tool “place_order” rewrote its description, which is the text the model reads security
    • Tool “recover_customer_key” rewrote its description, which is the text the model reads security
    • Destructive annotations: 0 → pass functional
    • “confirm_payment” reworded the description of “customer_key” cosmetic
  • 25 Sept 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
  • 24 Sept 26 0
    • Resource “GYOTAK 報酬の受取先” now points somewhere else: ui://gyotak/payout-v1 → ui://gyotak/payout-v2 security
    • Resource “GYOTAK 食べた写真” now points somewhere else: ui://gyotak/share-photo-v1 → ui://gyotak/share-photo-v2 security
    • Tool “claim_purchase_proof” rewrote its description, which is the text the model reads security
    • “claim_purchase_proof” added an optional parameter “auto_bind” cosmetic
    • “claim_purchase_proof” added an optional parameter “consent” cosmetic
  • 23 Sept 26 +1
    • Resource “GYOTAK カタログ” now points somewhere else: ui://gyotak/catalog-view-v11 → ui://gyotak/catalog-view-v12 security
  • 21 Sept 26 +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.

  • 19 Sept 26 0
    • Tool “claim_purchase_proof” rewrote its description, which is the text the model reads security
    • “claim_purchase_proof” reworded the description of “handle” cosmetic
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 28 Sept 2026 · Probed https://line-harness.gyotak.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gyotak.workers.dev CN=YE2,O=Let's Encrypt,C=US 22 Sept 2026 21 Dec 2026 ECDSA 256 ECDSA-SHA384 68b68f413842de33b90e613f6688c7ca202
SANs: *.gyotak.workers.dev, gyotak.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of line-harness.gyotak.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
workers.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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://line-harness.gyotak.workers.dev/mcp Verified 200
http (plaintext) http://line-harness.gyotak.workers.dev/mcp Inconclusive 405
MCP tools · 24 exposed · ~3,683 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. 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 →

Tool Tokens
apply_referrer ~165

Look up your GYOTAK referral MCP URL. The URL is issued automatically when the payment for your first chat order is confirmed and is included in the payment confirmation email; call this to see it again. If you have a paid order but no URL yet, one is issued now. Referrers earn 5% of the product subtotal on paid orders placed through their URL. If you are connected through a personal token URL, omit customerKey.

NameTypeReqDescription
contactstring–Contact (email, LINE ID, etc.) — optional
customerKeystring–Your customerKey (gyotak_cus_...). Omit when connected through a personal token URL.
namestring–Referrer display name — optional, defaults to your registered name

No output schema declared.

No examples provided.

ask_gyotak ~72

Search GYOTAK FAQ for answers about shipping, payment, products, defrosting, traceability, B2B registration, etc. Returns top matching FAQ entries. If no match, suggest using contact_gyotak to escalate.

NameTypeReqDescription
questionstringyesQuestion text (any language)

No output schema declared.

No examples provided.

check_payment_status ~110

Test / QA only — do not use for customer orders. Returns the Cardano preprod payment session of an order placed by a GYOTAK test customer (status, amount, deadline, TX hash if paid). For any other order_id it returns PromptPay guidance and nothing about the order. Customers pay via the PromptPay QR attached to the order confirmation email and receive an email once the payment is confirmed.

NameTypeReqDescription
order_idstringyesOrder ID (e.g. "BB-42")

No output schema declared.

No examples provided.

check_reply ~42

Check if GYOTAK staff has replied to a previously submitted inquiry.

NameTypeReqDescription
inquiryIdstringyesInquiry ID (e.g. "INQ-042")

No output schema declared.

No examples provided.

claim_purchase_proof ~410

Claim the on-chain purchase proofs for your own purchases and attach your X (Twitter) handle to them, so a post of yours can be checked against the chain. Each stamped purchase comes with the URL of its public verification page. Only works through a personal token URL connector — there is no customerKey argument. Called with no arguments it only lists the purchases that can be claimed and claims nothing, every time — pass handle to actually claim. A claim is stamped on chain and cannot be undone, so let the user pick the handle before you pass one. The handle is what you tell us: GYOTAK does not verify that you own the account. Automatic binding of future purchases is off by default: to turn it on, pass handle with auto_bind "on" — the first such call returns the consent text; show it to the user word for word (the text is in Japanese and English; show both), and only if they agree call again with consent true. Pass auto_bind "off" to stop it (no handle needed); only later purchases stop, anything already recorded stays.

NameTypeReqDescription
auto_bindstring–Turn automatic binding of future purchases to your X handle on or off. "on" needs handle and consent. "off" needs nothing else. Omit to leave the setting as it is.
consentboolean–Set true only when the user has read the consent text returned by an earlier auto_bind "on" call and agreed to it. Never set it on your own.
handlestring–Your X handle without the leading @ (letters, digits and underscore, 1-15 characters). Required to claim: a call without it only lists your purchases and claims nothing, even if you claimed before. P…
purchase_idstring–Claim only this purchase (e.g. "PB-20260917-a97953d3"). Omit to claim every purchase of yours that is not claimed yet.

No output schema declared.

No examples provided.

confirm_payment ~132

Test / QA only — do not use for customer orders: customers pay via the PromptPay QR attached to the order confirmation email. Executes the Cardano preprod A→B→A settlement for an order placed by a GYOTAK test customer. Requires that test customer's customerKey, a pending payment session from create_payment, and a monthly auto-settle allowance. For any other order_id it returns PromptPay guidance and changes nothing.

NameTypeReqDescription
customer_keystringyescustomerKey of the test customer that placed the order
order_idstringyesOrder ID (e.g. "BB-123")

No output schema declared.

No examples provided.

contact_gyotak ~69

Submit a question to GYOTAK staff when FAQ does not have the answer. Staff will reply via Discord. Use check_reply to retrieve the response later.

NameTypeReqDescription
namestring–Your name (optional)
questionstringyesQuestion to ask GYOTAK staff

No output schema declared.

No examples provided.

create_payment ~135

Test / QA only — do not use for customer orders, and do not call it after placing a customer order: customers pay via the PromptPay QR attached to the order confirmation email. Works only for orders of GYOTAK test customers; for any other order_id it returns PromptPay guidance and creates nothing. For a test order it computes the THB→tADA conversion, creates a Cardano preprod payment session with a 30-minute expiry, and returns the payment details (GYOTAK A→B→A round-trip).

NameTypeReqDescription
order_idstringyesOrder ID (e.g. "BB-42")

No output schema declared.

No examples provided.

get_catalog ~150

Get GYOTAK's full fish catalog with real-time availability, retail prices (THB/kg), freshness tiers, and traceability records. Retail prices are always included. For registered chat customers, pass customerKey (gyotak_cus_...) to show wholesale pricing and enable one-tap checkout. For LINE VIP customers, pass lineUserId. Delivery is available within Thailand only. International addresses are not accepted.

NameTypeReqDescription
customerKeystring–GYOTAK customerKey (gyotak_cus_...) for registered chat customers — enables identification, wholesale pricing, and one-tap checkout (optional)
lineUserIdstring–LINE user ID for VIP pricing (optional)

No output schema declared.

No examples provided.

get_catch_reports ~143

Get catch records by date or freshness tier. Returns GPS coordinates, photo timestamp, and blog URL for traceability verification. In-stock products reference these records; consumers can access records via blog URL on package label even after sold out. Planned integration: Each catch record will be registered on Midnight blockchain as an immutable on-chain transaction, making GPS coordinates, timestamps, and photo hashes tamper-proof and permanently verifiable.

NameTypeReqDescription
datestring–YYYY-MM-DD format. Returns records for that specific date.
tierstring–Freshness tier: fresh=last 30 days, tier1=31-60 days, tier2=61-90 days

No output schema declared.

No examples provided.

get_contact_info ~119

Get the two ways to buy from GYOTAK, with the contact details for each: retail (order here through place_order, or browse the web shop) and B2B wholesale for restaurants and businesses (LINE @284ezjvm, tier pricing, application required). Call this when the user asks how to buy, how to open a wholesale account, or how to reach GYOTAK. Takes no arguments and returns static text — for product availability or prices use get_catalog, and for other questions use ask_gyotak.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_komon_records ~73

Get GYOTAK KOMON physical authentication records from the database. Each record represents a PUF (physically unclonable function) registration with minutiae extraction and on-chain commitment. Shielded records do not expose GPS.

NameTypeReqDescription
statusstring–Filter by status (default: all non-test)

No output schema declared.

No examples provided.

get_order_history ~47

Get B2B order history (last 20 orders). Requires lineUserId of a registered VIP customer.

NameTypeReqDescription
lineUserIdstringyesLINE user ID of the VIP customer

No output schema declared.

No examples provided.

get_share_kit ~158

Get the facts and constraints for writing a social media post about GYOTAK with the caller's referral URL: order facts, fish photo URLs, verification page URLs of the caller's stamped purchase proofs, allowed and forbidden claims, and the required referral disclosure. The wording is up to the user and their assistant. Call this again each time the user asks for a post; do not reuse a previous result.

NameTypeReqDescription
customerKeystring–Your customerKey (gyotak_cus_...). Omit when connected through a personal token URL.
includePhotosboolean–Set true only if the user wants to attach a photo they take themselves with a blockchain capture record. Returns photo_capture_url and the list of recorded photos.

No output schema declared.

No examples provided.

my_referrals ~120

Show your referral summary as a GYOTAK referrer: your referral URL, number of referred orders (paid / unpaid), this month's estimated commission, unpaid balance, payout destination status, and the last 5 paid referred orders (order number, date, subtotal, commission — no buyer details). Only works for the customer of this connection; if you are connected through a personal token URL, omit customerKey.

NameTypeReqDescription
customerKeystring–Your customerKey (gyotak_cus_...). Omit when connected through a personal token URL.

No output schema declared.

No examples provided.

place_order ~586

Place an order. Two modes: (A) VIP wholesale: provide lineUserId of a registered VIP customer. (B) Guest retail: provide customerName, phone, items array, and a delivery address — shippingAddress, shippingProvince and email are all required, and an order missing any of them is rejected. Guest orders are priced at tier-linked retail rates (server-calculated) and the total is final at this point; a confirmation email with a PromptPay QR follows. Without customerKey or a personal token URL connection, every order creates a new customer with a new customerKey, even when the email was used before (orders are never linked to an existing customer by email); the new key is returned in the response and the confirmation email — tell the user to save it. Inventory is NOT deducted — orders go to the pick queue for staff fulfillment. Delivery is available within Thailand only, so the province must be a Thai one. International addresses are not accepted.

NameTypeReqDescription
customerKeystring–(Guest mode) Registered customer key (from register_customer). Resolves name/phone/shipping automatically. If you are connected through a personal token URL the customer is already resolved: send ite…
customerNamestring–(Guest mode) Customer name
emailstring–(Guest mode) Email address for the order confirmation — required for guest orders
fishNamestring–(VIP mode) Fish name (romaji)
itemsarray–(Guest mode) Order items
langstring–(Guest mode, optional) Language of the confirmation email. Defaults to en.
lineUserIdstring–LINE user ID of VIP customer (VIP mode). Omit for guest mode.
memostring–(Optional) Order notes
phonestring–(Guest mode) Contact phone number
referrerIdstring–(Optional) Referrer ID for tracking
requestedKgnumber–(VIP mode) Requested weight in kg
shippingAddressstring–(Guest mode) Street address and building name — required for guest orders
shippingDistrictstring–(Guest mode) Hua Hin / Pranburi 等の地元配達判定に必須。住所に含まれていれば自動判定するが、明示推奨 / District name. Required to detect local (free) delivery for Hua Hin / Pranburi. Auto-detected from shippingAddress when present, b…
shippingProvincestring–(Guest mode) Thai province name, used for shipping cost — required for guest orders. Thailand only.
totalThbnumber–(VIP mode) Total amount in THB

No output schema declared.

No examples provided.

recover_customer_key ~91

Explains where a lost customerKey can be found: a key issued with an order is written in the order confirmation email sent to the registered address (each order placed without a key has its own key). For keys that cannot be found there, it points to contact_gyotak. This tool does not look up, verify or send anything.

NameTypeReqDescription
phonestringyesPhone number used at registration

No output schema declared.

No examples provided.

register_customer ~117

Register as a GYOTAK customer. Collect name, phone, address, email, and customer type (Retail or Wholesale) via conversation BEFORE calling this tool. Returns a customerKey for future orders. Save the key in your AI memory.

NameTypeReqDescription
addressstringyesShipping address
customerTypestringyesCustomer type: Retail (consumer) or Wholesale (business)
emailstring–Email address (optional)
namestringyesFull name (English)
phonestringyesContact phone number

No output schema declared.

No examples provided.

register_payout ~181

Email the GYOTAK referrer a link to the form where they register where their commission should be sent: a Thai PromptPay QR (read inside the form, the image is never uploaded) or a stablecoin address (USDC on Base, or USDM on Cardano). Call this when the user wants to register, see, or change their payout destination. Returns the destination currently on file, masked, and the masked address the link was sent to. For security the form URL is never shown in the chat — the link goes only to the email address on file, so tell the user to open it from their email. Never ask the user to type the number or the wallet address into the chat.

NameTypeReqDescription
customerKeystring–Your customerKey (gyotak_cus_...). Omit when connected through a personal token URL.

No output schema declared.

No examples provided.

report_share ~119

Report a social media post you published that recommends GYOTAK with your referral URL. Call this right after posting, with the platform and the public URL of the post. GYOTAK records it and later verifies that the post is public and contains the referral URL.

NameTypeReqDescription
customerKeystring–Your customerKey (gyotak_cus_...). Omit when connected through a personal token URL.
platformstringyesPlatform the post was published on
post_urlstringyesPublic https URL of the published post

No output schema declared.

No examples provided.

search_fish ~60

Search fish by name (Japanese, Thai, or English). Provide lineUserId to include VIP tier pricing.

NameTypeReqDescription
lineUserIdstring–LINE user ID for VIP pricing (optional)
querystringyesFish name to search for

No output schema declared.

No examples provided.

verify_catch ~244

Verify a GYOTAK catch record DIRECTLY from the Midnight blockchain. Reads on-chain state and returns the raw hex plus decoded fields for independent verification. Unlike get_catch_reports (which returns GYOTAK's own database), this lets you verify without trusting GYOTAK. GPS coordinates are cryptographically hidden (hiding commitment with secret nonce); only the region is provable. Supports both preprod and mainnet. batchId also accepts several IDs separated by commas: they are all checked against a single fetch of the contract state, and the response lists found/not-found per ID.

NameTypeReqDescription
batchIdstring–Filter to a specific catch record by batchId (e.g. "CR-TESTV3-INSIDE-02"). Omit to return all records in the contract.
contractAddressstringyesMidnight contract address (64-char hex). Example: 2e519c349331a6aaee82a7ed31aa5e39d6a3995f6cf85ec2256c97cda9a8c302
networkstring–Midnight network (default: preprod)

No output schema declared.

No examples provided.

verify_komon ~135

Verify a GYOTAK KOMON record directly from the Midnight blockchain. Reads on-chain state and returns the raw hex plus decoded fields for independent verification. Unlike get_komon_records (which returns GYOTAK's database), this reads directly from the chain. Shielded records prove region membership without exposing GPS. Currently preprod only.

NameTypeReqDescription
contractAddressstring–Midnight komon contract address (64-char hex)
komonIdstring–Filter to a specific komon record by ID. Omit to return all records.
networkstring–Midnight network (default: preprod)

No output schema declared.

No examples provided.

verify_temp ~205

Verify GYOTAK cold-chain storage temperatures DIRECTLY from the Midnight blockchain. Reads on-chain state and returns decoded hourly temperature records per freezer for independent verification. Unlike the dashboard (which reads from GYOTAK's D1 database), this lets you verify without trusting GYOTAK. Each value is the HOURLY AVERAGE committed on-chain; it does not prove the temperature stayed within any limit at every moment in that hour. Supports both preprod and mainnet.

NameTypeReqDescription
contractAddressstring–Midnight temp-log contract address (64-char hex). Default: mainnet production contract.
freezerIdnumber–Filter to a specific freezer by ID. Omit to return all freezers.
hourStartUtcstring–Filter to a specific hour (e.g. "2026-07-09 11:00:00"). Omit to return all hours.
networkstring–Midnight network (default: mainnet)

No output schema declared.

No examples provided.

Common questions

What is the GYOTAK Fish Market MCP server?

GYOTAK Fish Market is an MCP server listed in the public MCP registry as com.thaifishsashimicatalog/fish-market. Sashimi-grade flash-frozen fish from Thailand. Catalog, ordering, and on-chain traceability. This page covers its hosted endpoint (https://line-harness.gyotak.workers.dev/mcp).

Is the GYOTAK Fish Market MCP server safe to use?

GYOTAK Fish Market scores 71 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 GYOTAK Fish Market MCP server expose?

GYOTAK Fish Market exposes 24 tools: get_catalog, search_fish, get_contact_info, get_catch_reports, place_order, and 19 more. Their descriptions and schemas cost roughly 3,683 tokens of context every time the server is loaded.

Does the GYOTAK Fish Market MCP server require authentication?

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

Is the GYOTAK Fish Market MCP server still maintained?

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