mcpbeat Sign in

GYOTAK Fish Market MCP Server

by thaifishsashimicatalog Your server? Claim it
answering

GYOTAK Fish Market is answering right now. Last checked 1 min ago. It exposes 23 tools.

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

Uptime history 60 days of history · worst day 93%
60 days agonow
100.0%
Uptime 24h
184 of 184 checks
23
Tools
read from the server
231 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 49

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 September 2026. No other catalogue keeps this.

26 Oct 3 tool descriptions were rewritten get_catch_reports, verify_catch, verify_komon
25 Oct 3 tools disappeared check_payment_status, confirm_payment, create_payment
25 Oct a tool changed the parameters it asks for verify_catch
23 Oct a tool appeared my_orders
23 Oct a tool description was rewritten my_orders
22 Oct a tool changed the parameters it asks for2 times that day place_order
22 Oct a tool description was rewritten place_order
10 Oct a tool appeared verify_purchase
4 Oct 3 tool descriptions were rewritten claim_purchase_proof, get_catch_reports, verify_catch
4 Oct a tool changed the parameters it asks for claim_purchase_proof
and 33 more, back to 8 September 2026

GYOTAK Fish Market missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add fish-market --transport http https://line-harness.gyotak.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://line-harness.gyotak.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.fish-market]
url = "https://line-harness.gyotak.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "fish-market": {
      "url": "https://line-harness.gyotak.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "fish-market": {
      "type": "http",
      "url": "https://line-harness.gyotak.workers.dev/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 23

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify
verify_catch
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 (GYOTAK's own list of records: date, district and verify links, never GPS), this lets you verify without trusting GYOTAK. The exact position is not on the chain (only a commitment to it). The region name is a label set by GYOTAK. GYOTAK checks the region range when recording, but the range used is not part of the record, so a third party cannot confirm it from the chain. 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.
verify_komon
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 do not put the GPS coordinates on the chain, only a hash of them (gpsHash); the region is a label set by GYOTAK. GYOTAK checks the region range when recording, but the range used is not stored in the record, so the region cannot be confirmed from the chain. Currently preprod only.
verify_purchase
Show a purchase proof and trace it: purchase → catch → storage temperature. Use this when the customer asks to see what they bought, where it was caught or how it was stored. Pass the customerKey from this conversation, or a purchase ID (PB-…). Read-only; returns only stamped (on-chain) proofs, with the arguments for verify_catch and verify_temp.
verify_temp
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.
contact
contact_gyotak
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.
get_contact_info
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.
register
register_customer
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.
register_payout
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.
apply
apply_referrer
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.
ask
ask_gyotak
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.
catalog
get_catalog
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.
catch
get_catch_reports
Get catch records by date or freshness tier. Returns the catch date, the region (district name), the blog post URL when published and, for records registered on the Midnight blockchain, a verify link per batch. Exact GPS coordinates are never returned: on v3 records the exact position is not on the chain (only a commitment to it); the district name is a label set by GYOTAK. GYOTAK checks the region range when recording, but the range used is not part of the record, so a third party cannot confirm it from the chain; GYOTAK can disclose the position of a record individually. In-stock products reference these records by date. To check a record on-chain without trusting GYOTAK, open its verify link, or call verify_catch with network "mainnet", the v3 contract address given in the response and the batch ID.
claim
claim_purchase_proof
Link your own purchases’ on-chain purchase proofs to your X (Twitter) account, so a post of yours can be checked against the chain. Buyer’s X account (self-declared): the buyer linked this purchase to their own X account; GYOTAK has not checked that the account belongs to the buyer. 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 linked and links nothing, every time — pass handle to actually link. A link is stamped on chain and cannot be undone, so let the user pick the handle before you pass one. 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.
fish
search_fish
Search fish by name (Japanese, Thai, or English). Provide lineUserId to include VIP tier pricing.
komon
get_komon_records
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.
order
get_order_history
Get B2B order history (last 20 orders). Requires lineUserId of a registered VIP customer.
orders
my_orders
Order history of a LINE VIP customer connected through their personal token URL (gyk_…). No arguments needed — the customer is the owner of this connection. Lists each order (and each invoice not tied to an order) with its date, status (paid / unpaid / overdue / cancelled / awaiting picking / awaiting invoice), the invoice total and due date when an invoice exists, and the items with requested kg → actual kg from the invoice. Invoices and receipts are not linked in the text: the user opens them from the buttons in the catalog widget (Orders tab). Chat-registered customers cannot list orders here; the Receipt button in their widget calls this tool with document=receipt and ref=<order id> to get a 15-minute receipt link for a paid order. Not for guests.
place
place_order
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. (C) LINE VIP customer connected through a personal token URL (get_catalog says ordering is available in this chat): send vipItems only — one entry per item, with fishName, status and tier exactly as get_catalog shows them and the quantity in the form get_catalog gives for that item (bands, packs or kg). The server calculates prices, shipping and the total; the total is an estimate, billing is by invoice after picking, and no payment is taken now. Call with dryRun: true first, show the user the lines and the estimate, and place the order only after the user confirms.
recover
recover_customer_key
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.
referrals
my_referrals
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.
reply
check_reply
Check if GYOTAK staff has replied to a previously submitted inquiry.
report
report_share
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.
share
get_share_kit
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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

set_share_draft
removed 10 Sep 2026
check_payment_status
removed 25 Oct 2026
confirm_payment
removed 25 Oct 2026
create_payment
removed 25 Oct 2026

Endpoints

URLTransportStateLatencyChecked
https://line-harness.gyotak.workers.dev/mcp streamable-http answering 65 ms 1 min ago
https://mcp.gyotakuprotocol.com/mcp streamable-http answering 59 ms 1 min ago

Alternatives to GYOTAK Fish Market

same job, measured the same way
Bellwether MCP
by bellwethermetrics

Live prediction market data from Polymarket and Kalshi with VWAP pricing and reportability.

53 installs/wk local only
Eclipse Promptseal
by cyan-eclipse-technologies-llc

Prompt seal chain + Herald approval binding + incident traceability over fixture prompts only.

local only
Archiet Audit
by anioko

Submit architecture docs, get a consulting-grade traceability audit at a shareable URL

83 installs/wk local only
Ireland CRO Company Registry Lookup & Monitor: Filing Alerts
by nero-engine

Irish company records from the CRO Open Data Portal, with alerts on status changes and filings.

answering
MCP Observability Server
by gagandeeppra

MCP server for querying logs from observability platforms with unified search and tracing

86 installs/wk local only
UDS Toolbox
by udslib

Find why a UDS flash failed from a CAN trace; decode UDS, ISO-TP and DTCs. No hardware.

7 tools answering
True Memory Fragments
by kyle641320

Detect stale source context and retain traceable code-chain understanding for AI coding agents.

69 installs/wk local only
Entalpa Requirements MCP
by entalpa

Spec-driven development for AI coding agents: live requirements, stories and traceability over MCP

answering

GYOTAK Fish Market — questions

Answers built from our own checks of this server.

What can GYOTAK Fish Market do?
It exposes 23 tools, read directly from the server on our last check. Among them: apply_referrer, ask_gyotak, check_reply, claim_purchase_proof, contact_gyotak, get_catalog and 17 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is GYOTAK Fish Market mostly used for?
Its tools cluster around verify, contact and register. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is GYOTAK Fish Market working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 184 of 184 checks got a reply (100.0%), average response time 231 ms. The bar chart above shows every period we have measured.
Did GYOTAK Fish Market ever remove tools?
Yes. set_share_draft, check_payment_status, confirm_payment, create_payment are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect GYOTAK Fish Market?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does GYOTAK Fish Market need an API key?
No. GYOTAK Fish Market completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 23 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is GYOTAK Fish Market?
It answers our handshake in 231 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.