Remote MCP · Endpoint
銀座の貸切個室で高級天然とらふぐ料理と近江牛 ぎんざ姿 MCP server
No. 銀座の貸切個室で高級天然とらふぐ料理と近江牛 ぎんざ姿 answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.yomitasu.jp/s/fugusugata-jp/mcp
The last check completed an MCP handshake.
- Registry name
- jp.yomitasu/fugusugata-jp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 609 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- 接待に、会食に。創業60年以上の、銀座 の 一日一組 の 完全個室 の老舗 ふぐ料理店 、高級和食店 、ぎんざ姿 でございます。（fugusugata.jp の内容を検索して答える。ヨミタス経由）
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 609 ms |
| 2 days ago | Handshake completed | 675 ms |
| 4 days ago | Handshake completed | 714 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with 銀座の貸切個室で高級天然とらふぐ料理と近江牛 ぎんざ姿 and makes no claim about it beyond what these checks measured.