GYOTAK Fish Market
Server Details
Sashimi-grade flash-frozen fish from Thailand. Catalog, ordering, and on-chain traceability.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 24 tools
Several pairs have blurry boundaries: my_orders vs get_order_history both return order history (differing only by connection type), and get_contact_info overlaps with ask_gyotak on 'how to buy / B2B registration'. The database-vs-on-chain pairs (get_catch_reports/verify_catch, get_komon_records/verify_komon) are well distinguished by their descriptions, and claim_stay_proof is an odd out-of-domain tool for a fish market, but most other tools target distinct resources.
Dominant verb_noun pattern (place_order, register_customer, verify_catch, claim_purchase_proof, report_share) with a few deviations: the my_* prefix (my_orders, my_referrals) and verb-only ask_gyotak/contact_gyotak. The convention is predictable enough to navigate despite these minor variants.
At 24 tools this sits in the heavy range for a fish-market ordering server; referral payouts, two parallel blockchain verification families (catch/KOMON/temp), proof claiming and stay proofs push it well beyond core commerce. Each tool is plausible, but the surface feels inflated and could be consolidated.
The lifecycle is largely covered: browse/search catalog, register, order, view orders, referrals, proofs, and independent chain verification, plus support escalation. Gaps remain around order modification/cancellation and delivery status tracking, so agents may hit dead ends after placing an order.
Available Tools
24 toolsapply_referrerMy referral URLADestructiveIdempotentInspect
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.
Inputs: name, contact, customerKey.
ask_gyotakSearch FAQARead-onlyIdempotentInspect
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.
Inputs: question (required).
check_replyCheck staff replyBRead-onlyIdempotentInspect
Check if GYOTAK staff has replied to a previously submitted inquiry.
Inputs: inquiryId (required).
claim_purchase_proofLink purchase proofs to X accountADestructiveInspect
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.
Inputs: handle, consent, auto_bind, purchase_id.
claim_stay_proofReceive stay purchase proofAInspect
Receive a stay purchase proof (SB-… ID, from a stay booked and paid through a GYOTAKU Protocol store window) with its claim code, and link it to your GYOTAK referral account. Works only through your personal token URL. Optional: show_referral puts your referral URL for that stay on the public proof page; handle links your own X account to the proof on the public chain (permanent; it cannot be removed). Call again with the same code to change show_referral or add an X account.
Inputs: claim_code (required), purchase_id (required), handle, show_referral.
contact_gyotakMessage GYOTAK staffADestructiveInspect
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.
Inputs: question (required), name.
get_catalogFish catalogARead-onlyIdempotentInspect
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 let them order with their saved details. For LINE VIP customers, pass lineUserId. Delivery is available within Thailand only. International addresses are not accepted.
Inputs: lineUserId, customerKey. Returns: vip, items, catalog, nextActions, +1 more
get_catch_reportsCatch recordsARead-onlyIdempotentInspect
Get catch records by date or freshness tier. Returns the catch date, the region (district name), the blog post URL when published (records whose blog post is not published yet are included, without a blog URL) 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.
Inputs: date, tier. Returns: count, limit, reports, verifyCatchContract
get_contact_infoHow to buy / contactARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
get_komon_recordsKOMON recordsARead-onlyIdempotentInspect
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.
Inputs: status.
get_order_historyVIP order historyARead-onlyIdempotentInspect
Get B2B order history (last 20 orders). Requires lineUserId of a registered VIP customer.
Inputs: lineUserId (required).
my_ordersMy orders (LINE VIP)ARead-onlyIdempotentInspect
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= to get a 15-minute receipt link for a paid order. Not for guests.
Inputs: ref, document.
my_referralsReferral summaryARead-onlyIdempotentInspect
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.
Inputs: customerKey.
place_orderPlace orderADestructiveInspect
Place an order. Two modes: (A) 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. (B) 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.
Inputs: lang, memo, email, items, +9 more.
recover_customer_keyFind a lost customerKeyARead-onlyIdempotentInspect
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.
Inputs: phone (required).
register_customerRegister customerADestructiveInspect
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.
Inputs: name (required), phone (required), address (required), customerType (required), +1 more.
register_payoutPayout destination (email link)ADestructiveInspect
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.
Inputs: customerKey.
search_fishSearch fishARead-onlyIdempotentInspect
Search fish by name (Japanese, Thai, or English). Provide lineUserId to include VIP tier pricing.
Inputs: query (required), lineUserId. Returns: query, results, vipCompanyName
verify_catchVerify catch record on chainARead-onlyIdempotentInspect
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.
Inputs: contractAddress (required), batchId, network. Returns: error, found, source, message, +16 more
verify_komonVerify KOMON record on chainARead-onlyIdempotentInspect
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.
Inputs: komonId, network, contractAddress. Returns: error, source, message, records, +4 more
verify_purchasePurchase proof and traceARead-onlyIdempotentInspect
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.
Inputs: purchaseId, customerKey. Returns: error, message, pending_stamp, older_not_shown, +1 more
verify_tempVerify storage temperatures on chainARead-onlyIdempotentInspect
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.
Inputs: network, freezerId, hourStartUtc, contractAddress. Returns: error, source, message, freezers, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
AI-readable directory + commerce layer: 3,500+ SEA businesses, plus products from verified stores.
Free read-only crypto whale-tracking & market-data MCP tools across 14 chains. No auth.
AI-powered organic supply chain verification: certification, OFAC, FDA import checks.
A2A + MCP hub for retail grocery procurement — 20 markets on the SCHEMA algo record. Trade only.
Related MCP Servers
- FlicenseNot gradedqualityFmaintenanceSemantic product search and price-intelligence API over Singapore e-commerce data. Computes auditable value-scores from Shannon entropy across vendor price distributions, with pay-per-call pricing via x402 (USDC) alongside Stripe.-
- AlicenseNot gradedqualityDmaintenanceMethodology-transparent BTC + ETH whale forensics. 30 tools, anonymous OAuth 2.1 Free tier.MIT
- AlicenseNot gradedqualityBmaintenanceA2A Grocery is the Agent-to-Agent (A2A) + Model Context Protocol (MCP) hub for retail grocery procurement. It puts makers, brand owners, private label, distributors and importers in front of the AI agents that now do the grocery buying, and gives retail procurement desks every cleared supplier's record, ready to order. 20 markets on the SCHEMA algo record. No ads. No rank for sale. Trade only.MIT
- AlicenseNot gradedqualityBmaintenanceAn open MCP and REST front door that lets a customer's own AI purchasing agent search a wholesaler's catalogue, receive signed fixed-price offers, and place orders within limits a person signed. Each order is auto-confirmed, held for a named approver, or refused by mandate rules, with every decision recorded in a tamper-evident, hash-chained log both sides can verify.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.