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/earthenware-jp/mcp

The last check completed an MCP handshake.

Registry name
jp.yomitasu/earthenware-jp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
653 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
柏崎剛がプロデュースする陶器「慈焼」の公式サイトです。(earthenware.jp の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of 慈(慈焼 公式サイト)
CheckedResultHandshake
1 hour agoHandshake completed653 ms
2 days agoHandshake completed282 ms
4 days agoHandshake completed231 ms
6 days agoHandshake completed223 ms
7 days agoHandshake completed603 ms
9 days agoHandshake completed1.07 s
10 days agoHandshake completed350 ms
11 days agoHandshake completed219 ms
14 days agoHandshake completed231 ms
15 days agoHandshake completed216 ms
17 days agoHandshake completed215 ms
19 days agoHandshake completed219 ms
20 days agoHandshake completed596 ms
21 days agoHandshake completed573 ms
22 days agoHandshake completed733 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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.