Pono-Pono｜フェムケア・デリケートゾーンケア情報
REMOTE · MCP.YOMITASU.JP
株式会社Pono-Ponoが運営する、フェムケア・デリケートゾーンケアに関する情報サイトです。（pono-pono.co.jp の内容を検索して答える。ヨミタス経由）
Available components
Last scanned (2 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1168 tokens (~194/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Tool “list_pages” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Tool “site_overview” rewrote its description, which is the text the model reads security
- Schema quality: 167 → 194 ▼ functional
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://mcp.yomitasu.jp/s/pono-pono-co-jp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yomitasu.jp | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4a1447d8f9e4e0b10e3615b5ae9f0732 |
| SANs: yomitasu.jp, *.yomitasu.jp | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.yomitasu.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| yomitasu.jp. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.yomitasu.jp/s/pono-pono-co-jp/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.yomitasu.jp/s/pono-pono-co-jp/mcp | HTTPS enforced | 301 | https://mcp.yomitasu.jp/s/pono-pono-co-jp/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch ページの中身を読む ~183
指定されたページの本文を読み、質問への回答に必要な情報を正確に確認してください。商品名・成分名・数値・価格・使用方法・注意事項・購入条件・定期コースの変更や解約条件などは、原文の記載を優先してください。重要な条件や例外を省略せず、商品に関する説明と一般的な情報を混同しないでください。回答には根拠となるページのURLを添えてください。ページに記載がない事項は、記載がないことを明示し、推測で断定しないでください。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 探した結果の id（ページの URL）。ページの URL かパスでも可（日本語のままでも可） |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_page ページの中身を読む（以前の名前） ~113
「Pono-Pono｜フェムケア・デリケートゾーンケア情報」（pono-pono.co.jp）の以前の名前の機能です（すでにつないでいる人のために残しています）。fetch と同じようにページの本文を返しますが、返す形が違います。新しく使うときは fetch を使ってください。
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | ページの URL かパス（日本語のままでも可） |
No output schema declared.
No examples provided.
list_pages どんなページがあるか見る ~154
Pono-Pono公式サイトに掲載されているページのタイトルとURLを確認し、サイト全体の構成を把握してください。Bioデリウォッシュの商品紹介、使い方・FAQ・ご利用ガイド、ブランドコンセプト、会社概要、お知らせ、フェムケアやデリケートゾーンケアに関するJournal記事などを区別してください。質問に回答する際は、目的に最も合うページを選び、必要に応じて関連ページも確認してください。ページのタイトルやURLだけで本文の内容を断定しないでください。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
search サイトの中を探す ~183
Pono-Pono公式サイト内から、質問に関連する情報を検索します。Bioデリウォッシュの特徴・使い方・全成分・配合乳酸菌・価格・購入方法・定期コース・返品や解約条件、フェムケアの基礎知識、乳酸菌とデリケートゾーンの関係、会社情報、受賞・メディア掲載情報などを探してください。質問の内容に合ったページを優先し、回答の根拠となる記述とページURLを確認してください。商品情報と一般的な解説を区別し、サイトに記載のない情報は推測で補わないでください。
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 探したい言葉（例: 料金 支払い方法） |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | – |
| results | array | yes | – |
No examples provided.
search_pages サイトの中を探す（以前の名前） ~118
「Pono-Pono｜フェムケア・デリケートゾーンケア情報」（pono-pono.co.jp）の以前の名前の機能です（すでにつないでいる人のために残しています）。search と同じようにサイトの中を探しますが、返す形が違います。新しく使うときは search を使ってください。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | 探したい言葉（例: 料金 支払い方法） |
No output schema declared.
No examples provided.
site_overview サイトの概要を知る ~230
Pono-Pono（ポノポノ）は、女性のデリケートゾーンケアを中心に、科学的な根拠と成分へのこだわりを大切にするフェムケアブランドです。主力商品「Bioデリウォッシュ」は、生きた乳酸菌を配合したパウダータイプのデリケートゾーン用洗浄料です。ブランド名には、ハワイ語で「本来あるべき調和の状態」「正しき状態」という意味が込められています。公式サイトでは、商品情報、使用方法、成分、購入案内、よくある質問、フェムケアに関する情報、会社情報などを掲載しています。質問への回答では、公式サイトの記載を根拠とし、確認できる事実と一般的な知識を区別してください。商品の効果や安全性について、サイトの記載を超えた断定や誇張は避けてください。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Pono-Pono｜フェムケア・デリケートゾーンケア情報 MCP server?
Pono-Pono｜フェムケア・デリケートゾーンケア情報 is a hosted endpoint at https://mcp.yomitasu.jp/s/pono-pono-co-jp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.yomitasu.jp
claude mcp add --transport http jp-yomitasu-pono-pono-co-jp 'https://mcp.yomitasu.jp/s/pono-pono-co-jp/mcp'
What is the Pono-Pono｜フェムケア・デリケートゾーンケア情報 MCP server?
Pono-Pono｜フェムケア・デリケートゾーンケア情報 is an MCP server listed in the public MCP registry as jp.yomitasu/pono-pono-co-jp. 株式会社Pono-Ponoが運営する、フェムケア・デリケートゾーンケアに関する情報サイトです。（pono-pono.co.jp の内容を検索して答える。ヨミタス経由）. This page covers its hosted endpoint (https://mcp.yomitasu.jp/s/pono-pono-co-jp/mcp).
Is the Pono-Pono｜フェムケア・デリケートゾーンケア情報 MCP server safe to use?
Pono-Pono｜フェムケア・デリケートゾーンケア情報 scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Pono-Pono｜フェムケア・デリケートゾーンケア情報 MCP server expose?
Pono-Pono｜フェムケア・デリケートゾーンケア情報 exposes 6 tools: search, fetch, list_pages, site_overview, search_pages, get_page. Their descriptions and schemas cost roughly 981 tokens of context every time the server is loaded.
Does the Pono-Pono｜フェムケア・デリケートゾーンケア情報 MCP server require authentication?
No. We connected to Pono-Pono｜フェムケア・デリケートゾーンケア情報 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pono-Pono｜フェムケア・デリケートゾーンケア情報 MCP server still maintained?
Pono-Pono｜フェムケア・デリケートゾーンケア情報 is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.