Home / MCP registry index / com.thaifishsashimicatalog/fish-market

GYOTAK Fish Market

com.thaifishsashimicatalog/fish-market in the official MCP registry. Endpoint https://mcp.gyotakuprotocol.com/mcp.

The registry describes it as: Sashimi-grade flash-frozen fish from Thailand. Catalog, ordering, and on-chain traceability.

We read its 23 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_catalog search_fish get_contact_info get_catch_reports place_order get_order_history my_orders verify_catch verify_temp get_komon_records verify_komon ask_gyotak contact_gyotak check_reply register_customer recover_customer_key apply_referrer my_referrals get_share_kit verify_purchase report_share claim_purchase_proof register_payout

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-thaifishsashimicatalog-fish-market/badge.svg)](https://lazaretto.dev/mcp-registry/com-thaifishsashimicatalog-fish-market)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.