Remote MCP · Endpoint

Pono-Pono|フェムケア・デリケートゾーンケア情報 MCP server

No. Pono-Pono|フェムケア・デリケートゾーンケア情報 answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://mcp.yomitasu.jp/s/pono-pono-co-jp/mcp

The last check completed an MCP handshake.

Registry name
jp.yomitasu/pono-pono-co-jp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.16 s
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
株式会社Pono-Ponoが運営する、フェムケア・デリケートゾーンケアに関する情報サイトです。(pono-pono.co.jp の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of Pono-Pono|フェムケア・デリケートゾーンケア情報
CheckedResultHandshake
3 hours agoHandshake completed1.16 s
9 days agoHandshake completed641 ms
10 days agoHandshake completed610 ms
11 days agoHandshake completed641 ms
12 days agoHandshake completed682 ms
14 days agoHandshake completed632 ms
14 days agoHandshake completed598 ms
15 days agoHandshake completed711 ms
17 days agoHandshake completed667 ms
19 days agoHandshake completed622 ms
21 days agoHandshake completed650 ms
24 days agoHandshake completed818 ms
26 days agoHandshake completed616 ms
28 days agoHandshake completed640 ms

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

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 Pono-Pono|フェムケア・デリケートゾーンケア情報 and makes no claim about it beyond what these checks measured.